However, after recompiling xmonad and restarting my computer, everything is fixed again.
I would suggest that people try a combination of (1) recompiling xmonad and (2) restarting X / restarting computer. Eventually, for me at least, everything gets fixed, and I don't have to worry until next time I update something relevant to xmonad.
]]>(Using xmobar 0.15-2 with xmonad 0.11-1 still works perfectly btw)
]]>Cheers.
]]>brianb wrote:Hey guys, no need to downgrade xmobar or ghc. When you upgrade xmobar (e.g., from 0.15-* to 0.16-3, or from 0.16-1 to 0.16-3), just make sure to recompile and restart xmonad once. Mod Q by default, or
xmonad --recompile xmonad --restart
Then hit reset your layout (mod+shift+space by default) and you should see xmobar just fine. This worked for me, at least.
This didn't work for me on xmobar 0.16-3, had to downgrade to 0.16-1.
Weird. I'm up and running just fine with ghc 7.6.1 and xmobar 0.16-3. Did you try logging out of and back into X after recompiling xmonad?
]]>Hey guys, no need to downgrade xmobar or ghc. When you upgrade xmobar (e.g., from 0.15-* to 0.16-3, or from 0.16-1 to 0.16-3), just make sure to recompile and restart xmonad once. Mod Q by default, or
xmonad --recompile xmonad --restart
Then hit reset your layout (mod+shift+space by default) and you should see xmobar just fine. This worked for me, at least.
This didn't work for me on xmobar 0.16-3, had to downgrade to 0.16-1.
]]>xmonad --recompile
xmonad --restart
Then hit reset your layout (mod+shift+space by default) and you should see xmobar just fine. This worked for me, at least.
]]>See here for more details: https://github.com/jaor/xmobar/issues/78
Archlinux is providing 7.6.2 by default but it's not part of the haskell platform, so lot of things are broken.
]]>