Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 758089 - sys-apps/dbus?: x11-misc/notify-osd and x11-misc/notification-daemon: Activated service 'org.freedesktop.Notifications' failed
Summary: sys-apps/dbus?: x11-misc/notify-osd and x11-misc/notification-daemon: Activat...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal with 1 vote (vote)
Assignee: Freedesktop bugs
Depends on:
Reported: 2020-12-02 18:09 UTC by segmentation fault
Modified: 2020-12-02 23:28 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description segmentation fault 2020-12-02 18:09:43 UTC

This is a "bug" (or issue, if you prefer) with a solution, so feel free to set its status to "resolved" immediately. It affects both packages


but, actually, the problem lies elsewhere (dbus?). However, most people will expect the problem to be in those two packages, that's why I am filing it under their names.


Suppose you installed one of the two notification daemons above. Suppose also that you don't run their "standard" window managers - i.e. you run neither GNOME, nor xfce. I run fvwm, you may be running something else. Actually, it should not matter. Suppose further that you have KDE installed, but you don't run it (currently, in your session).

Now, try to send a notification to yourself by typing in a X terminal:

notify-send test test

Nothing happens and syslog shows:

Activating service name='org.freedesktop.Notifications' requested by...
Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1

This happens with any of the two notification daemons above (you can't have both installed at the same time).


The notification daemon does not start. BUT: the file that controls the start of the notification daemon, namely


is correct! There is nothing wrong with it: in each case it contains the right path to the daemon. It is the job of dbus to start it with this information automatically - but it does not.

The real reason here is that there exists another *.Notifications.service file, which (for some reason) takes precedence over the one above:


Dbus seems to try to start the notification daemon with the information from *this* (KDE Plasma) file, rather than the one from your installed notification package. Therefore, it tries to start

/usr/bin/plasma_waitforname org.freedesktop.Notifications

and, of course, it fails.


A true solution would be to fix the order of precedence of *.Notifications.service files to conform to the user's situation, but this is not done.

As a workaround, try renaming


to, say,


Voila! Notifications suddenly work! :-)

See also

I hope this helps somebody with the same problem - I spent half a day chasing it...
Comment 1 Jonas Stein gentoo-dev 2020-12-02 23:28:20 UTC
@freedesktop-bugs do you have an idea/solution how to proceed here?