Notifications eventually stop showing up on wayland/sway #1066
Labels
Comments
|
Thank you for the bug report! I have seen the same thing a couple times after running dunst for a while, but i dont do that often, so I haven't looked into it yet. I dont think th pause function is at fault here, but instead something wayland-specific. Thank you for your time and I hope we can fix this issue |
|
A few more things to note: |
|
Since some time I noticed this too. I'm running hikari. My deduction was, it had something to do with wlroots 0.15 and the compositor in question, as I did a git bisect on dunst back to the time where Wayland support was introduced and could always reproduce the problem. |
|
It might still be a bug present in the initial dunst wayland implementation. But since it has only been reproduced on sway afaik, it's only guessing at this point. The debug info mentioned above would probably narrow it down. |
|
That may be, but then it only appeared with wlroots 0.15. This behaviour wasn't there with previous versions. And I use dunst and its wayland integration from the beginning. And as written: Can easily reproduce on a different compositor: Log (fairly long, at the end were dunst doesn't appear anymore): Logs |
|
@Narrat could you please move the log of yours either to a gist or wrap it in <details>
<summary>Logs</summary>
```
logs
```
</details>? So recently there have been a couple confirmations that switching to git mako helps with it not being able to show anything, anymore. I have looked through the change history in mako and there aren't all that many changes to look through. emersion/mako@6caaa55 seems like the only relevant change. These are the relevant-looking commits: all pretty small, and all look like something dunst would want to integrate one way or another. |
|
Thank you both for the investigation.
Done
If that's the case, that would be great, since dunst and mako have pretty much identical wayland implementations. I'll make a branch applying all the patches that have been made to mako's wayland file. When that's done, could you test it to see if that fixes it? |
Merged
|
I've made a PR (#1067), although I'm sceptical this fixes the bug, since the first two patches are meant to fix am memory leak and the other applies to same-size reconfigures. But testing to see if it helps would be appreciated. |
|
I also affected with this bug for sometime. I'll test the PR today |
|
Has anyone noticed a difference with #1067? |
|
I've been using the patch for four days uptime. The notifications are still showing up so far, which is good. Might need more tester though |
|
I've merged #1067. If you see this problem again in current dunst-git or later, let me know and I'll reopen this issue. |
|
Will also test a build from git when I'm around one of my systems. Which may take some time. Not that much around. |
|
FWIW for me the issue went away before I could apply the patch, so it might very well be the case that it was indeed an issue in some other component (sway or wlroots perhaps.) |
|
As I could produce this behaviour frequently and now with a build from master not... It indeed seems to be fixed :) |
|
Great! |
|
I got this bug again with the latest dunst-git. Anyone else noticed it again? |
|
Nvm, wrong issue. You can ignore the comment. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue description
I have recently switched from mako to dunst due to emersion/mako#404, and dunst was working quite well for me until after a couple days of runtime
dunststopped showing notifications too!I'm not entirely sure at this point if this is an issue with dunst or sway (the wayland compositor I use), but I have been running both with debug logging enabled and was able to reproduce the issue just now.
When I run
notify-send -t5, the following output fromdunstctlis visible:That is – the dunst appears to be operating as usual.
However I don't see any notifications and sway's logs show no sign of any windows being created like for example these I otherwise would see when things work normally:
So in short, wayland surfaces aren't getting created, but dunst does not surface any errors in its own logs either.
I utilize
set-pausedfunctionality to stop notifications from showing up when the screen is locked, but runningdunstctl is-pausedreturnsfalse. Is there a reason to believe use of thepausefunctionality could be to blame here?Any advise for further troubleshooting would be greatly appreciated
Installation info
I haven't attempted to minify the configuration yet.
dunstrc
The text was updated successfully, but these errors were encountered: