SUMMARY I am running KDEConnect independently of Plasma/KWin as part of my own workflow, with dunst as my notification daemon. However KDEConnect breaks dunst's action support, and the dunst developers have suggested getting more information here. Dunst issue on Github (I am @xPMo): https://github.com/dunst-project/dunst/issues/575 Especially note this comment: https://github.com/dunst-project/dunst/issues/575#issuecomment-505275604 STEPS TO REPRODUCE 1. Run KDEConnect on Linux with a device connected 2. Run dunst as a notification daemon 3. Get a property from the device (with qdbus/dbus-send/kdeconnnect-indicator) 4. Recieve an actionable notification 5. Perform the keyboard shortcut to show/take the action in dunst 6. Select an action OBSERVED RESULT The notification is not dismissed, the action is not taken. EXPECTED RESULT The notification is dismissed; the action is taken. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.2.0-arch2-1-ARCH/none kdeclarative: 5.60.0-1 Qt Version: 5.13.0-7
This seems to be caused by the DBus eavesdropping done by the "Send notifications to phone" feature. Somehow it makes DBus things go wrong. A workaround is to disable/not enable the "Send Notifications" feature. I'm not sure how a proper, cross-desktop solution would look like