You are not logged in.
I have a really weird issue with all window managers: after a window switch I have to restart them. The simptoms are always the same. Focus gets stuck on one window, and no window raises, and many buttons stop working (both decoration and app buttons):
- kwin has to be restarted every window switch.
- openbox does the same.
- awesome suffers from the same condition, but it shows these errors on launch:
W: awesome: xerror:811: X error: request=GrabKey (major 33, minor 0), error=BadAccess (10)
W: awesome: xerror:811: X error: request=GrabKey (major 33, minor 0), error=BadAccess (10)
W: awesome: xerror:811: X error: request=GrabKey (major 33, minor 0), error=BadAccess (10)
W: awesome: xerror:811: X error: request=GrabKey (major 33, minor 0), error=BadAccess (10)
W: awesome: xerror:811: X error: request=GrabKey (major 33, minor 0), error=BadAccess (10)
W: awesome: xerror:811: X error: request=GrabKey (major 33, minor 0), error=BadAccess (10)
W: awesome: xerror:811: X error: request=GrabKey (major 33, minor 0), error=BadAccess (10)
W: awesome: xerror:811: X error: request=GrabKey (major 33, minor 0), error=BadAccess (10)Xorg log shows this message when I start compiz, but i don't think it has any relation:
[ 703.101] (II) NVIDIA(GPU-0): Display (Acer X243W (CRT-0)) does not support NVIDIA 3D Vision
[ 703.101] (II) NVIDIA(GPU-0): stereo.
[ 703.101] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 703.101] (**) NVIDIA(0): device Acer X243W (CRT-0) (Using EDID frequencies has been
[ 703.101] (**) NVIDIA(0): enabled on all display devices.)The problem started suddently. Las upgrade before the errors was 3 days ago. No dmesg output seems related to to this. Nothing comes out once this happens.
So, the WMs just stop working, and I don't know any other file/method to get more information that can point me to the problem.
I updated the system after the problem.
I am using nvidia propietary driver, linux-ck.
If anyone knows about it, had a similar situation or can point me other places commands/logs to check I will appreciate the help.
Thank you
Last edited by Pajaro (2012-12-19 09:04:15)
Offline
After posting I closed all application to go to a reboot and then it was working again. I had rebooted before.
Xorg.0.log shows this:
[ 4043.911] (II) NVIDIA(0): Setting mode "CRT-0:nvidia-auto-select"
[ 4043.965] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 4043.965] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 4043.965] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 4043.965] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 4043.965] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 4043.965] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 4043.965] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 4043.965] (II) NVIDIA(0): Config Options in the README.After seeing the error I installed acpid and enabled it. Let's see how it goes now, but I am surprised that it could be and acpi error. Again, dmesg says nothing, journalctl says nothing.
Last edited by Pajaro (2012-12-18 23:25:51)
Offline
After a reboot the issue came back. I unplugged and plugged again the keyboard and the mouse, the issue seems to have gone.
Last edited by Pajaro (2012-12-19 09:04:02)
Offline
next time this happens, see if a cold reboot makes a difference.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
next time this happens, see if a cold reboot makes a difference.
I'll try, thank you. I just got puzzled for the fact that no error was reported anywhere.
Offline