I use a single "Panel" that has the laucher, virtual desktop switcher, task manager, and notifications / clock. Every once in a while (usually < 1hr of usage) I notice that the clock is stopped. Also the task manager portion shows old state... if I had xosview open (for example) when the "Panel" froze, then kill it later... I can still see the xosview in the task manager. The state of the task manager *is* updated. I can change from app to app just fine, but I have to know where they are because what I see does not reflect the current state. I can even hover and pause and discover what is actually on the panel. i.e. If I hover over what appears to be taskA (even though taskA is no longer preset) if taskB happens to be in that same spot, the flyout menu shows taskB. Also alt+tab shows the correct tasks and task order, even when the panel UI/diplay is "frozen".
This seems an awful lot like the bug described here: https://bugzilla.redhat.com/show_bug.cgi?id=1193742 That bug talks about this happening with Intel graphics though. I am running NVIDIA hardware and drivers. One other interesting thing is if I start and stop the compositor the transparency of the panel get enabled/disabled, but still the wrong information is shown (i.e. the clock is wrong, the state of the task manager is wrong etc).
Hi, I'm experiencing the same bug daily. I'm using NVIDIA drivers and latest software version (on Archlinux). I did not found a pattern to reproduce the bug. Sometimes it starts while copying files or after opening/closing notifications. Similar bugs: https://bugs.kde.org/show_bug.cgi?id=380250 https://bugs.kde.org/show_bug.cgi?id=383660 https://bugs.kde.org/show_bug.cgi?id=386781 https://bugs.kde.org/show_bug.cgi?id=375781 https://bugs.kde.org/show_bug.cgi?id=358231 https://bugs.kde.org/show_bug.cgi?id=351897 https://bugs.kde.org/show_bug.cgi?id=382372 If you need more detailed info just ask :-)
*** This bug has been marked as a duplicate of bug 353983 ***
For what its worth... I have been running with the compositor disabled for a while now, and the issue is gone while in this mode. I suspect the issue still exists, but I just keep the compositor disabled.