Issue 390 in xmonad: xmobar crashes after some minutes of work

Status: New Owner: ---- New issue 390 by muellerto: xmobar crashes after some minutes of work http://code.google.com/p/xmonad/issues/detail?id=390 What steps will reproduce the problem? Difficult to explain. In my case xmobar disappears completely from the screen and the process ends surely after some minutes of work. After I started X11 with Xmonad and xmobar I can change the focus between applications, I can switch virtual screens, several times, everything looks great. But after not more than five minutes xmobar dies completely. I can't tell a more concrete reason for this. What is the expected output? What do you see instead? I see only the remaining xmobar output as long as the screen isn't painted again. After I switch to another virtual screen I see only the configured black gap on top of the screen. What version of the product are you using? On what operating system? xmobar 0.9.2, xmonad 0.9, Arch Linux x86_64 Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". The relevant lines in my xmonad.hs are: main = do handle <- spawnPipe "xmobar" xmonad defaultConfig { This has been working very well for more than a year or so. I didn't change anything on xmonad.hs nor on .xmobarrc. Please provide any additional information below. The problem came with the last update of ghc (6.12) provided by the Arch Build System. I recompiled Xmonad manually and this runs very well. Now I also recompiled xmobar but that didn't solve the problems. -- 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

Comment #1 on issue 390 by muellerto: xmobar crashes after some minutes of work http://code.google.com/p/xmonad/issues/detail?id=390 I watched this seriously now. For this I made xmobar as simple as possible. I let it consist of the text only and removed all other parts from it. The crash happens when the text changes, this means when Xmonad writes on stdout, but not at the first time. I guess it's related to the length of the text or a specific character. -- 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

Comment #2 on issue 390 by daniel.wagner: xmobar crashes after some minutes of work http://code.google.com/p/xmonad/issues/detail?id=390 Can you please try the darcs version of xmobar? They recently fixed a bug in dealing with certain UTF8-encoded Unicode characters. -- 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

Comment #3 on issue 390 by jaspervdj: xmobar crashes after some minutes of work http://code.google.com/p/xmonad/issues/detail?id=390 I think I encountered this issue as well. For me, the concrete problem was that the title of the current window sometimes contained strange characters. I fixed it by using customPP = defaultPP { -- Filter out strange characters that might cause xmobar to crash. ppTitle = shorten 80 . filter (\c -> ord c < 128) ... Hope this helps. -- 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

Comment #4 on issue 390 by vogt.adam: xmobar crashes after some minutes of work http://code.google.com/p/xmonad/issues/detail?id=390 For reference this is the xmobar issue daniel mentioned: http://code.google.com/p/xmobar/issues/detail?id=17 And the appropriate bug with your package, where #4 has a workaround if you can't use xmobar from darcs: http://bugs.archlinux.org/task/18867 -- 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

Comment #5 on issue 390 by muellerto: xmobar crashes after some minutes of work http://code.google.com/p/xmonad/issues/detail?id=390 YES! The 0.10 from the darcs repository solves the problem. But I couldn't use my wonderful piped command lines any longer with this 0.10. I had command outputs piped through sed for formatting purposes. This causes xmobar parse errors :( I made small scripts now for this. xmobar calls these scripts and gets only the output back while the piping is in the scripts. This works fine and my .xmobarrc is much simpler now. -- 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

Updates: Status: Invalid Comment #6 on issue 390 by vogt.adam: xmobar crashes after some minutes of work http://code.google.com/p/xmonad/issues/detail?id=390 (No comment was entered for this change.) -- 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
participants (1)
-
codesite-noreply@google.com