Xmonad becomes unresponsive. No focus changing (using keys or mouse), workspace changing or recompile.

[GoogleCodeExporter]

What steps will reproduce the problem?

1. No idea.  Each time time it's with relatively few windows open (chromium 
with ~10 tabs and ~4 instances of urxvt).  Nothing too heavy.  Seems to be 
random at this point.

What is the expected output? What do you see instead?

I expect it to...well, no lock up.  But it freezes up and none of the 
keybindings in haskell.hs work (can't even recompile).  I can't change 
workspaces or window focus, but the currently focused window still has its 
(non-monad related) bindings and functionality work fine (chromium, screen w/ 
urxvt) and I can still ctrl+alt+F1 to console.  Mouse still works, but it 
doesn't change focus on the windows.

What version of the product are you using? On what operating system?

Arch x86_64 with kernel 2.6.34-ARCH and xmonad 0.9.1

Are you using an xmonad.hs?  Please attach it and the output of "xmonad
--recompile".

No --recompile output.  See attached for xmonad.hs.

Please provide any additional information below.

It's done it twice in the less than 24 hours I've had it installed.  ivanm @ 
#xmonad has confirmed this problem also. (see logs for 30/07/10 19:31)

Original issue reported on code.google.com by 6181...@gmail.com on 31 Jul 2010 at 2:40

Attachments:

• xmonad.hs

[GoogleCodeExporter]

Thats 19:31 PDT by the way.

Original comment by 6181...@gmail.com on 31 Jul 2010 at 2:45

[GoogleCodeExporter]

To make it easier, here are the relevant parts of the logs:

<nharris> Does anyone ever have issues where the keys don't respond in xmonad?
<nharris> well
<nharris> xmonad doesn't respond at all
<nharris> but the last window with focus does
<nharris> (chromium in this case)
<nharris> I can't change workspaces or windows
<nharris> or reload for that matter
<nharris> bleh
<nharris> I'm filing a bug report
<nharris> I can't find anything existing that matches that
<ivanm> I've had that before
<ivanm> could never work out what happened
<ivanm> luckily, the window that was focussed was xchat, so I could use /exec 
to kill the current instance of xmonad and start it again
<nharris> huh
<nharris> I have to go to tty1 and ^C it
<nharris> well in any case, I'm about to post the report, brb
<nharris> how  often does it happen btw?
<ivanm> nharris: I've had it happen maybe 2 or 3 times in what, 3 years?

Original comment by ivan.miljenovic@gmail.com on 31 Jul 2010 at 2:56

[GoogleCodeExporter]

Is there anything I can do to pinpoint the problem when it's frozen?  It's 
locked up now and I'd like to do what I can to get this worked out.

Original comment by 6181...@gmail.com on 31 Jul 2010 at 3:37

[GoogleCodeExporter]

Try to find out what it's frozen on:  attach to it with gdb or a tracer and see 
what system call it's blocked in.  (I'd bet it's stuck writing to xmobar, which 
will have choked for some reason.)

Linux: strace
recent Mac OS X and Solaris: dtruss
older Solaris: truss
*BSD and older Mac OS X: ktrace

Original comment by allber...@gmail.com on 31 Jul 2010 at 3:42

[GoogleCodeExporter]

OK so after running 'strace -p <xmonad pid>' I get the following:

select(5, [], [4], NULL, {134, 217727}

and after a minute or so this gets added to the same line:

) = 0 (Timeout)

Original comment by 6181...@gmail.com on 31 Jul 2010 at 4:20

[GoogleCodeExporter]

That looks exactly like being stuck on writing to xmobar.

Original comment by liskni...@gmail.com on 31 Jul 2010 at 7:42

[GoogleCodeExporter]

Can you confirm that xmobar actually runs? (Have you got it installed? Is it in 
your path? Does it appear when xmonad starts?)

Original comment by daniel.w...@gmail.com on 31 Jul 2010 at 7:48

[GoogleCodeExporter]

Daniel.wagner: yes, yes, and yes. I'm away from my computer but would you like 
to see .xmobarrc when I get back to it?

Original comment by 6181...@gmail.com on 31 Jul 2010 at 8:28

[GoogleCodeExporter]

Config { font = "xft:DejaVu Sans Mono:pixelsize=10:antialias=true:hinting=true"
       , bgColor = "#2b2b2b"
       , fgColor = "#00e0ff"
       , position = Top
       , lowerOnStart = True
       , commands = [ Run Network "eth0" ["-L","0","-H","32","--normal","green","--high","red"] 10
            , Run Network "wlan0" ["-L","0","-H","32","--normal","green","--high","red"] 10
                    , Run Cpu ["-L","3","-H","50","--normal","green","--high","red"] 10
                    , Run Memory ["-t","Mem: <usedratio>%"] 10
                    , Run Swap [] 10
                    , Run Com "uname" ["-s","-r"] "" 36000
                    , Run Date "[ %d-%m // %H:%M ]" "date" 10
                    ]
       , sepChar = "%"
       , alignSep = "}{"
       , template = "}{<fc=#00e0ff>[ %cpu% | %memory% | %swap% ] // [ %eth0% | %wlan0% ]</fc> <fc=#ffe100>%date%</fc>"
       }

Original comment by 6181...@gmail.com on 1 Aug 2010 at 6:47

[GoogleCodeExporter]

Yeah, okay, your pipe to xmobar is filling up. You have two choices. One is to 
use the StdinReader add-on or module or whatever they call it for xmobar 
(adding it both to the list of commands *and* to the template). The other is to 
change your xmonad config to use spawn instead of spawnPipe and take xmobar out 
of your log hook. It would look something like this:

main = do
    xmonad $ withUrgencyHook NoUrgencyHook
           $ defaultConfig {
                terminal           = "urxvt",
                modMask            = mod4Mask,
                borderWidth        = myBorderWidth,
                workspaces         = ["1", "2", "3", "4", "5", "6", "7", "8", "9"],
                normalBorderColor  = "#00e0ff",
                focusedBorderColor = "#f92672",
                manageHook         = myManageHook,
                keys               = myKeys,
                mouseBindings      = myMouseBindings,
                layoutHook         = myLayout,
                startupHook        = spawn "xmobar"
    }

See also 
http://haskell.org/haskellwiki/Xmonad/Frequently_asked_questions#XMonad_is_froze
n.21

Original comment by daniel.w...@gmail.com on 1 Aug 2010 at 2:40

[GoogleCodeExporter]

Havin the same issue without xmobar..

Original comment by ostro...@gmail.com on 15 Jun 2012 at 2:49

[GoogleCodeExporter]

ostronom, if xmobar (or dzen or some similar consumer) is not running, but you 
have a log hook, then you are almost certainly filling up a pipe. Get rid of 
your log hook if you know how, or attach your config here and we can help you 
do that.

Original comment by daniel.w...@gmail.com on 15 Jun 2012 at 4:23

[GoogleCodeExporter]

I'm very sorry. There was a filled up pipe, but deep in modules.

Original comment by ostro...@gmail.com on 15 Jun 2012 at 4:35

[GoogleCodeExporter]

Hello,

I am experiencing the same problem. I would be very thankful if someone could 
help me fix my config. Thank You.

Config { font = "-*-Fixed-Bold-R-Normal-*-13-*-*-*-*-*-*-*"
       , bgColor = "black"
       , fgColor = "grey"
       , position = Top
       , lowerOnStart = False
       , commands = [ Run Weather "EGPF" ["-t"," <tempF>F","-L","64","-H","77","--normal","green","--high","red","--low","lightblue"] 36000
                    , Run Cpu ["-L","3","-H","50","--normal","green","--high","red"] 10
                    , Run Memory ["-t","Mem: <usedratio>%"] 10
                    , Run Swap [] 10
                    , Run Date "%a %b %_d %l:%M" "date" 10
                    , Run StdinReader
                    ]
       , sepChar = "%"
       , alignSep = "}{"
       , template = "%StdinReader% }{ %cpu% | %memory% * %swap%    <fc=#ee9a00>%date%</fc> | %EGPF%"
       }

Original comment by slyons...@gmail.com on 13 Sep 2012 at 3:39

[GoogleCodeExporter]

slyons511, You will also need to show us your xmonad config.

Original comment by daniel.w...@gmail.com on 13 Sep 2012 at 4:00

[GoogleCodeExporter]

I am also experiencing this problem. Here is the link to my xmonad.hs file: 
http://pastebin.com/UpFa1xpy
Thanks in advance and sorry for digging up an old thread !

Original comment by abhixecu...@gmail.com on 1 Mar 2013 at 2:51

[GoogleCodeExporter]

abhixecutor (and future visitors to this bug report), we need to see both 
xmonad.hs and the configuration files for whatever bar you are running (e.g. 
.xmobarrc). The bug reported here arises when two processes aren't agreeing 
about how to communicate, so showing just one or the other process's 
configuration is not enough.

Original comment by daniel.w...@gmail.com on 1 Mar 2013 at 12:15