Bug 381693 - org.kde.plasma.Notifications.service conflicts with org.xfce.xfce4-notifyd.Notifications.service
Summary: org.kde.plasma.Notifications.service conflicts with org.xfce.xfce4-notifyd.No...
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.10.0
Platform: Archlinux Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
Depends on:
Reported: 2017-06-26 18:16 UTC by David Rosenstrauch
Modified: 2020-05-08 10:04 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description David Rosenstrauch 2017-06-26 18:16:09 UTC
I run XFCE as my DE, and use xfce4-notifyd for notifications.  However, I also keep most of the KDE packages installed, as I often use several KDE apps.

The recent upgrade of the plasma-workspace package (from v5.9.5.1 to v5.10.0) broke notification on my system.  The cause seems to be the inclusion of the new dbus org.kde.plasma.Notifications.service file.  The presence of that new file causes dbus to try to perform notifications using plasma (even though I don't have plasma running) rather than using xfce4-notifyd and so all notifications are failing / timing out.

There doesn't seem to be any fix for this other than either removing the plasma-workspace package - and half of KDE along with it, due to dependencies - or hand-editing the file to comment out its contents so that it won't get called by dbus for notifications.  I chose the 2nd option for now, but neither option is really a proper fix.

Since that new org.kde.plasma.Notifications.service is what caused the breakage, I'd think that a proper fix might require some re-thinking about the use of that file, and how to make it work properly when other DE's are present and/or running.
Comment 1 David Rosenstrauch 2017-06-26 18:17:36 UTC
Sorry - forgot to include the error message that DBus gives:

Jun 23 16:55:27 darosedm dbus-daemon[723]: Activating service name='org.freedesktop.Notifications'
Jun 23 16:56:27 darosedm plasma_waitforname[1988]: org.kde.knotifications: WaitForName: Service was not registered within timeout
Jun 23 16:56:27 darosedm dbus-daemon[723]: Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1

The correct functioning looks like so:

Jun 26 12:19:31 darosedm dbus-daemon[640]: Activating via systemd: service name='org.freedesktop.Notifications' unit='xfce4-notifyd.service'
Jun 26 12:19:31 darosedm systemd[614]: Starting XFCE notifications service...
Jun 26 12:19:31 darosedm dbus-daemon[640]: Successfully activated service 'org.freedesktop.Notifications'
Jun 26 12:19:31 darosedm systemd[614]: Started XFCE notifications service.
Comment 2 David Edmundson 2017-06-26 22:01:54 UTC
There is a proposed fix in newer DBus where we will copy service files into /run somewhere and have this solvable per session.

Till then DBus activation with two desktops is a slighlty rubbish area and there is no good fix.

You can solve it by autostarting xfce-notifyd with your session 
also you can override .service files in your ~/.local/share.
Comment 3 Aleksandar Kostadinov 2020-05-08 10:04:35 UTC
Where is this D-Bus upstream proposal for a fix? After 2 years and a half this still continues to be the same problem.