This is a weird bug which occures to me seemingly randomly ever since upgrading to 4.11.2, and remains in 4.11.3. Every 20-40 minutes, the system tray icons suddenly change, and become the old-style icons, instead of the new, symbolic icons. Their behaviour also changes - so for example clicking on kmix opens the mixer application window, instead of just opening the volume meters from the panel. After this happens, hotkeys don't work anymore: keyboard layout switching and brightness control isn't possible using the shortcuts. The only way to solve this is logout-login. I don't know what may cause this - but it MAY be related to random kde daemon crashes which seem to not affect anything as they happen (I simply get a message that kde daemon crashed, but everything keeps working as usual). Reproducible: Didn't try Steps to Reproduce: There is no concrete way to reproduce. It happens seemingly randomly. Even with a new user, with loads/no applets enabled, and with various software open.
Please find out which kded module is responsible by disabling them. For more information, see http://kdepepo.wordpress.com/2011/05/11/troubleshooting-kded4-bugs/ Also, if you get the KDE crash dialog, please add the backtrace. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Same behaviour here on Archlinux x86_64. The only thing I can say is that no Custom Hotkeys is working, tray icons are the old-style ones. If you want to reproduce the crash, just disable one of your custom hotkeys and apply.
Artaserse - I cannot seem to be able to reproduce the crash as you say. Can you provide an example? For now, I have disabled Kdeconnect on a hunch, and so far it seems to be ok (few hours now). I'll update.
(In reply to comment #3) > Artaserse - I cannot seem to be able to reproduce the crash as you say. Can > you provide an example? > > For now, I have disabled Kdeconnect on a hunch, and so far it seems to be ok > (few hours now). I'll update. Unfortunally it actually happened three or four times in a row only, I thought it was reproducible, but I was wrong. Btw I've disabled Kdeconnect too and it is working now
Reassigning to kdeconnect developers for further inspection, but I guess without a backtrace, there is nothing that can be done.
Just visiting to confirm - after disabling kdeconnect the problem has stopped completely. It is almost definitely something in kdeconnect.
Should be fixed in the latest version from git master.