10

I have recently begun trying out XMonad on my Ubuntu 10.04 machine, and I have one major complaint. Oddly, I have not found the problem duplicated elsewhere on the web.

My XMonad session starts out peachy, but after 30 minutes or so, the mod key stops working. If I then want to turn off my computer...if Ihave a terminal open, I can run shutdown manually, but otherwise I have been using the hard power button to shut my computer off.

The failure of the mod key appears to occur after the screensaver has activated and I have subsequently deactivated it.

Can I provide any further information from my xmonad.hs or setup besides

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

?

Thanks in advance,

Jamie D

Sumurai8
  • 20,333
  • 11
  • 66
  • 100
Jamie D
  • 101
  • 3
  • Do you use synergy? I have experienced a similar issue when running a synergy client, where restarting the client "solves" the problem. – bitmask Sep 20 '11 at 13:47
  • 1
    Does the problem also occur when you use the default xmonad config instead of your xmonad.hs? – bitmask Sep 20 '11 at 14:36
  • is your mod key refusing to work globally, or does it still work within other programs? – frosch03 Oct 18 '11 at 10:26

2 Answers2

6

Usually this is because a dynamicLog is writing to a pipe handle that's not being read

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

user2751455
  • 61
  • 1
  • 2
2

I've been looking all over the place for a solution to this bug. Thanks user2751455. If anyone else is having this problem, this one liner (which is just a compressed form of what the linked FAQ says to do) should do the trick:

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

a long-term fix would involve tweaking the xmonad.hs file so that it doesn't spawn pipes that go unread.

pseudo sue
  • 31
  • 1