Community Packages

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!
Tasklist

FS#47545 - xmobar is covered by other windows

Attached to Project: Community Packages
Opened by Yisu Remy Wang (remwang) - Sunday, 27 December 2015, 20:01 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 01 January 2016, 15:19 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jelle van der Waa (jelly)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

xmobar is covered by other window. Downgrading xmonad and xmonad-contrib to the previous version solves the problem. The same bug appeared a while ago see http://stackoverflow.com/q/13867197

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:

start xmonad, then open xterm.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 01 January 2016, 15:19 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Configuration issue
Comment by Ebrahim Azarisooreh (eazar001) - Tuesday, 29 December 2015, 06:20 GMT
I can verify this behavior. However for me, it only happens on the first xmonad workspace. The other workspaces behave as expected, with xmobar on top. I currently use `trayer` in conjunction with the WM and taskbar; killing trayer and reenabling it seems to act as a hack/temporary fix to stop it from hiding behind windows. I have not yet tried a downgrade.
Comment by Ebrahim Azarisooreh (eazar001) - Tuesday, 29 December 2015, 21:39 GMT
The resolution is pointed to by: https://github.com/jaor/xmobar/issues/249
I expect a more permanent integration of the solution to be in the next release.
Comment by Yisu Remy Wang (remwang) - Tuesday, 29 December 2015, 22:25 GMT
I don't even have trayer. I wonder if this is an xmonad problem or one from xmobar. But since downgrading fixes it, the former's more possible.
Comment by Ebrahim Azarisooreh (eazar001) - Tuesday, 29 December 2015, 23:18 GMT
No, the solution is not to get trayer. The solution is to add `OverrideRedirect=False` to your xmobarrc file.
Comment by Ebrahim Azarisooreh (eazar001) - Thursday, 31 December 2015, 02:21 GMT
Were you able to fix it with that @remwang?
Comment by Ebrahim Azarisooreh (eazar001) - Thursday, 31 December 2015, 02:22 GMT
And by the way, the configuration setting was overrideRedict = False
I misstated it above.
Comment by Yisu Remy Wang (remwang) - Thursday, 31 December 2015, 02:40 GMT
Yep worked like a charm, Thanks. From the history of the github issue it looks like the flag was a hack from xmobar's end to deal with the behavior, so I guess there's still something to fix.

Loading...