Created attachment 178583 [details] The session journalctl log. SUMMARY Under specific (but not entirely known) circumstances (presumably using the system with multiple virtual desktops and post-wake from sleep), launching some applications can entirely freeze plasmashell, causing the appearance of a frozen screen. The system still operates behind the frozen graphics. This has been observed with the Telegram Desktop Flatpak and GPU Screen Recorder specficially, though it's not likely that thee applications are specific culprits. Immediately force shutting down the system and viewing the previous boot logs on the next boot by using `sudo journalctl --no-hostname -b -1`, the logs continue as normal until a type error is reached. This, presumably, causes the freeze. ``` Feb 18 23:27:34 plasmashell[18474]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:79: TypeError: Cannot read property 'status' of null Feb 18 23:27:34 plasmashell[18474]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:79: TypeError: Cannot read property 'status' of null Feb 18 23:27:34 plasmashell[18474]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:79: TypeError: Cannot read property 'status' of null ``` STEPS TO REPRODUCE 1. Have a set up with 4x4 virtual desktops, and a panel with Icons Only Task Manager. 2. Sleep the system, mess around with applications on multiple virtual desktops. 3. Launch (presumably) any application. OBSERVED RESULT The system's graphics (and presumably input) are frozen. The system still operates behind the scenes. Media still plays, network connections are still active etc. EXPECTED RESULT The Icons-Only Task Manager widget operates as normal, and does not crash plasmashell when launching some applications under specific (though not entirely known) circumstances. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Bazzite 41 (6.12.12-207.bazzite.fc41.x86_64 (64-bit)) KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION The specific cause is unknown. This needs to be investigated.
Just for clarity, I don't entirely *know* that this is the cause, just that I saw this happen two times in a row between two seperate system sessions that ended with the same error. Regardless, the entire boot log was provided to help pin it down.
The error message is fixed in 6.3.1, and should not cause freezes or anything of the sort. In 6.3.0 it appears on almost every mouse interaction with the task manager, so it's not unlikely that you will see it, but it's mostly harmless. Renaming to focus on the real problem.
Ah, so it was a red herring, just as I feared. I've recategorised the report. Would the journalctl logs be enough to help narrow this down, should I go about providing more information?
(In reply to ottergauze from comment #3) > Ah, so it was a red herring, just as I feared. I've recategorised the > report. Would the journalctl logs be enough to help narrow this down, should > I go about providing more information? I had a quick look, and there doesn't seem to be anything particularly obvious. Maybe someone else can spot something though. With a crash we would really need a crash report; but when the system is hanging we don't really get a trace automatically, the way we usually do for crashes. We have some specific instructions about how to get debug information for freezes which I'm pasting below, but if the whole screen is frozen, not just the panels/desktop, this is likely kwin freezing, not plasmashell, and that blocks the usual way of doing this. If you can still switch to a virtual console it could work, or if you can ssh into the system from another one it's maybe easiest. Also note that some distributions block attaching gdb to a running process for security reasons, so you might need to enable that first. Also, have you had this issue for a while or is it new with Plasma 6.3? There is a known freezing issue with 6.3, but it appears when moving windows to the top of the screen, see here: https://bugs.kde.org/show_bug.cgi?id=499913 ---- Can you get a backtrace of what it's doing when it's hung? Run gdb attach -p $(pidof kwin_wayland) in a terminal window while it's hung If it says "--Type for more, q to quit, c to continue without paging--" at the bottom of the terminal window, press the "c" key. When you see a prompt that says "(gdb)", type "bt" and press the enter key. If it says "--Type for more, q to quit, c to continue without paging--" at the bottom of the terminal window, press the "c" key. Copy-and-paste the contents of the terminal window into a comment here. Thanks!
.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.