https://bugs.kde.org/show_bug.cgi?id=506236
--- Comment #2 from Ismael Asensio <[email protected]> --- Got a hint of what's going on. Apps that don't have a custom .notifyrc config file (such as 3rd party apps using the notification service) actually use a plasma_workspace event. When pressing "configure" over such notification, the kcm receives this as an argument, and gets misleaded: It tries to configure the app from the desktop entry (ex. Spotify), but it opens in "system notifications" mode with no events to configure. For a Spotify notification, the KCM is receiving these arguments: kcm_notifications --desktop-entry com.spotify.Client --notifyrc plasma_workspace --event-id notification Or when clearing the trash in dolphin: kcm_notifications --desktop-entry org.kde.dolphin --notifyrc plasma_workspace --event-id 'Trash: emptied' Not sure yet where to try and fix this issue. In the first case we'd want to open the notification settings for "Spotify", but on the second one I think it's better to actually open the system notifications for the trash event. But we're mixing both and failing to show the right configuration in both cases. -- You are receiving this mail because: You are watching all bug changes.
