Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#13175 - xmobar won't start
Attached to Project:
Community Packages
Opened by Michael (mihi) - Monday, 09 February 2009, 18:31 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 26 February 2009, 10:24 GMT
Opened by Michael (mihi) - Monday, 09 February 2009, 18:31 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 26 February 2009, 10:24 GMT
|
DetailsDescription:
When trying to start xmobar I get following error: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 1 (X_CreateWindow) Serial number of failed request: 29 Current serial number in output stream: 31 Additional info: * package version(s) I've tried it with the plain pacman install and by compiling it myself (using the PKGBUILD script of xmobar). * config and/or log files etc. The error is printed whether I've a configuration or not. I'm running a "Failsave xterm" session started via GDM. My system is up to date. It did not matter if I started xmobar by hand or via the xmonad configuration (as described here: http://haskell.org/haskellwiki/Xmonad/Config_archive/John_Goerzen%27s_Configuration) Steps to reproduce: Start xmobar on x86_64. |
This task depends upon
Closed by Sergej Pupykin (sergej)
Thursday, 26 February 2009, 10:24 GMT
Reason for closing: Fixed
Additional comments about closing: rebuilt with --disable-optimization
Thursday, 26 February 2009, 10:24 GMT
Reason for closing: Fixed
Additional comments about closing: rebuilt with --disable-optimization
Comment by Michael (mihi) -
Monday, 09 February 2009, 18:41 GMT
The current xmobar-darcs from AUR (http://aur.archlinux.org/packages.php?ID=13627) works for me, though.
Comment by David Campbell (Davekong) -
Thursday, 26 February 2009, 00:38 GMT
The bug is related to GHC 6.10/x86_64. Building the package with --disable-optimization should fix it. See this report thread that supplies detailed testing of the issue and an explanation of the fix. http://code.google.com/p/xmonad/issues/detail?id=226