Closed stepnem closed 3 months ago
I have same issue. (writing here just to get notifications)
I have same issue. (writing here just to get notifications)
You can click subscribe to receive notifications. No need to add a comment for that
@tobast What do you think of this and the proposed solution?
Whoops, I think I indeed introduced that. Basically, whenever the timer calls run()
, if there is no need to set a new timer, the previous timer ID was not cleared — and a subsequent run()
would later try to remove it, although it is now expired. See MR above.
@fwsmit hang on, now that I look at it a bit more, I don't understand how it passed my tests. There are more issues here, I need to think about it. Can you reopen this issue?
Okay, I'll reopen it :)
Maybe it's better to set the timeout id to zero when it's removed
Is this still happening?
Yes, it is not solved yet. Sorry, I did not find the time to focus on this recently, I'll try to do this soon.
With current master (commit a8b265094189) as well as latest release (Arch Linux package 1.9.2-1), I get error messages like the one in subject (only the number changes) for each notification after the first one since dunst started, as long as no other notification is being displayed. (IOW, the error does not seem to occur when a notification reuses another notification's window on screen.)
No config involved (started as dunst -conf - </dev/null), but happens with my usual configuration as well.
No desktop environment (startx with XMonad window manager).
glib2 version 2.76.4-1 (Arch Linux package)
I've stopped the log spam (with no ill effects) with the following patch:
But that's most likely not the solution, just stopping the symptom. Quoting https://docs.gtk.org/glib/type_func.Source.remove.html:
It is a programmer error to attempt to remove a non-existent source.
Dunst seems to be doing just that. Unfortunately I'm not familiar with dunst code base or GLib and am unlikely to be of much further help any time soon.
Here's a GDB backtrace at time of writing the error message: