avoidStruts not working on first start
Hello XMonad list! For some reason avoidStruts doesn't seem to work the first time I log in, my dzen bars are hidden. However if I reload XMonad it seems to work fine. I can only reproduce this behaviour by rebooting the machine. This configuration used to work before, but recently I've switched to an ssd, so I suspect that the problem might be related to some race condition. Did anyone had this problem before? I've pasted my xmonad.hs here: http://pastebin.com/6nzAWCQa -- Best Regards, Peter Kasza http://www.iit.uni-miskolc.hu/~kasza1 mr.schyte@gmail.com () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
For what it's worth, I've been seeing this too. What's more, it's even more specific than "first boot": it's also only a problem on the first workspace! Very strange. I've no idea what's causing it. ~d On 2013-09-28 18:09, Kasza Péter wrote:
Hello XMonad list!
For some reason avoidStruts doesn't seem to work the first time I log in, my dzen bars are hidden. However if I reload XMonad it seems to work fine. I can only reproduce this behaviour by rebooting the machine. This configuration used to work before, but recently I've switched to an ssd, so I suspect that the problem might be related to some race condition. Did anyone had this problem before?
I've pasted my xmonad.hs here: http://pastebin.com/6nzAWCQa
_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad
On Tue, Oct 01, 2013 at 10:30:26PM -0400, Daniel Wagner wrote:
For what it's worth, I've been seeing this too. What's more, it's even more specific than "first boot": it's also only a problem on the first workspace! Very strange. I've no idea what's causing it.
~d Strange. You're right, It happens only on the first workspace for me too. I haven't noticed that before. I'll try to debug it on the weekend, but I don't know much about the internals of XMonad.
-- Best Regards, Peter Kasza http://www.iit.uni-miskolc.hu/~kasza1 mr.schyte@gmail.com () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
On Wed, Oct 2, 2013 at 2:02 PM, Kasza Péter
On Tue, Oct 01, 2013 at 10:30:26PM -0400, Daniel Wagner wrote:
For what it's worth, I've been seeing this too. What's more, it's even more specific than "first boot": it's also only a problem on the first workspace! Very strange. I've no idea what's causing it.
Strange. You're right, It happens only on the first workspace for me
too. I haven't noticed that before. I'll try to debug it on the weekend, but I don't know much about the internals of XMonad.
The other day, a couple people in the IRC channel reported this happening starting after an Ubuntu update. Perhaps we have an xorg (or other dependency) bug? -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
On Wed, 02 Oct, 2013 at 02:30:26 GMT, Daniel Wagner wrote:
For what it's worth, I've been seeing this too. What's more, it's even more specific than "first boot": it's also only a problem on the first workspace! Very strange. I've no idea what's causing it.
What about multiple monitors? I sometimes see my terminals overlap xmobar, but moving between workspaces (even just focusing another monitor), or switching the focused window with <prefix>j makes the struts apply again. My xmobars usually take a while on first login because the network isn't up yet and the Weather plugin is timing out, but I've seen it on subsequent logins where I open a terminal quickly as well. Could it be that xmonad only checks for struts when something changes and doesn't get notified on their creation? --Ben
On 2013-10-10 01:11, Ben Boeckel wrote:
On Wed, 02 Oct, 2013 at 02:30:26 GMT, Daniel Wagner wrote:
For what it's worth, I've been seeing this too. What's more, it's even more specific than "first boot": it's also only a problem on the first workspace! Very strange. I've no idea what's causing it.
What about multiple monitors? I sometimes see my terminals overlap xmobar, but moving between workspaces (even just focusing another monitor), or switching the focused window with <prefix>j makes the struts apply again. My xmobars usually take a while on first login because the network isn't up yet and the Weather plugin is timing out, but I've seen it on subsequent logins where I open a terminal quickly as well.
Could it be that xmonad only checks for struts when something changes and doesn't get notified on their creation?
I know the behavior you're talking about: sometimes, xmonad seems to have "lost" the fact that xmobar appears. But just about anything fixes it: opening a new window, switching workspaces, hitting xmonad's "redraw" key -- anything that causes the layout to be recomputed clears the problem. With what I'm seeing now, only a full restart (of either xmonad or xmobar) fixes the problem. In addition, for what it's worth, I have two monitors. I run xmobar on each monitor, and trayer only on one monitor. On the first workspace for each monitor, the space left open for struts is wrong -- and in different ways on the two monitors. ~d
On Thu, Oct 10, 2013 at 2:19 AM, Daniel Wagner
On 2013-10-10 01:11, Ben Boeckel wrote:
On Wed, 02 Oct, 2013 at 02:30:26 GMT, Daniel Wagner wrote:
For what it's worth, I've been seeing this too. What's more, it's even more specific than "first boot": it's also only a problem on the first workspace! Very strange. I've no idea what's causing it.
Could it be that xmonad only checks for struts when something changes and doesn't get notified on their creation?
I know the behavior you're talking about: sometimes, xmonad seems to have "lost" the fact that xmobar appears. But just about anything fixes it: opening a new window, switching workspaces, hitting xmonad's "redraw" key -- anything that causes the layout to be recomputed clears the problem.
So, for grins and giggles --- does http://xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Hooks-ManageDocks.html#v... (See also https://code.google.com/p/xmonad/issues/detail?id=525)
In addition, for what it's worth, I have two monitors. I run xmobar on each monitor, and trayer only on one monitor. On the first workspace for each monitor, the space left open for struts is wrong -- and in different ways on the two monitors.
Depending on how the monitors are positioned, this could be https://code.google.com/p/xmonad/issues/detail?id=526 . -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
I cannot reproduce this bug anymore, it seems to have disappeared after an update to X11. -- Best Regards, Peter Kasza http://www.iit.uni-miskolc.hu/~kasza1 mr.schyte@gmail.com () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
participants (4)
-
Ben Boeckel -
Brandon Allbery -
Daniel Wagner -
Kasza Péter