You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tag: Branch: Tree: b57a7419a6

wilder

wilder-5.14

wilder-5.17

wilder-5.18

wilder-5.19

wilder-5.22

wilder-5.24

wilder-5.25

wilder-5.26

wilder-5.26-rebase

wilder-broken-krunner

wilder-portage

wilder-portage-prov

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'b57a7419a6'

${ noResults }

plasma-workspace/startkde/waitforname

History

David Edmundson ab60c3be74 Fix co-installability with other DBus activated notification services ... 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 Reviewers: #plasma, mart Reviewed By: #plasma, mart Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D5968		9 years ago
..
CMakeLists.txt	Fix co-installability with other DBus activated notification services	9 years ago
main.cpp	…
org.kde.plasma.Notifications.service.in	Fix co-installability with other DBus activated notification services	9 years ago
waiter.cpp	…
waiter.h	…