Bug 904985 – x11-misc/dunst-1.9.1 doesn't start with dbus

• Product: Gentoo Linux
• Status: RESOLVED CANTFIX

[Description zen 2023-04-24 22:13:00 UTC]

The install makes "org.knopwob.dunst.service" under "/usr/share/dbus-1/services" with contents:
[D-BUS Service]
Name=org.freedesktop.Flatpak
Exec=/usr/libexec/flatpak-session-helper
SystemdService=flatpak-session-helper.service

But the dunst doesn't start when I run `dbus-run-session sway` and trying to trigger notifications results in "Unable to send notification: Error calling StartServiceByName for org.freedesktop.Notifications: Process org.freedesktop.Notifications received signal 5"

[Comment 1 zen 2023-04-24 23:28:30 UTC]

(In reply to zen from comment #0)
> The install makes "org.knopwob.dunst.service" under
> "/usr/share/dbus-1/services" with contents:
> [D-BUS Service]
> Name=org.freedesktop.Flatpak
> Exec=/usr/libexec/flatpak-session-helper
> SystemdService=flatpak-session-helper.service
> 
> But the dunst doesn't start when I run `dbus-run-session sway` and trying to
> trigger notifications results in "Unable to send notification: Error calling
> StartServiceByName for org.freedesktop.Notifications: Process
> org.freedesktop.Notifications received signal 5"

The following is in sway's error output, similar errors for other programs attempting to push notifications


(plexamp:3): libnotify-WARNING **: 18:23:30.077: Failed to connect to proxy
dbus-daemon[6038]: [session uid=1000 pid=6038] Activating service name='org.freedesktop.Notifications' requested by ':1.19' (uid=1000 pid=6191 comm="xdg-dbus-proxy --args=41")
WARNING: Cannot open X11 display.
ERROR: [  get_x11_output:0065] Couldn't initialize X11 output. Aborting...
dbus-daemon[6038]: [session uid=1000 pid=6038] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications received signal 5

[Comment 2 Alexis 2023-04-25 00:28:55 UTC]

That service file isn't right. It should be:

    [D-BUS Service]
    Name=org.freedesktop.Notifications
    Exec=/usr/bin/dunst
    SystemdService=dunst.service

As it is on my system, for dunst-1.9.1.

Your service file looks like one that might have been installed via Flatpak? Did you install dunst using `emerge`?

[Comment 3 zen 2023-04-25 00:38:49 UTC]

(In reply to zen from comment #0)
> The install makes "org.knopwob.dunst.service" under
> "/usr/share/dbus-1/services" with contents:
> [D-BUS Service]
> Name=org.freedesktop.Flatpak
> Exec=/usr/libexec/flatpak-session-helper
> SystemdService=flatpak-session-helper.service
> 
> But the dunst doesn't start when I run `dbus-run-session sway` and trying to
> trigger notifications results in "Unable to send notification: Error calling
> StartServiceByName for org.freedesktop.Notifications: Process
> org.freedesktop.Notifications received signal 5"

I pasted the wrong thing, these are the actual contents: 

> cat /usr/share/dbus-1/services/org.knopwob.dunst.service
[D-BUS Service]
Name=org.freedesktop.Notifications
Exec=/usr/bin/dunst
SystemdService=dunst.service

[Comment 4 Conrad Kostecki 2023-05-07 12:35:50 UTC]

Did you also test 1.9.2?

[Comment 5 zen 2023-05-26 00:12:30 UTC]

(In reply to Conrad Kostecki from comment #4)
> Did you also test 1.9.2?

I have not(In reply to Conrad Kostecki from comment #4)
> Did you also test 1.9.2?

i have, it seems i have to start it with sway, and i think the reason is because dusnt requires an active wayland display to start.  I'm starting sway from tty1

[Comment 6 Conrad Kostecki 2023-05-31 15:47:02 UTC]

Well, in this case, I don't see, what I could do here. The ebuild just install dunst, but starting is managed by the user. I would recommend to open a ticket for upstream in this case.