https://bugs.kde.org/show_bug.cgi?id=420635
--- Comment #28 from Brian Wright <b...@briandwright.com> --- (In reply to Konrad Materka from comment #27) > Have you tried fresh user account on your local system? Yes, I have. Everything works as it should. I backed up my personal home directory, nuked it, and then started fresh. Everything worked OK, until I restored some of my app data. With the test account, I will be keeping it pristine except for the apps that I need to autostart. > Thank you! Other people are/were affected, reinstall helped but IMO that's > not a proper solution. A reinstall should only take place if the system is not working, period. :-) > > Let's investigate it further... > > * I modified listIcons.sh script, now it outputs PID, path and start time. > Can you run it again when icons are not registered? org.kde.StatusNotifierWatcher pid,start,command: 29782 13:36:26 kded5 ITEMS: ITEM: :1.40/org/ayatana/NotificationItem/pasystray PID STAT: 31350 13:36:27 /usr/bin/pasystray ID: pasystray TITLE: pasystray ITEM: :1.91/StatusNotifierItem PID STAT: 31134 13:36:27 /usr/bin/xembedsniproxy ID: pasystray TITLE: pasystray ITEM: :1.102/StatusNotifierItem PID STAT: 7545 13:36:58 /usr/bin/kalarm --tray ID: KAlarm TITLE: KAlarm Result - Kmix, DiscoverNotifer, Slack, Skype, KeepassXC, HP-Systray Dropbox icons are not in the system tray. PasSystray duplicated. > * Please find in logs the time when StatusNotifierHost was registered. On my > system, I've run: > journalctl -b 0 | grep StatusNotifierHost May 10 13:35:32 bdw-desktop kded5[4104]: Registering "org.kde.StatusNotifierHost-9430" as system tray May 10 13:37:18 bdw-desktop kded5[29782]: Registering "org.kde.StatusNotifierHost-31127" as system tray > > * In system settings, can you disable all background service and leave only > one enabled: Status Notifier Manager? Then restart. Maybe something is > blocking Status Notifier Manager service during startup. Disabling all background services except for Status Notifier Manager: Output from journalctl -b 0 | grep StatusNotifierHost: May 10 17:13:59 bdw-desktop kded5[21295]: Registering "org.kde.StatusNotifierHost-27235" as system tray May 10 17:13:59 bdw-desktop kded5[11899]: Registering "org.kde.StatusNotifierHost-12215" as system tray Output from ./listIcons.sh: org.kde.StatusNotifierWatcher pid,start,command: 21295 17:12:32 kded5 -e ITEMS: -e ITEM: :1.38/StatusNotifierItem PID STAT: 27336 17:12:36 /usr/bin/korgac ID: KOrganizer Reminder Daemon TITLE: KOrganizer Reminder Daemon -e ITEM: :1.35/StatusNotifierItem PID STAT: 27274 17:12:36 /usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier ID: Discover Notifier_org.kde.DiscoverNotifier TITLE: Updates -e ITEM: :1.31/org/ayatana/NotificationItem/pasystray PID STAT: 27295 17:12:36 /usr/bin/pasystray ID: pasystray TITLE: pasystray -e ITEM: :1.55/StatusNotifierItem PID STAT: 27345 17:12:36 /usr/bin/kmix --keepvisibility ID: KMix TITLE: Volume Control -e ITEM: :1.39/org/ayatana/NotificationItem/Skype1 PID STAT: 27337 17:12:36 /usr/share/skypeforlinux/skypeforlinux --executed-from=/home/bdw --pid=27328 ID: Skype1 TITLE: skypeforlinux -e ITEM: :1.63/StatusNotifierItem PID STAT: 2517 17:13:07 /usr/bin/kalarm --tray ID: KAlarm TITLE: KAlarm -e ITEM: :1.98/org/ayatana/NotificationItem/dropbox_client_27390 PID STAT: 27390 17:12:36 /home/bdw/.dropbox-dist/dropbox-lnx.x86_64-96.4.172/dropbox ID: dropbox-client-27390 TITLE: dropbox -e ITEM: :1.111/org/ayatana/NotificationItem/dropbox_client_24606 PID STAT: 24606 17:17:32 /home/bdw/.dropbox-dist/dropbox-lnx.x86_64-96.4.172/dropbox ID: dropbox-client-24606 TITLE: dropbox KeepassXC, Slack, and HP-SystemTray did not open their windows and their icons did not appear in the system tray. > > * In one of comments you wrote that problem occurs only when KDE is started > from SDDM, but it is fine when started using startx command. I checked both, > there is a difference is startup procedure: > SDDM runs startplasma-x11 (using sddm-helper) > startx runs plasma_session (using x-session-manager) > I don't know if what is the difference, I will check with other Plasma > developers. I plan to run additonal tests to confirm this. Either a background process is messing this up, or something with sddm. We just have to narrow things down. That being said, startx always seems to work (though I do plan to run multiple tests with it to see if it's consistent). -- You are receiving this mail because: You are watching all bug changes.
