KDE Desktop/GUI freezes, no TTY requiring hard shut down

Ask Fedora
, ,
1

This has been happening for a while now. Sometimes I get close to 2 days out of it and sometimes it happens 3 times a day.
Nothing special running.
Firefox/Thunderbird/GrellM/Konsole are the ones 90% in usage.
System is fully up to date.

Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.3
KDE Frameworks Version: 6.28.0
Qt Version: 6.11.1
Kernel Version: 7.1.4-204.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen AI 9 HX 370 w/ Radeon 890M
Memory: 64 GiB of RAM (62.1 GiB usable)
Graphics Processor: AMD Radeon 890M Graphics
Manufacturer: Framework
Product Name: Laptop 16 (AMD Ryzen AI 300 Series)
System Version: A9

2

Do you have a second system you can use to ssh into failing system?
If so does ssh work when the hang happens?

3

I have a 2nd laptop with Suse Tumbleweed, but I have never used SSH before. I will have to do some research for that.

4

You will need to turn on sshd on the Fedora system.

sudo dnf enable sshd --now

Then you should be able to ssh into the Fedora system.
I don’t recall changing the firewall…

5

Is there anything interesting in the log for the previous boot after the system comes back up?

$ journalctl -b -1

Also, if this keeps happening, you might want to enable the magic SysRq key for a more controlled reboot/shutdown. With that enabled on my machines, I can just hold Alt+PrScr and type the letters s (sync), u (remount read-only), and b (reboot)/o (power off), which reduces the chance for filesystem issues dramatically.

6

I have booted into the previous Kernel as I was now getting constant freezes.
Besides that, these messages for
widged “Panel colorizer” come up on thousands of lines.
So for the time being, I have turned it off and see what happens now.

Jul 26 18:57:11 fedora plasmashell[2255]: Insufficient arguments 
                                           getWidgetProperties@file:///home/alfstandard/.local/share/plasma/plasmoids/luisbocanegra.panel.colorizer/contents/ui/code/utils.js:274
                                          expression for widgetProperties@file:///home/alfstandard/.local/share/plasma/plasmoids/luisbocanegra.panel.colorizer/contents/ui/components/CustomBackground.qml:60

Also get the following dmeg’s

sudo dmesg -T --level=err
Place your finger on the fingerprint reader
[Sun Jul 26 18:43:10 2026] virt/tdx: TDX not supported by the host platform
[Sun Jul 26 18:43:10 2026] platform MSFT0201:00: AMD-Vi: [Firmware Bug]: No ACPI device matched UID, but 1 device matched HID.
[Sun Jul 26 18:43:12 2026] hid-multitouch 0018:093A:0274.0003: Returned feature report did not match the request
[Sun Jul 26 18:43:12 2026] amdtee: failed to load firmware /amdtee/f29bb3d9-bd66-5441-afb88acc2b2b60d6.bin
[Sun Jul 26 18:43:12 2026] amdtee: failed to copy TA binary
[Sun Jul 26 18:43:12 2026] Failed to open TEE session err:0x0, rc:-12
[Sun Jul 26 18:43:12 2026] amd-pmf AMDI0103:00: Failed to open TA session (-12)
[Sun Jul 26 18:43:13 2026] ucsi_acpi USBC000:00: unknown error 256
[Sun Jul 26 18:43:14 2026] ucsi_acpi USBC000:00: unknown error 256
7

I can’t rule it out, of course, but I wouldn’t expect that a widget can crash your system hard enough that you can no longer switch to a virtual terminal.

Similarly, nothing really stands out.

And I take it there aren’t any obvious “oops”, “panic”, or “call trace” messages in the kernel log from previous boots?

$ journalctl -o short-precise -k -b -1  # -2, -3, etc. to go back to earlier boots
8

Thanks for showing an interest, no nothing else standing out for the moment.
Action taken:

  1. Properly removed widged “Panel colorizer”
  2. Not rebooted, but shut down laptop
  3. booted using the latest kernel again.

No crashes so far. Below are the latest kernel messages.

journalctl -b -0 -p err --system --no-pager
Jul 27 05:53:23 fedora kernel: virt/tdx: TDX not supported by the host platform
Jul 27 05:53:23 fedora kernel: platform MSFT0201:00: AMD-Vi: [Firmware Bug]: No ACPI device matched UID, but 1 device matched HID.
Jul 27 05:53:24 fedora kernel: hid-multitouch 0018:093A:0274.0003: Returned feature report did not match the request
Jul 27 05:53:24 fedora kernel: amdtee: failed to load firmware /amdtee/f29bb3d9-bd66-5441-afb88acc2b2b60d6.bin
Jul 27 05:53:24 fedora kernel: amdtee: failed to copy TA binary
Jul 27 05:53:24 fedora kernel: Failed to open TEE session err:0x0, rc:-12
Jul 27 05:53:24 fedora kernel: amd-pmf AMDI0103:00: Failed to open TA session (-12)
Jul 27 05:53:25 fedora kernel: ucsi_acpi USBC000:00: unknown error 256
Jul 27 05:53:26 fedora kernel: ucsi_acpi USBC000:00: unknown error 256
Jul 26 19:53:29 fedora bluetoothd[1123]: Failed to set mode: Failed (0x03)
Jul 26 19:53:43 fedora bluetoothd[1123]: Failed to set mode: Failed (0x03)
9

I believe that’s a typo. I think you meant:

sudo systemctl enable --now sshd

10

Yes, it was, but an easy fix.

11

I will mark this as resolved. Since removing Panel Colorizer no more freezing/crashes have occured.
The author even mentions on Github that updates could cause plasma to crash.

Caution

The C++ plugin may stop working or cause Plasma to crash after a system update (#209) and will need to be rebuilt, see Build from source (With C++ Plugin).

To temporarily recover from the crashes, you can manually remove the plugin