Some recent package upgrade seems to be causing xfce4-notifyd to mysteriously crash, with no info available in the logs as to why. This started happening within the last couple of weeks. : * Start XFCE (from lightdm via startxfce4) * xfce4-notifyd seems to either fail to automatically start, or to crash soon after start: $ ps ax | grep notify; date 3017 pts/2 S+ 0:00 grep notify Wed Jun 21 11:04:48 EDT 2017 * Start xfce4-notifyd manually. Observe that it is running: $ systemctl --user start xfce4-notifyd.service $ ps ax | grep notify; date 3020 ? Ssl 0:00 /usr/lib/xfce4/notifyd/xfce4-notifyd 3026 pts/2 S+ 0:00 grep notify Wed Jun 21 11:04:53 EDT 2017 * At some point later it shuts down: $ ps ax | grep notify; date 6141 pts/2 S+ 0:00 grep notify Wed Jun 21 14:06:43 EDT 2017 * So I restart again $ systemctl --user start xfce4-notifyd.service * There's no indication in the logs as to why it crashed: $ sudo grep notif /var/log/messages.log ... Jun 21 11:04:50 darosedm systemd[602]: Starting XFCE notifications service... Jun 21 11:04:50 darosedm systemd[602]: Started XFCE notifications service. Jun 21 11:14:18 darosedm nm-openvpn[3259]: Option 'explicit-exit-notify' in [PUSH-OPTIONS]:1 is ignored by previous <connection> blocks Jun 21 14:06:46 darosedm systemd[602]: Starting XFCE notifications service... Jun 21 14:06:46 darosedm systemd[602]: Started XFCE notifications service. I'm running: * Arch Linux * XFCE 4.12.1 * xfce4-notifyd 0.3.6 * Kernel 4.11.6
Hi, this behavior is not as mysterious as it may seem, but was actually an intentional feature that was always present in xfce4-notifyd. I have recently dropped it as I don't feel there are any good arguments for a service that consumes so few resources to not be running. See also https://bugzilla.xfce.org/show_bug.cgi?id=12754 and https://git.xfce.org/apps/xfce4-notifyd/commit/?id=d87a4a93b2ec4ab094f5a35ae818395f750f2891 So it will be part of the next release. *** This bug has been marked as a duplicate of bug 12754 ***
Makes sense ... somewhat. But why would this issue only be manifesting itself recently? I've been using xfce4-notifyd-0.3.6 since March but I'm pretty sure this issue has only been present in the last few weeks.
BTW, the issue I'm referring to is that events that trigger notification (e.g., pressing the screen brightness keys, increasing the volume via the volume control widget, etc.) have recently started getting stuck waiting on the notification service and eventually timing out. That wasn't happening before.
I guess notifyd is having problems restarting, not sure why that would be (although the duplicate bugreport mentions systemd failing to restart it, so maybe some change in systemd causes this problem for you now as well). You could still try to build and install from git master and see whether that fixes your problem.
(In reply to Simon Steinbeiss from comment #1) > Hi, > this behavior is not as mysterious as it may seem, but was actually an > intentional feature that was always present in xfce4-notifyd. > I have recently dropped it as I don't feel there are any good arguments for > a service that consumes so few resources to not be running. > > See also > https://bugzilla.xfce.org/show_bug.cgi?id=12754 > and > https://git.xfce.org/apps/xfce4-notifyd/commit/ > ?id=d87a4a93b2ec4ab094f5a35ae818395f750f2891 > > So it will be part of the next release. > > *** This bug has been marked as a duplicate of bug 12754 *** BTW, any idea when this fix might get released in a new version of xfce4-notifyd? Thanks, DR