Bug#899377: xfce4-notifyd doesn't autostart with xfce session
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 /usr/share/dbus-1/services/org.xfce.xfce4-notifyd.Notifications.service Apparently the one in my home directory takes precedence over the system-wide ones. Torbjörn Andersson
Bug#899377: xfce4-notifyd doesn't autostart with xfce session
I don't know if I had the same bug, but I've also had problems with xfce4-notifyd lately in Debian sid: xfce4-notifyd wouldn't start, causing some programs (e.g. Thunderbird on startup and Thunar when unmounting an USB device) to stall for a while. I *think* the problem in my case was that I had two Notifications services installed: xfce4-notifyd and plasma-workspace. I guess it just picked the first one of these (alphabetically?), and the one in plasma-workspace did not play nice with Xfce. My first workaround was to install dunst, which perhaps worked because it was even earlier in the alphabet. My second was to remove /usr/share/dbus-1/services/org.kde.plasma.Notifications.service But I'm hoping there is a better way... Torbjörn Andersson
Bug#899377: xfce4-notifyd doesn't autostart with xfce session
-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 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'. So it's not that the service is not started, it's that it fails to start for some reason. We'll have to investigate that. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl0uF7sACgkQ3rYcyPpX RFuZuwgA7HqqLgzlzeyzqxOSAWsnirw0Kv8fS0VtCDsWkKk+4SMOLy94KARbfsKR 8/FVxwk3Bw1ONGL5anV0/NlyZv3Q0/T1lSvl9fAI0U+ED7I6EVtrs+C2sxXLBlPh Mq8wPg0wdJd0riPksA7daaezbatBjT8r5aX3/blKbFQUH4sI/9ym46WB/2eaaE9e yxENoJA+dLCLNqTc0y3HfqUy+K3GATrLXgmLUm26cEW/V90CrS3I1mt19auf/Vh8 ZfDZIQiTlvaW/l1JCzyACD4fhvI1fC8DCS1y5cj+dBImAgiYsgjRZJJ8yHx44rGL Syri6k7qOz0q9EFZm65M7B1UiqDYTg== =ZjmU -END PGP SIGNATURE-
Bug#899377: xfce4-notifyd doesn't autostart with xfce session
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] 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.
Bug#899377: xfce4-notifyd doesn't autostart with xfce session
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2018-05-23 at 15:49 +0200, Pavel Kreuzt wrote: > 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 for a > notification to be displayed (in my case nm-applet, qhen connecting to my > home network). Hi, as far as I can tell, xfce4-notifyd *should* be started on demand, when a notification is requested (it ships a DBus interface file at /usr/share/dbus- 1/services/org.xfce.xfce4-notifyd.Notifications.service which requests the org.freedesktop.Notifications) I'll have to check on a Buster install how it behaves, but it does work fine on sid at least. Can you check if you don't have another notification daemon installed which would prevent xfce4-notifyd beeing started, maybe? There might be better way, but grepping org.freedesktop.Notifications in /usr/share/dbus-1/services/*.service should give a start. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl0mTysACgkQ3rYcyPpX RFtdnQf+JIWx/O3jCaQPCn4cpeduThJdDpGsGReVFb5DwB9WVV8AFcWihGHwB831 VxXW4XnJOj5zpSTnyaSCdRoG3FNThv+tjiXLvMVNU890ylzpq2pmTIg6Z2CwtwmV gdzzz5BBvm7R19BvwTQS1TcoAPPPwvqf0eQwNPH+8cVaITxyDe9GfeJ1s1MJn8Wj 7UHbZdG7L/wH+TVd2cYMhRpwBbdGmQf2/4K3zLdUEygvIq7WHp27DOLkCITRkzP/ yg2xbl8EIDI2Y8iuTnR8McKOLtqWDz5F0FqkBOfQxubCq12oSpJPycqwN4tuVJpU pTLGUaBQxvVxwQhBWr+Xx5SiHeUvZA== =nIEB -END PGP SIGNATURE-
Bug#899377: xfce4-notifyd doesn't autostart with xfce session
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 workaround was provided on Xfce forums - add this command to the automatically started programs in the Session & Startup settings manager: systemctl --user start xfce4-notifyd -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xfce4-notifyd depends on: ii libatk1.0-0 2.30.0-2 ii libc62.28-10 ii libcairo-gobject21.16.0-4 ii libcairo21.16.0-4 ii libdbus-1-3 1.12.16-1 ii libdbus-glib-1-2 0.110-4 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2 ii libgtk-3-0 3.24.5-1 ii libnotify4 0.7.7-4 ii libpango-1.0-0 1.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libx11-6 2:1.6.7-1 ii libxfce4panel-2.0-4 4.12.2-1 ii libxfce4ui-2-0 4.12.1-3 ii libxfce4util74.12.1-3 ii libxfconf-0-24.12.1-1 Versions of packages xfce4-notifyd recommends: ii libnotify-bin 0.7.7-4 xfce4-notifyd suggests no packages. -- no debconf information
Bug#899377: xfce4-notifyd doesn't autostart with xfce session
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 for a notification to be displayed (in my case nm-applet, qhen connecting to my home network). Debian Buster x86_64 Versions of packages xfce4-notifyd depends on: ii libatk1.0-0 2.28.1-1 ii libc62.27-3 ii libcairo-gobject21.15.10-3 ii libcairo21.15.10-3 ii libdbus-1-3 1.12.8-2 ii libdbus-glib-1-2 0.110-2 ii libfribidi0 0.19.7-2 ii libgdk-pixbuf2.0-0 2.36.11-2 ii libglib2.0-0 2.56.1-2 ii libgtk-3-0 3.22.29-3 ii libnotify4 0.7.7-3 ii libpango-1.0-0 1.42.0-1 ii libpangocairo-1.0-0 1.42.0-1 ii libx11-6 2:1.6.5-1 ii libxfce4panel-2.0-4 4.12.2-1 ii libxfce4ui-2-0 4.12.1-3 ii libxfce4util74.12.1-3 ii libxfconf-0-24.12.1-1 Versions of packages xfce4-notifyd recommends: ii libnotify-bin 0.7.7-3 xfce4-notifyd suggests no packages. -- no debconf information
