Hello,
I’m experiencing an issue where my Fedora KDE system completely freezes after being idle overnight. The system becomes unresponsive — both the mouse and keyboard stop working, and I’m forced to do a hard reboot.
fpaste --sysinfo: UNTITLED - Pastebin Service
I get 404 Page Not Found trying to access your Pastebin.
I’m assuming your system is suspending overnight. If you use the GUI to click on Suspend, does it have the same problem?
If you search the forums you’ll see lots of us are having problems with suspend on kernel 6.11+. It seems that the device to blame is this Mediatek chip. Try disabling bluetooth in your KDE settings or moving back to a 6.10.x kernel until it’s resolved. There are also scripts posted here that will disable this device before suspend and re-enable it afterwards if you need to use bluetooth.
Here is my chip (from inxi -Fzx):
Network:
Device-1: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
vendor: Foxconn driver: mt7921e v: kernel bus-ID: 0a:00.0
Bluetooth:
Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB
bus-ID: 3-6:3
Report: btmgmt ID: hci0 rfk-id: 4 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: <filter> bt-v: 5.2 lmp-v: 11
Sorry, I think the 404 page is because pastebins in that site are deleted after 24 hours.
Here’s my inxi -Fzx:
System:
Kernel: 6.11.8-300.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.43.1-2.fc41
Desktop: KDE Plasma v: 6.2.3 Distro: Fedora Linux 41 (KDE Plasma)
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: TUF GAMING B550-PLUS v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 3611
date: 09/30/2024
CPU:
Info: 12-core model: AMD Ryzen 9 5900X bits: 64 type: MT MCP arch: Zen 3+
rev: 2 cache: L1: 768 KiB L2: 6 MiB L3: 64 MiB
Speed (MHz): avg: 550 min/max: 550/4951 boost: enabled cores: 1: 550
2: 550 3: 550 4: 550 5: 550 6: 550 7: 550 8: 550 9: 550 10: 550 11: 550
12: 550 13: 550 14: 550 15: 550 16: 550 17: 550 18: 550 19: 550 20: 550
21: 550 22: 550 23: 550 24: 550 bogomips: 177261
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 22 [Radeon RX 6700/6700
XT/6750 XT / 6800M/6850M XT] vendor: Micro-Star MSI driver: amdgpu
v: kernel arch: RDNA-2 bus-ID: 0d:00.0
Display: wayland server: Xwayland v: 24.1.4 compositor: kwin_wayland
driver: N/A resolution: 2560x1440
API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast platforms:
active: gbm,wayland,x11,surfaceless,device inactive: N/A
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.7 glx-v: 1.4
direct-render: yes renderer: AMD Radeon RX 6700 XT (radeonsi navi22 LLVM
19.1.0 DRM 3.59 6.11.8-300.fc41.x86_64)
API: Vulkan v: 1.3.296 drivers: N/A surfaces: xcb,xlib,wayland devices: 2
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 21/23 HDMI/DP Audio
driver: snd_hda_intel v: kernel bus-ID: 0d:00.1
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 0f:00.4
API: ALSA v: k6.11.8-300.fc41.x86_64 status: kernel-api
Server-1: PipeWire v: 1.2.7 status: active
Network:
Device-1: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
v: kernel bus-ID: 07:00.0
IF: wlp7s0 state: up mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
port: f000 bus-ID: 0a:00.0
IF: enp10s0 state: down mac: <filter>
IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Bluetooth:
Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB
bus-ID: 1-7.2:5
Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.3
lmp-v: 12
Drives:
Local Storage: total: 9.33 TiB used: 952.47 GiB (10.0%)
ID-1: /dev/nvme0n1 vendor: Toshiba model: N/A size: 238.47 GiB
temp: 47.9 C
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 980 PRO 2TB size: 1.82 TiB
temp: 40.9 C
ID-3: /dev/sda vendor: Western Digital model: WD4005FZBX-00K5WB0
size: 3.64 TiB
ID-4: /dev/sdb vendor: Western Digital model: WD40EZAZ-00SF3B0
size: 3.64 TiB
Partition:
ID-1: / size: 1.82 TiB used: 809.79 GiB (43.5%) fs: btrfs dev: /dev/dm-0
mapped: luks-d2a30d84-1732-4bda-8fef-17952407fdf2
ID-2: /boot size: 973.4 MiB used: 348.3 MiB (35.8%) fs: ext4
dev: /dev/nvme1n1p2
ID-3: /boot/efi size: 598.8 MiB used: 19.3 MiB (3.2%) fs: vfat
dev: /dev/nvme1n1p1
ID-4: /home size: 1.82 TiB used: 809.79 GiB (43.5%) fs: btrfs
dev: /dev/dm-0 mapped: luks-d2a30d84-1732-4bda-8fef-17952407fdf2
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
System Temperatures: cpu: 53.4 C mobo: N/A gpu: amdgpu temp: 47.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 64 GiB note: est. available: 62.69 GiB used: 9.06 GiB (14.4%)
Processes: 646 Uptime: 2h 31m Init: systemd target: graphical (5)
Packages: 25 note: see --rpm Compilers: gcc: 14.2.1 Shell: Bash v: 5.2.32
inxi: 3.3.36
OK, since you don’t have the Mediatek wifi/bluetooth chip it’s likely a different issue, but the issue hasn’t been root caused yet so who knows. Might be interesting to try one of the workarounds just to see. Might also look at journalctl to see if you see any errors.
I also have this issue which began when I installed KDE as a fresh install. This doesn’t occur with Gnome via Wayland or X11.
I have applied the proposed workarounds of disabling at least WiFi or Bluetooth manually, via the script mentioned here on Reddit and also by disabling the Bluetooth service entirely.
None of the options have worked.
I have noticed that it isn’t a complete freeze. Rather, the system shows the previous frame before the screen turned off. This just happens to be the lock screen. The keyboard does in fact work (at least for me) and I should warn that it’s important to be careful that you don’t type a password and hit enter because you could be typing that into whichever application is running in the foreground, such as Discord, if your PC has unlocked.
If you press CTRL+ALT+F3 (to go into terminal mode) and then CTRL+ALT+F2 (to return to desktop) then it should finally unfreeze that frame and let you back in.