[xmonad] 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.

Item 2:
Unforgettably my ~/.xsession-errors was empty on crash. I ran several
tests, i think i narrowed down (when) it happens.

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 <allbery.b at gmail.com>
wrote:

> On Thu, Jun 18, 2015 at 2:20 PM, Dave Macias <davama at gmail.com> 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
> allbery.b at gmail.com
> ballbery at sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonad
> http://sinenomine.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/xmonad/attachments/20150623/1691b39d/attachment.html>