-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dunst notifications are not paused as postlock directly executes #389
Comments
Please retry newest release, can't reproduce as I don't use betterlockscreen anymore but open to pull-requests if the issue gets confirmed. |
The problem still persists for me. I wonder whether I am on the only one with that problem now… This issue did not gain a single reaction as far as I can judge and that should be a relatively glaring problem. |
Same issue here. My dunst is still sending notifications after locking the screen with I am using the newest release and bspwm btw. |
From my point of view the suggested
does that help? |
Nope, dunst is still showing notifications after, sry about that... Btw I have checked multiple related issues, some of them mentioned about compton like picom, but even with |
I don't see what/why picom/compton as compositor should have todo with dunst not pausing notifications right? Can you place |
Sure, there you go:
Whats more, if I manually pause dunst with |
Can you add I want to ensure if postlock is called after unlocking or right after locking if you have another idea how to do that. Did you check your journalctl or dunst-service logs if the command raised any silent/logged errors in background? |
I found multiple errors using journalctl, they all look like this:
pre(copied from above):
post:
It seems that the pre-lock and post-lock function are executed at the same time? Is it the main cause? |
I think there is the bug - it seems that https://github.com/betterlockscreen/betterlockscreen/blob/next/betterlockscreen#L858C1-L858C12 overwrites the https://github.com/betterlockscreen/betterlockscreen/blob/next/betterlockscreen#L850 additionally lockargs does not exist at the time of the addition. can you move |
Log:
Dunst is still sending message to locked screen :( and the output of the two date are still identical(I have waited for a while in the locked screen) |
Moving the Before:
After:
|
Oh yes, moving |
Also, it seems that the program would only seek for I believe the fix for this problem should be easy, just deprecate the previous config dir or seek custom scripts in both two dirs. |
…sh only from betterlockscreen XDG-dir not ~/.config/, Prepare for v4.2.0 release
Hey, can please everyone having issues try the pull-request #395 and let me know if it fixes your issues so I can make a release? |
Both pausing dunst and executing custom pre/post script works perfectly for me. Thanks! :) |
Seems to work, though after a suspend the screen is shown for a second before the lockscreen appears. But that's probably more on my side. Thanks :) |
Is there an existing issue for this?
Operating system
Arch linux, 6.3.7-arch1-1
Installation method
Package Manager (from OS)
Betterlockscreen & Dependency-Versions
Betterlockscreen: version: v4.0.4 (dunst: true, feh: true) i3lock: version 2.13.c.4 © 2010 Michael Stapelberg, © 2015 Cassandra Fox, © 2021 Raymond Li Version: ImageMagick 7.1.1-11 Q16-HDRI x86_64 21206 https://imagemagick.org Copyright: (C) 1999 ImageMagick Studio LLC License: https://imagemagick.org/script/license.php Features: Cipher DPC HDRI Modules OpenCL OpenMP(4.5) Delegates (built-in): bzlib cairo djvu fftw fontconfig freetype heic jbig jng jp2 jpeg jxl lcms lqr ltdl lzma openexr pangocairo png raqm raw rsvg tiff webp wmf x xml zip zlib Compiler: gcc (13.1) dunst version: 1.9.2 feh version 3.10 Compile-time switches: curl exif inotify help magic stat64 verscmp xinerama [B] Betterlockscreen
Bug description
Locking the screen does not pause notifications. It executes the prelock (including dunstcl pause) and then directly runs the postlock (dunstcl unpause), resulting in all notifications still being displayed.
It works correctly when suspending, notifications are still paused when the computer resumes.
I am not quite sure why you are not using
--nofork
. I found a few issues regarding this (#28, #47), the PR said it would break notification display, but I did not find any resolution. Currentlylockselect
never blocks and instead always forks.This leads to the behaviour, as
betterlockscreen/betterlockscreen
Line 302 in 5cb876d
As far as I understand the no-fork option was disabled for suspension. But the suspend command explicitly forks the
lockselect
method (which, as far as I can tell, it does not need to do currently.lockselect
forks, the additional&
doesn't do much):betterlockscreen/betterlockscreen
Line 298 in 5cb876d
Adding
--nofork
and keeping the fork (&
) in the suspend case seems to fix all problems for me, but I am sure there is a good reason it is the way it is? I could manually wrap my lock command indunstcl set-paused
, but it sounds like something betterlockscreen should be doing correctly in all cases.Steps to reproduce
betterlockscreen -l
Relevant log output
No response
The text was updated successfully, but these errors were encountered: