Skip to content
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

Notifications in dunst stick and don't timeout #483

Open
marcusorjames opened this issue Oct 10, 2019 · 4 comments
Open

Notifications in dunst stick and don't timeout #483

marcusorjames opened this issue Oct 10, 2019 · 4 comments

Comments

@marcusorjames
Copy link

I'm not sure if this is specifically a dunst issue or for any notification system, but my chat notifications never timeout. The urgency seems to be set to normal which is fine and my timeout is set to 4 seconds, which all other normal urgency notifications abide by. Hangups just sticks forever until I open hangups and the message marks as read.

Happy for this to be a flag, if the default behaviour is for it to stick until read.

Thanks for an otherwise fantastic application.

Running Ubuntu 18.04, Dunst 1.3.0

@tdryer
Copy link
Owner

tdryer commented Nov 2, 2019

Currently hangups is setting the timeout to -1. According to the spec this means:

the notification's expiration time is dependent on the notification server's settings, and may vary for the type of notification.

We could certainly add a flag for this.

@marcusorjames
Copy link
Author

Interesting, so if that's the case then it should be abiding by my settings, but this is not what I am seeing. I'm not sure setting a flag is a good idea, it might just be my environment ignoring the -1.

@Terrance
Copy link
Contributor

Terrance commented Nov 4, 2019

'{summary}', '{body}', '[]', '{{}}', ' -1'

Is the leading space in that argument intentional? Might it be causing DBus to parse it badly?

@tdryer
Copy link
Owner

tdryer commented Nov 17, 2019

The leading space is required for some reason. According to dbus-monitor the value is parsed correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants