Bug 470309 - System randomly becomes unresponsive to any input, but audio playback still works normally
Summary: System randomly becomes unresponsive to any input, but audio playback still w...
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 5.27.5
Platform: Fedora RPMs Linux
: NOR grave
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-26 19:09 UTC by Henning
Modified: 2023-08-26 01:58 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Last log messages after freeze (10.56 KB, text/plain)
2023-07-12 12:27 UTC, Oleg
Details
Full journal log (21.10 KB, text/plain)
2023-07-12 12:39 UTC, Oleg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Henning 2023-05-26 19:09:30 UTC
I currently have no logs or anything, but this is happening repeatedly, throughout some updates.

After doing nothing for a while, screen was off, the shell does not repond to mouse or keyboard input anymore.

I listened to music, which still worked normally, even titles changed once the first was finished.

Closing the lid and waiting did not turn off the display, normally set to 1min.

--- Software ---
OS: Fedora Linux 38.20230526.0 (Kinoite)
KDE Plasma: 5.27.5
KDE Frameworks: 5.106.0
Qt: 5.15.9
Kernel: 6.2.15-300.fc38.x86_64
Compositor: wayland

--- Hardware ---
CPU: AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx
RAM: 13.5 GB
GPU: AMD Radeon Vega 8 Graphics
Video memory: 2048MB
Comment 1 Henning 2023-05-26 19:10:02 UTC
the only thing I could do was hard shutdown. Even fallback to TTY didnt work.
Comment 2 Techognito 2023-05-27 17:39:48 UTC
I had the same issue previously, for me, it was an out-of-memory issue.

Since TTY stops working, the symptom sounds unrelated to KDE
(KDE might be the cause, it is to be confirmed)

For logs with info, check out: /var/log/messages (also see the /var/log/messages-<date-stamp>, for the date that fits) or journalctl -xe

Alternatively, the next time you leave your computer alone, open system monitor on the processes page and change the view to Show: All Processes (this gives you a nice overview of what consumes resources when it froze)

I am on F37 but if I remember correctly there is a bug already for F38 and memory leaks
Comment 3 Vlad Zahorodnii 2023-06-01 11:14:24 UTC
Can you attach the kwin logs to this bug report when the screen is frozen? The logs can be retrieved using

 journalctl --user-unit plasma-kwin_wayland --boot -1
Comment 4 Henning 2023-06-10 11:59:10 UTC
I tried getting a journalctl log couple of times, no errors where shown.

I could also not identify a specific problem, maybe an update, maybe firefox, I cant say.
Comment 5 Henning 2023-06-14 15:25:12 UTC
Jun 14 17:05:40 fedora plasmashell[1650]: file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:61:17: Unable to assign [undefined] to int
Jun 14 17:05:40 fedora plasmashell[1650]: file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:61:17: Unable to assign [undefined] to int
Jun 14 17:05:10 fedora plasmashell[1650]: file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:61:17: Unable to assign [undefined] to int
Jun 14 17:05:10 fedora plasmashell[1650]: file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:61:17: Unable to assign [undefined] to int

That was the only error journalctl found
Comment 6 Henning 2023-06-14 15:25:56 UTC
after that error the whole screen got black 0,5s and then on again, sound stopped and went on but no peripherals anymore. No apps crashed visibly.
Comment 7 Oleg 2023-07-12 12:27:59 UTC
Created attachment 160253 [details]
Last log messages after freeze

I can confirm this issue.
KWin Wayland could completely freeze on AMDGPU ignoring any input while rest of the system stays completely intact. I encountered this issue on my 6700 XT desktop and 5600H laptop. Killing "kwin_wayland" process eventually will bring you to SDDM but that's not practically different from rebooting. In the attachment are last journactl messages recovered by SSHing in hanged machine.
Comment 8 Oleg 2023-07-12 12:39:16 UTC
Created attachment 160255 [details]
Full journal log

Sorry, ignore previous attachment, it wasn't complete.
Comment 9 Oleg 2023-07-17 20:44:12 UTC
I think this issue caused by drawing thumbnails in task bar when you hover mouse over application icons. When I toggled them off I don't experience this issue anymore.
Comment 10 Zamundaaa 2023-08-09 09:20:32 UTC
The amdgpu driver seems to be crashing for you, which is most likely the cause of the issue. Please open an issue about it to https://gitlab.freedesktop.org/drm/amd/-/issues
Comment 11 Henning 2023-08-26 01:58:45 UTC
hmm, yes possible. But normally the reaction to "no icon available" is simply to show the icon or a blank window?