*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY kded takes primary ownership of StatusNotifierWatcher when spawned under non-plasma desktop environment. STEPS TO REPRODUCE 1. Run a desktop environment other than plasma. 2. Spawn an application that triggers kded service startup. 3. Restart existing (non-kded) StatusNotifierWatcher application (or attempt to start SNW application after kded has spawned during DE startup). OBSERVED RESULT kded takes primary ownership of StatusNotifierWatcher, even though it can do nothing useful with it, preventing other applications from taking ownership of the bus. EXPECTED RESULT kded must not attempt to own StatusNotifierWatcher (or similar buses) when not spawned under plasma, or at minimum should provide some mechanism to disable this functionality, since kded service is automatically started as a side-effect of starting various KDE applications. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.19.0 Qt Version: 6.10.0 ADDITIONAL INFORMATION