XMonad mod key stops working during a session

Question

I recently started trying out XMonad on my Ubuntu 10.04 machine, and I have one serious complaint. Oddly enough, I did not find the problem duplicated elsewhere on the Internet.

My XMonad session starts with peachy, but after 30 minutes or so, the mod stops working. If I want to turn off the computer ... if I open the terminal, I can start shutdown manually, but otherwise I used the hard power button to turn off the computer.

A malfunction of the mod key appears after activating the screen saver, and I subsequently disabled it.

Is it possible to provide additional information from my xmonad.hs or installation other than

... , modMask = mod4Mask -- Rebind Mod to the Windows key ... 

?

Thanks in advance,

Jamie d

Answer 1

This usually happens because dynamicLog writes to a channel handle that is not readable

http://www.haskell.org/haskellwiki/Xmonad/Frequently_asked_questions#XMonad_is_frozen.21

Answer 2

I have searched everywhere for a solution to this problem. Thanks to user2751455. If anyone else has this problem, this one liner (which is just a condensed form of what the related FAQ is talking about) should do the trick:

cat / proc / $ (ps aux | grep [x] monad | cut -d "" -f4) / fd / *> / dev / null

A long-term fix will include configuring the xmonad.hs file so that it does not produce pipes that are not readable.