On 21-06-2017 20:16, David Rosenstrauch wrote: > On 06/21/2017 03:07 PM, Bjoern Franke wrote: >> Am 21.06.2017 um 14:17 schrieb David Barri via arch-general: >>> Broke for me recently too. I had to add this to my .xinitrc: >>> >>> systemctl --user start xfce4-notifyd.service >>> >> >> Which DE are you using? With XFCE, it's autostarted here, not need for >> systemctl --user. >> >> Regards >> Bjoern > > I (the original reporter) am running XFCE. > > I've done a bit of research on the issue. Seems like what's happening is: > > a) Apparently xfce4-notifyd intentionally (!) shuts itself down after 10 > mins of inactivity (see > https://bugzilla.xfce.org/show_bug.cgi?id=12754). However, it's had > this behavior for quite some time (since v0.3.0 - we're now at 0.3.6), > so I don't think this is the source of the issue. > > b) It looks like what changed recently is that for some reason dbus is > no longer able to automatically restart xfce4-notifyd when a > notification happens. See what I get when I issue "notify-send 'test'": > > Jun 21 15:08:16 darosedm dbus-daemon[628]: Activating service > name='org.freedesktop.Notifications' > Jun 21 15:09:16 darosedm plasma_waitforname[7097]: > org.kde.knotifications: WaitForName: Service was not registered within > timeout > Jun 21 15:09:16 darosedm dbus-daemon[628]: Activated service > 'org.freedesktop.Notifications' failed: Process > org.freedesktop.Notifications exited with status 1 > > I haven't quite pinned down what's causing the restart to fail yet. If > anyone has any relevant info, please do share. > It's working fine here. I don't use a login manager, I login from a tty and I haven't changed any configuration in a long while. I also don't do anything special to launch xfce or anything else. my .xinitrc has: if [ -d /etc/X11/xinit/xinitrc.d ]; then for f in /etc/X11/xinit/xinitrc.d/*; do [ -x "$f" ] && . "$f" done unset f fi exec startxfce4 and that's all. -- Mauro Santos
