Created attachment 1109533 [details] backtrace when the process is stuck Description of problem: Every now and then, my desktop (not the applications) freezes due to hang in plasmashell. Version-Release number of selected component (if applicable): plasma-workspace-5.5.0-4.fc23.x86_64 How reproducible: always Steps to Reproduce: 1. use KDE on Fedora 23 2. wait a few hours, definitely less than a day 3. meanwhile, if you're impatient, try to generate lots of messages in systray (like 'copying done', KDE Connect sees a new device, etc.) Actual results: panel clock stops at some point, nothing in panel reacts (cannot open K menu etc.), the last notification stays shown on top (over any maximized window or anyhing like that) and cannot be closed, various other KDE things behave strangely - for example, in already running Konqueror window sometimes there may be a problem to open new tab (it seems not to react at first, then it may open after a few minutes ...) Expected results: (nothing of above) Additional info: There is the bug 1237269 but it doesn't eat cpu in my case - it just sits and waits in some poll. Also, as noted before, it seems to usually happen right after popping up some notification (i.e. not always after the notification, but if it happens, it happens after that). If this is hardware dependent (intel driver seems involved), lspci identifies it as: 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
I raised basically the same issue with Fedora 25 in bug 1409109. Please feel free to follow that bug and bump it from time to time so that it won't be closed due to EOL like this one.
See bug 1399396 for current status.
(In reply to Piotr Dobrogost from comment #3) > I raised basically the same issue with Fedora 25 in bug 1409109. Please feel > free to follow that bug and bump it from time to time so that it won't be > closed due to EOL like this one. thanks for the information but I have "fixed" this for myself by using LXQT on a new machine install ... however, changing to dupe as it seems more proper and I do like to keep Bugzilla tidy ;-) *** This bug has been marked as a duplicate of bug 1399396 ***