Comment #31 on issue 97 by savinov.guram: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 I have same problem and I don't use xmodbar: 1. booting gdm->xmonad 2. run xscreensaver-command -lock 3. click "new login" and go to gdm 4. click to my user and return to xscreensaver locker 5. put password 6. keyboard don't responce 7. mouse work correctly, and keybooard will responce if I change windows by mouse How to fix this problem?

Comment #33 on issue 97 by selfsorted: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 I also have the same problem in Ubuntu 10.10 and previously in Ubuntu 10.04 (I also tried latest version from darcs and the problem is still there). I don't use xmobar. The problematic application is Netbeans - after only about 1 hour of using it it completely stops responding to keyboard. My config is very simple. My .xsession: xrdb -merge .Xresources gnome-power-manager& nm-applet --sm-disable& exec /home/artur/.cabal/bin/xmonad This forced me to stop using XMonad so for me this is a highest-priority bug!

Comment #35 on issue 97 by s.g.mcat...@gmail.com: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 I also had this issue and it turned out that I somehow had two copies of the xscreensaver daemon running at startup. To check if this is the case in your configuration, open a terminal and type: $ ps aux | grep xscreensaver You should get something like: ******** 970 0.7 0.0 59528 2836 ? S 07:06 0:00 xscreensaver -nosplash ******** 1050 0.0 0.0 9144 1060 pts/1 S+ 07:06 0:00 grep --color=auto screen The top line is the xscreensaver daemon and the second line is the command you entered above - this is what it *should* look like. When I had two copies of xscreensaver running, i.e. the output looked like: ******** 970 0.7 0.0 59528 2836 ? S 07:06 0:00 xscreensaver -nosplash ******** 970 0.7 0.0 59528 2836 ? S 07:06 0:00 xscreensaver -nosplash ******** 1050 0.0 0.0 9144 1060 pts/1 S+ 07:06 0:00 grep --color=auto screen I was suffering the described error. Solution: check your startup scripts to make sure that xscreensaver daemon is only launched once.

Comment #37 on issue 97 by BabyG...@gmail.com: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 Just hit this problem. First time user and fresh (2day old) install of ubuntu saucy. Happened on password screen, no way to input password. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

Comment #39 on issue 97 by beyer...@gmail.com: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 I strongly suspect that the issue is related to keyboard focus, based on this log from my xsession: xscreensaver: 19:20:55: couldn't grab keyboard! (AlreadyGrabbed) xscreensaver: 19:20:59: couldn't grab pointer! (AlreadyGrabbed) I know of a few workarounds, although the latter is somewhat tedious. 1) If you are using TwoPane, simply focus the other window with the mouse and it should regain keyboard focus. 2) If that doesn't work, go into a console (ex. Ctrl+Alt+F1..F[N]), set your DISPLAY environment variable to your regular display and execute an arbitrary GUI application (I use xterm), and then you should regain keyboard focus. Once you're done with that, log off on the console, and close the redundant application. I wouldn't say that it's a bug in xscreensaver per-se, or at least, it is relatively easy for me to regain keyboard focus in wmii (as a point of comparison). I don't think that the issue affects non-tiling window managers at all. I'm working on software with timed locking (like xidle) for my screen locker, metalock. (I would suspect that the main reason why xscreensaver is preferred over other tools is due to the daemon's ability to accept pings via xscreenaver-cmd -deactivate) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings