-
Notifications
You must be signed in to change notification settings - Fork 336
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
Can't force timeout on notifications from web browser. #1283
Comments
The error you see is solved in master. Not sure if that's the cause, though |
I built and installed the latest version of dunst and now
And the issue of the telegram web notification not timing out is still present. |
It seems the timeout set by the browser is overriding the default one you set. Maybe you could try using a rule that sets the timeout to notifications sent by the browser? |
I tried this before and didn't work, but now I can't try it again because how do I get the appname now? before Sorry for the late reply, the email was sent to my junk. UPDATE: I was able to get the appname again by simply reading the original log I posted here lol, I added this my dunstrc config:
And it is "working" because the background color for the notifications does change to the one I have set there, however the timeout of 1 second doesn't work still. |
When using telegram web on the browser (brave) notifications don't timeout at the time I have set in my dunst configuration.
When looking at
dunst --print
There's an error for the notifications of the web browser:Installation info
Dunst - A customizable and lightweight notification-daemon 1.9.2 (2023-04-20)
Arch Package
i3wm
Archlinux
Dunstrc here
The text was updated successfully, but these errors were encountered: