I may already have strayed from the topic of this bug report (sorry
about that), but it looks like I was able to solve my problem by making
~/.local/share/dbus-1/services/org.xfce.xfce4-notifyd.Notifications.service
a symlink to
Processing control commands:
> retitle -1 xfce4-notifyd fails to start with DBus activation (Unable to init
> server)
Bug #899377 [xfce4-notifyd] xfce4-notifyd doesn't autostart with xfce session
Changed Bug title to 'xfce4-notifyd fails to start with DBus activation (Unable
to init server)'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: retitle -1 xfce4-notifyd fails to start with DBus activation (Unable
to init server)
On Sat, 2019-07-13 at 13:31 -0700, Bob Hauck wrote:
> Jul 13 13:29:28 robin xfce4-notifyd[2624]: Unable to init server: Could not
> connect: Connection
On Wed, 10 Jul 2019 22:48:43 +0200 Yves-Alexis Perez
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]
Package: xfce4-notifyd
Version: 0.4.3-1
Followup-For: Bug #899377
Dear Maintainer,
I can confirm this on Buster. Also, I think the severity of this bug is more
than normal because this causes major problems to many important desktop
features such as NetworkManager and volume control.
A
Package: xfce4-notifyd
Version: 0.4.2-1
Severity: normal
Dear Maintainer,
Since last upgrade xfce4-notifyd dowsn't start anymore with XFCE session, nor
it does when some program presses some notification. This also causes some odd
behaviour with some other apps which seem to "hang" awaiting
