vpilo added a comment.
In https://phabricator.kde.org/D4799#90169, @dfaure wrote: > About the code in kded that calls ksplash: that code is obsolete and currently only kept for compatibility reasons, see https://git.reviewboard.kde.org/r/129010/ > IOW you can ignore that code completely. OK, thanks :) In https://phabricator.kde.org/D4799#90165, @broulik wrote: > Most are not, however. PowerDevil, for instance, actually delays its notifications (e.g. you startup with a low battery) until a notification service registers itself to avoid the embarrassing popup ontop of KSplash while still showing the notification soon after logging in. Almost anything else ("You are now connected to network X") is pointless, and I hate this Yakuake notification when logging in. All notifications can be disabled if the user finds them useless and/or annoying - not a reason to prevent them from showing at all by means of frameworks, though, IMHO. And we can't expect the applications to all do what PowerDevil does. Unless we make this change happen (with another trigger to decide whether the splash is being shown). REPOSITORY R289 KNotifications REVISION DETAIL https://phabricator.kde.org/D4799 EMAIL PREFERENCES https://phabricator.kde.org/settings/panel/emailpreferences/ To: vpilo Cc: dfaure, broulik, graesslin, mck182, #frameworks
