Closed jebotz closed 3 years ago
OK, well, doh. It's doing exactly what it's supposed to be doing... the problem is that for some reason it's not getting started in the first place by d-bus. I'll investigate further, but for now this doesn't seem to be a mate-notification-daemon bug; most likely a Fedora packaging issue.
On Fedora 32 I noticed that I wasn't getting notifications, so I checked and saw that the daemon wasn't running. Starting it by hand makes it work and actually handle notifications, but it exits after being idle for exactly 30 seconds. Note that so long as there are notification events it does not exit... it exits 30 seconds after the last event.
Also, I've rebuilt it from latest github source and it still does the same thing.
Running it with --debug gives the following:
...and again it exits after 30 seconds. Running it with strace gives the following (last few lines):
Expected behaviour
daemon handles notifications
Actual behaviour
daemon exits without error exactly 30 seconds after starting
Steps to reproduce the behaviour
/usr/libexec/mate-notification-daemon
MATE general version
1.24.1
Package version
mate-notification-daemon-1.24.1-1.fc32
Linux Distribution
Fedora 32
Link to downstream report of your Distribution