On Wed, 10 Jul 2019 22:48:43 +0200 Yves-Alexis Perez <[email protected]> wrote:
> I'll have to check on a Buster install how it behaves, but it does work fine > on sid at least. On Buster, just upgraded from Stretch /var/log/daemon.log has: Jul 13 13:29:28 robin dbus-daemon[1285]: [session uid=514801104 pid=1285] Activating via systemd: service name='org.freedesktop.Notifications' unit='xfce4-notifyd.service' requested by ':1.65' (uid=514801104 pid=2619 comm="xfce4-notifyd-config --socket-id=23069188 ") Jul 13 13:29:28 robin systemd[1253]: Starting XFCE notifications service... Jul 13 13:29:28 robin xfce4-notifyd[2624]: Unable to init server: Could not connect: Connection refused Jul 13 13:29:28 robin systemd[1253]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE Jul 13 13:29:28 robin systemd[1253]: xfce4-notifyd.service: Failed with result 'exit-code'. Jul 13 13:29:28 robin systemd[1253]: Failed to start XFCE notifications service. > Can you check if you don't have another notification daemon installed which > would prevent xfce4-notifyd beeing started, maybe? None are installed. No other desktops are installed either. Turning off apparmor makes no difference. Sending a test notification from the setitngs panel fails as well with the same error messages and the top of the window has an orange banner saying that the service is not running.
