Issue 90: Restarting xmonad re-runs dzen/xmobar, which puts it at the top of the window stack http://code.google.com/p/xmonad/issues/detail?id=90 Comment #2 by andrea.rossato: now, xmonad does not run anything and so it is not xmonad that is starting another instance of xmobar or dzen.. so probably you are experiencing some issues with you Xsession startup script. Is this related to documentation you read - that documentation could be indeed bugged? For xmobar, you can use the standard input reader: when xmonad quits xmobar is going to quit too. Have a look at XMonad.Config.Sjanssen (of the xmonad-contrib library) for a working example. I would suggest to mark this report as invalid. Thanks Andrea -- 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