-
Notifications
You must be signed in to change notification settings - Fork 342
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
After running for several days, dunst no longer displays notifications #1186
Comments
Try to list coredumps to see if dunst crashed:
If it did, make sure gdb is installed and set the following environment variable:
And run:
gdb will download all the required symbols from the debuginfod server, and at some point you will be dropped into a gdb shell, run the |
Thanks for the response! It took some time to reproduce again, but just today I confirmed notifications are not showing up. I did not have It returns
but I'm not familiar with the tool (I could imagine it would only work if it is installed during a crash). I don't think it crashed though, given that is still appears in the list of running processes:
Is there anything else I should try now, or just go ahead and manually kill and relaunch as I did before and check for coredumps again the next time it stops displaying notifications? |
Correct You might also want to check man systemd-coredump, enabling the service might be required if it's not already.
Doesn't mean it didn't crash, dunst is automatically invoked by dbus if it's not already running when a notification is received. You might want to check the output of |
I believe it was automatically enabled when I installed it based on the return value of this command:
I also tested by sending
Ah good to know. I have tested with multiple notifications once I notice one that didn't come through though. (My thinking here being that if the only problem was that dunst crashed, and then was restarted by the next notification, it would seem that the restart would fix the issue, and then subsequent notifications should be displayed without issue -- which doesn't match observations). But I suppose something could happen that gets even the relaunched dunst into a bad state, but it's curious that manually killing that dunst process and relaunching seems to be a temporary fix.
Thanks! You are correct, there are three status=1/Failure messages. Here is the full output:
|
I'll go ahead and restart the service today if there is nothing further we can glean from this instance and update again when/if I next observe a missed notification, and will upload any applicable core dumps. |
and
Seem to suggest that you spawned multiple X11 servers, was it intended behavior ? If it was not, I would try to understand why it's happening. |
Did it happen again? If not I think this issue can be closed. It could be something weird about your setup if there are issues connecting to Xorg |
Yes, I can reliably reproduce this issue given a few days. I am still able to fix by killing and restarting dunst. After Shell suggested multiple X11 servers I reached out to the xorg list. On Tuesday I can check the logs mentioned in this reply again. The other reply suggests that this must be happening locally, but that multiple logins could create multiple X11 servers. There is only one use account on the machine in question, so the only idea I have is that perhaps something strange is going on with the screen lock, resulting in multiple logins -> multiple X11 servers -> problems for dunst until relaunched. This doesn't seem to match the observations though, since entering the password at the lock screen seems to bring back the exact state the session was left in beyond the passage of time. |
A workaround would be to set the service to restart when it fails in systemd (Restart=always) |
Did you resolve it in the end? |
Issue description
The first time this happened, I thought it was a fluke. It has now happened a second time.
After several days (will get a more accurate estimate in a few days) dunst claims to be working, but no notifications are displayed.
A short-term workaround is to manually kill dunst and relaunch.
Installation info
1.9.0 (2022-06-27)
Configuration Details
dunstrc have not created a custom dunstrc, using the builtin default.
Repro (after waiting several days)
After noticing the issue had recurred again today, I set about trying to determine the cause.
No stdout or stderr, no popup displayed.
No popup displayed.
Test with browser notifications:
No notification (not in chrome nor dunst / system popup).
Web page output:
Also tried this in firefox. Same exact result.
Debugging Attempts
Confirm dunst is running.
Try the debug command, ensure not paused.
Check status.
Check dunst server info.
Used the following to kill and attempt to relaunch:
While the initial attempt to kill and failed, relaunching with systemctl is successful.
Now all notifications work. Will update with details of if I am able to reproduce which action causes notifications to stop working again after several days.
The text was updated successfully, but these errors were encountered: