[xmonad] Issue 97 in xmonad: xmonad stops responding to keyboard input after running xscreensaver

[codesite-noreply at google.com]

Comment #26 on issue 97 by allbery.b: xmonad stops responding to keyboard  
input after running xscreensaver
http://code.google.com/p/xmonad/issues/detail?id=97

The preceding is because the pipe to xmobar is filling up and blocking,  
because xmonad is generating output
faster than xmobar is consuming it.  It might be worth setting stdout to  
nonblocking; otherwise, fork a thread to
handle the log output (and compile with -threaded).

--
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