-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Immediate crash with xf86-intel-video and xorg-server-git #7
Comments
Thanks for the report. Chamferwm does some logging to stdout, try this in your .xinitrc to have the log written: exec stdbuf -oL chamfer --shader-path=/usr/share/chamfer/shaders/ > /tmp/log Please upload the log here and let's see 👍 |
Nothing too interesting in the log, but another possibly relevant error caught my eye. When X crashes, it spews out the error I'm really not trying to load chamfer on my nvidia gpu, and I'm not sure why it would try that. Probably doesn't matter, but I do have the latest nvidia drivers, and I think I have nouveau blacklisted/not installed. It is supposed to work on intel GPUs right? FIY, chamfer starts fine without compositor (i.e. with Output of
|
Yes, it should definitely work on Intel GPUs. I found that the problem is most likely related to how makepkg builds the binary. I disabled custom build flags in PKGBUILD for now, can you try update from AUR and rebuild? |
Works great, thanks! |
I still get the |
If I launch chamferwm (with instructions from the README), for a few seconds I see a black screen and a mouse pointer that I can move around, and then it crashes me back to the tty. It doesn't seem like it will let me start any programs.
I can't see any errors in
~/.local/share/xorg/Xorg.0.log
. Is there another place where errors are logged?I installed chamerfwm from the AUR. Other specifics are that I'm running xf86-intel-video-git, xorg-server-git, and a vanilla, fully updated Arch.
It's probably a misconfiguration on my side, so my main question is where to look for errors.
The text was updated successfully, but these errors were encountered: