Created attachment 188510 [details] sudo journalctl SUMMARY After restarting my Laptop, sometimes non-KDE tray icons no longer appear in the tray bar. Normal KDE tray icons (volume, battery, etc) are still there. Examples for the missing tray icons: Discord, fw-fanctrl (a python script), Insync, Joplin (flatpak), ms-teams (flatpak), netcloud, slack, pumble, .. These are all application automatically started on login (via various methods) STEPS TO REPRODUCE 1. Boot laptop 2. plug in 2 monitors either from the start or during the boot 3. missing tray icons in the bottom right :/ OTHER INFORMATION I'm kinda (?) sure it has something to do with my monitor setup. I never could reproduce it without my external monitors. If I log-out and start a new session everything works - in this flow I dont unplug+replug my monitors. There is already a similar bug: https://bugs.kde.org/show_bug.cgi?id=499892 But I think (?) this is something different, because zxvb12z can reproduce it every time (Its only sometimes for me). And on his side it does not seem to correlate with any external monitor.. I have attached the output of `journalctl` after such an occurrence. I can see that there is a crash of kded6 - which I did not see any effect of while using the system (no crash report, no apparent restarting of the shell..) - I guess this could be the reason? Also there is just a bunch of other warning/error logs - not sure what is relevant from that :D SOFTWARE/OS VERSIONS Laptop: Framework 16 Operating System: Arch Linux KDE Plasma Version: 6.5.4 KDE Frameworks Version: 6.22.0 Qt Version: 6.10.1 Kernel Version: 6.18.4-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 9 7940HS w/ Radeon 780M Graphics Memory: 64 GiB of RAM (60.6 GiB usable) Graphics Processor 1: AMD Radeon 780M Graphics Graphics Processor 2: AMD Radeon RX 7700S Manufacturer: Framework Product Name: Laptop 16 (AMD Ryzen 7040 Series) System Version: AJ
> I can see that there is a crash of kded6 - which I did not see any effect of while using the system (no crash report, no apparent restarting of the shell..) - I guess this could be the reason? yes, that's exactly the reason. The attached logs suggest it's the same as https://bugs.kde.org/show_bug.cgi?id=512971 *** This bug has been marked as a duplicate of bug 512971 ***