D5968: Fix co-installability with other DBus activated notification services

David Edmundson noreply at phabricator.kde.org
Thu May 25 07:51:13 UTC 2017


davidedmundson created this revision.
Restricted Application added a project: Plasma.
Restricted Application added a subscriber: plasma-devel.

REVISION SUMMARY
  In Plasma we install a DBus activated service to handle the case of
  notifications being sent before Plasma is loaded. This file clashes with
  other notification daemons and causes distro issues.
  
  The convention is to make this file name match the DBus service name so
  that we can detect conflicts, however in this case we know we have an
  unavoidable conflict, but it doesn't really have an repurcisions other
  than the user having an undetermined notification daemon chosen during
  plasma bootup (which was the case before this patch too)
  
  Effectively it's the same problem we have with the
  org.freedesktop.FileManager1 service and Dolphin, and the same solution.

TEST PLAN
  Installed this
  kquitapp5 plasmashell
  notify-send some message. Confirmed it waited
  started plasmashell. Got the message

REPOSITORY
  R120 Plasma Workspace

BRANCH
  master

REVISION DETAIL
  https://phabricator.kde.org/D5968

AFFECTED FILES
  startkde/waitforname/CMakeLists.txt
  startkde/waitforname/org.freedesktop.Notifications.service.in
  startkde/waitforname/org.kde.plasma.Notifications.service.in

To: davidedmundson, #plasma
Cc: plasma-devel, ZrenBot, spstarr, progwolff, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, mart, lukas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20170525/2ba3a022/attachment.html>


More information about the Plasma-devel mailing list