https://bugs.kde.org/show_bug.cgi?id=420635
--- Comment #29 from Konrad Materka <mate...@gmail.com> --- (In reply to Brian Wright from comment #28) > 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. That should be enough to pinpoint the root cause. If clean account is working fine and with restored setting it is not, then most probably something is wrong with these settings. > 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 > > PasSystray duplicated. One is a legacy icon (handled by xembedsniproxy). Probably PasSystray detects that there is no SNI and configures legacy tray icon. Then detects that SNI is configured and uses SNI, but legacy icon still there. Killing xembedsniproxy should hide one of the duplicated icons. > > * 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 This is strange, two registrations? Did you log out immediately after login, then logged in again? If yes, then it is also strange, there is a big difference between PIDs (9430, 31127)... The pids and start times are really strange: 13:36:26 kded started (PID 29782) - OK 13:36:27 pasystray started (PID 31350) - OK, one second later 13:36:27 xembedsniproxy started (PID 31134) - OK, one second later 13:36:58 kalarm started (PID 7545) - 30 seconds later... Maybe coincident... 13:37:18 StatusNotifierHost registered (PID 31127) - much, MUCH too late, on my system StatusNotifierHost is registered 1-2 seconds after kded is started. Is you Plasma Desktop taking long time to start? Can you disable some of the apps starting and check if that helps? I have no idea but to start with clean user profile and restore configuration one app at a time. > Disabling all background services except for Status Notifier Manager: OK, no change, dead end. > That being said, startx always seems to work (though I do plan to run > multiple tests with it to see if it's consistent). OK, thanks. -- You are receiving this mail because: You are watching all bug changes.
