Issue 97 in xmonad: xmonad stops responding to keyboard input after running xscreensaver
Issue 97: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 Comment #1 by byorgey: Another data point: today, after unlocking the screen, neither the mouse nor the keyboard would respond. I was still able to switch to a virtual terminal and log in, so I could verify that xmonad was still running. I decided to kill xscreensaver, and it caused X to exit as well. At this point I have no idea whether this is an xmonad bug or an xscreensaver bug. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Hi --
On 07/12/2007, codesite-noreply@google.com
Issue 97: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97
Comment #1 by byorgey: Another data point: today, after unlocking the screen, neither the mouse nor the keyboard would respond. I was still able to switch to a virtual terminal and log in, so I could verify that xmonad was still running. I decided to kill xscreensaver, and it caused X to exit as well. At this point I have no idea whether this is an xmonad bug or an xscreensaver bug.
I don't think this problem is xscreensaver specific, and I would argue is a red-herring. I too find for no apparent reason that after sometime, Firefox no longer responds to keyboard focus unless it is either moved to the floating layer and retiled or a new window is opened. This will be an issue with Firefox though, and not of XMonad itself. How best to fix it (whether XMonad can send a synthetic event to Firefox or not) is still something I am pondering. -- Thomas Adam
participants (2)
-
codesite-noreply＠google.com -
Thomas Adam