Dunst: do not display notifications when screensaver/lock is on or when app is in full screen mode
this might be expected behavior (or possibly configurable?), but it would be great to support this
Installation info
- Version:
Dunst - A customizable and lightweight notification-daemon 1.3.0 (2018-01-05) - Install type:
package - Distro and version:
ubuntu 18.04.1 LTS
fawaf
All 25 comments
oh, just found the closed issues about this. do you know if the state querying with i3lock works?
fawaf
on 24 Oct 2018
could you give us please some more information? like some related issues, or some more details about the bad behavior.
bebehei
on 25 Oct 2018
ah yeah, sorry about that.
https://github.com/dunst-project/dunst/issues/77#issuecomment-11372069 says that xscreensaver does not use X11 extensions for setting the screensaver state. i was wondering if i3lock does that and whether dunst respects that.
fawaf
on 25 Oct 2018
Well, #77 is so old, I wouldn't bother to read it :wink:
Do you experience problems? Because usually these type of problems are solved in i3lock.
bebehei
on 25 Oct 2018
yeah, when i3lock is on, dunst still shows notifications over it.
fawaf
on 25 Oct 2018
Tell me more. Which i3lock version? Reproducible behavior? desktop i3wm?
bebehei
on 25 Oct 2018
@gnowxilef Can you try building from master? dffe1e1a5ab39682ce4b279144ad1d1e774f00d7 is an attempt to improve the situation but hasn't been in a release yet.
tsipinakis
on 26 Oct 2018
sure, i can do both.
i3lock version: i3lock: version 2.10 (2017-11-25) 漏 2010 Michael Stapelberg
yep, always happens
yes, desktop i3wm.
fawaf
on 26 Oct 2018
@gnowxilef And does building dunst from master and running it help you, like @tsipinakis said?
git clone https://github.com/dunst-project/dunst.git
cd dunst
make all test
killall dunst
./dunst
the latest master seems to fix the issue for fullscreen mode, but still displays over i3lock.
fawaf
on 29 Oct 2018
Sorry, I can't reproduce it. I've tested it in my Ubuntu 18.04 VM, installed i3, i3lock and dunst. The notification does flicker shortly. But i3lock takes control (it probably receives an XVisibilityEvent) and redraws its own window.
The whole thing happens in less than 50ms.
I can't reproduce it. Could you please deliver a reproducer? Otherwise, I can't help you.
bebehei
on 29 Oct 2018
what do you mean by "deliver a reproducer"? what do you want specifically?
fawaf
on 29 Oct 2018
I just need some kind of information how I can reliably reproduce it on my system.
bebehei
on 29 Oct 2018
It seems that i3lock doesn't redraw on top of the notifications if a composition manager like compton is active (at least in glx mode, I did not try xrender). I never noticed that since I pause dunst notifications with SIGUSR1/2.
My steps were: Start an i3 session, start compton, start i3lock, sleep a bit and send a notification.
progandy
on 30 Oct 2018
@progandy Yeah, I can reproduce it now! Thank you very much!
The question is now: Is it dunst's or i3lock's issue?
bebehei
on 30 Oct 2018
ah yes, i use compton as well.
fawaf
on 30 Oct 2018
That is probably i3lock. For some reason it doesn't raise itself if a compositor is enabled. Try this:
i3lock ; sleep 1; dunstify test; sleep 1; xdotool search --name '^i3lock' windowraise
Well, I think i3/i3lock#130 is quite related. Interestingly, they claim to have it fixed in 2.10.
bebehei
on 30 Oct 2018
The readme and code from xsecurelock make for intersting reading. To hide notifications with a compositor, i3lock probably needs proper compositing support and not that half-baked thing that was reverted.
progandy
on 30 Oct 2018
Is the fullscreen behaviour configurable though? While I agree it makes sense to hide notifications when i3lock is running, I'd rather keep notifications around when running fullscreen apps (which is kinda 90% of the time for me).
WhyNotHugo
on 30 Oct 2018
@WhyNotHugo The fullscreen behavior is something completely different. But it's implemented in #472 and on current master. Search for fullscreen in the dunstrc for more information.
bebehei
on 30 Oct 2018
@bebehei Thanks for the clarification!
WhyNotHugo
on 1 Nov 2018
So guys, can somebody please go on and upstream this to the correct repository?
bebehei
on 8 Nov 2018
As far as I can see, i3lock will just close the issue unless you come with a complete fix in a pull request.
https://github.com/i3/i3lock/issues/130#issuecomment-307741053
https://github.com/i3/i3lock/issues/152
progandy
on 8 Nov 2018
Well, I've upstreamed it now with fairly easy reproduction instructions. I'm going to close this. We can't fix it in this repo.
bebehei
on 10 Nov 2018
Related issues
coxley
路
4Comments
meribold
路
5Comments
chronus7
路
5Comments
patrick-motard
路
6Comments
Kaligule
路
5Comments
Most helpful comment
It seems that i3lock doesn't redraw on top of the notifications if a composition manager like compton is active (at least in glx mode, I did not try xrender). I never noticed that since I pause dunst notifications with SIGUSR1/2.
My steps were: Start an i3 session, start compton, start i3lock, sleep a bit and send a notification.