Comment #25 on issue 317 by mlmeola: Implement a working X.U.putSelection http://code.google.com/p/xmonad/issues/detail?id=317 (First of all, I love xmonad. thanks for all the work) How is this low priority? A window manager should never hang. It needs to be critical. People often type Ctrl-C to try to close things. That shouldn't hang the window manager. Getting a useful action working may be low priority, but stopping the hang should be done immediately.

Comment #27 on issue 317 by gwern0: Implement a working X.U.putSelection http://code.google.com/p/xmonad/issues/detail?id=317 alexey, what he means is that the high priority is getting the removal of putSelection into a release and this is a major concern which has gone unnoticed; notice that users *not* running out of darcs will be running http://hackage.haskell.org/packages/archive/xmonad-contrib/0.9.1/doc/html/XM... which can freeze Xmonad.

Comment #29 on issue 317 by mlme...@gmail.com: Implement a working X.U.putSelection http://code.google.com/p/xmonad/issues/detail?id=317 My workaround while waiting for a release that fixes this is a modified exec line in my .xinitrc: exec bash -c '/usr/bin/xmonad ; while [ $? -eq 143 ] ; do echo "xmonad restarting" ; /usr/bin/xmonad ; done' 143 is what xmonad (many things? everything?) returns when killed by sigterm, so when xmonad freezes, a simple Ctrl+Alt+F2, login, and killall xmonad fixes everything.