window clients ignore docks on xmonad login

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

window clients ignore docks on xmonad login

Dave Macias
When log into box for the first time the "sendMessage ToggleStruts" seems to be on because when i open a terminal or any window it covers the docks.
I tested opening a window client on another non-visible workspace at it respected the dock. It seems to only affect visible (focused/nonfocused) workspaces.
Only when i reset the layout or change workspace does the dock get uncovered.

only see this happening with darcs version 0.12. I tested also with haskell version and it works fine. Docks are respected all the time.

One more thing:
when i have an urgenthint evoked and i run "xmonad --restart" i get kicked out of xmonad and into my login screen (lxdm)
Someone had told on the irc channel that it had to do with the window id and the timer "remindWhen". This happens on both darcs and haskell versions of xmonad.

here is a snippet of the urgentconfig: 
myUrgencyConfig = urgencyConfig {suppressWhen= Visible, remindWhen = (Every (minutes 1.0))}



Hope all this makes sense.

Thank you in advance

-Dave

_______________________________________________
xmonad mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad
Reply | Threaded
Open this post in threaded view
|

Re: window clients ignore docks on xmonad login

Brandon Allbery
On Thu, Jun 18, 2015 at 2:20 PM, Dave Macias <[hidden email]> wrote:
When log into box for the first time the "sendMessage ToggleStruts" seems to be on because when i open a terminal or any window it covers the docks.

I have not been able to reproduce this. I do know of a similar issue but it is not likely to produce these symptoms (opening a window corrects it, for example).

The edges of desktop windows (e.g. file manager window) are often covered because older versions don't set _NET_WORKAREA and darcs sets it incorrectly; this should not affect docks.

It is conceivable that the change to avoidStruts to (incorrectly) calculate _NET_WORKAREA caused a problem, but as I have two xmonad instances that do not show the problem you describe, I don't think it broke strut handling significantly.
 
One more thing:
when i have an urgenthint evoked and i run "xmonad --restart" i get kicked out of xmonad and into my login screen (lxdm)
Someone had told on the irc channel that it had to do with the window id and the timer "remindWhen". This happens on both darcs and haskell versions of xmonad.

That was probably me, as I've discussed that with at least two people in #xmonad over the past month. :)

I have never reproduced this one, either, but as I run xmonad under MATE I have never had a reason to configure the UrgencyHook.

It would help if you could arrange for your .xsession-errors to be saved after a crash (log in on a text console or ssh and copy it out of the way) so we could see the error message from the crash.

--
brandon s allbery kf8nh                               sine nomine associates
[hidden email]                                  [hidden email]
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net

_______________________________________________
xmonad mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad
Reply | Threaded
Open this post in threaded view
|

Re: window clients ignore docks on xmonad login

Dave Macias
Thank you for the reply Brandon.

Regarding item 1, i really didn't understand much of what you mentioned or how i could test it. Either way when i flip the visible workspaces (focused/non) on my monitors the problem goes away and the avoidstrut works. I googled a bit and i believe "_NET_WORKAREA" has to do with EWMH desktops. The only thing i use is "ewmhDesktopsLogHook" because i gives keyboard focus to chromium when switch to it. Didn't like the whole ewmh functionality cuz it would steal my focus.


configuration: xmonad $ withUrgencyHook myUrgentHook   --- no urgencyconfig
what is visible:  dzen bar and logpp on 
restart effect: kicks out
;;
same config
what is visible: just logpp is on, bar disappears
restart effect: xmoand restart successfully
;;
configuration: xmonad $ withUrgencyHookC myUrgentHook myUrgencyConfig --- where myUrgencyConfig = urgencyConfig { suppressWhen = Focused }
what is visible: both bar ahd logpp
restart effect: kicks out
;;
same config:
what is visible: logpp
restart effect: xmonad is good
;; 
configuration: xmonad $ withUrgencyHookC myUrgentHook myUrgencyConfig --- where myUrgencyConfig = urgencyConfig {suppressWhen= Visible, remindWhen = (Every (minutes 1.0))}
for this one i get kicked out regardless of what is visible

Thanks again
Dave


On Fri, Jun 19, 2015 at 9:16 PM, Brandon Allbery <[hidden email]> wrote:
On Thu, Jun 18, 2015 at 2:20 PM, Dave Macias <[hidden email]> wrote:
When log into box for the first time the "sendMessage ToggleStruts" seems to be on because when i open a terminal or any window it covers the docks.

I have not been able to reproduce this. I do know of a similar issue but it is not likely to produce these symptoms (opening a window corrects it, for example).

The edges of desktop windows (e.g. file manager window) are often covered because older versions don't set _NET_WORKAREA and darcs sets it incorrectly; this should not affect docks.

It is conceivable that the change to avoidStruts to (incorrectly) calculate _NET_WORKAREA caused a problem, but as I have two xmonad instances that do not show the problem you describe, I don't think it broke strut handling significantly.
 
One more thing:
when i have an urgenthint evoked and i run "xmonad --restart" i get kicked out of xmonad and into my login screen (lxdm)
Someone had told on the irc channel that it had to do with the window id and the timer "remindWhen". This happens on both darcs and haskell versions of xmonad.

That was probably me, as I've discussed that with at least two people in #xmonad over the past month. :)

I have never reproduced this one, either, but as I run xmonad under MATE I have never had a reason to configure the UrgencyHook.

It would help if you could arrange for your .xsession-errors to be saved after a crash (log in on a text console or ssh and copy it out of the way) so we could see the error message from the crash.

--
brandon s allbery kf8nh                               sine nomine associates
[hidden email]                                  [hidden email]
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net


_______________________________________________
xmonad mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad