6.15.4-200.fc42 crashes to tty instead of suspend (KDE Plasma)

Since updating to, I would say, either 6.15.3 or 6.15.4, my system has randomly started to crash to “legacy TTY” when I leave it running, but go away. I would expect it to suspend at some point (maybe 30min I think I have it set to), but instead it often just seems to “crash to” (not sure if that is the correct way to say it) TTY. When I return to my computer, I see a screen similar to this (screenshot from google), but with my name saying I should login (enter username). It is completely unresponsive though, and my keyboard is no longer lit, so I think it may have at least started the suspension process to some degree, but the keyboard won’t work and I am stuck.


At this point I have to hit the reset button on my computer and boot again.

I am a bit uncertain exactly at what point it is crashing, but I thought that I could get something from journalctl and I did manage to pull this, though it does not tell me much (newbie). I see “legacy console [tty0] enabled” in the output, so I thought that could be a lead..?

DE: KDE Plasma 6.4.1

UPDATE: Just remembered that this, “The screen locker is broken…” also now happens regularly (screenshot below). Not sure if this then always happens before the “tty crash”, but I suppose it could be so. This part (at least) is probably KDE Plasma related?


I do actually get out of this, oddly enough not according to the instructions though. I press CTRL+ALT+F1 and after 2s I am back at the login screen and can unlock my computer, like I normally would after screen saver + lock…

inxi -Gxx

Graphics:
  Device-1: NVIDIA GA104 [GeForce RTX 3060] vendor: ASUSTeK driver: nvidia
    v: 575.64 arch: Ampere pcie: speed: 16 GT/s lanes: 16 ports: active: none
    off: DP-1,DP-2 empty: DP-3,HDMI-A-1 bus-ID: 08:00.0 chip-ID: 10de:2487
  Device-2: Microsoft LifeCam HD-3000 driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 5-1.1:3
    chip-ID: 045e:0779
  Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
    alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
    d-rect: 3840x1080 display-ID: 0
  Monitor-1: DP-1 pos: right model: Samsung LC24RG50 res: 1920x1080 hz: 144
    dpi: 92 diag: 613mm (24.1")
  Monitor-2: DP-2 pos: primary,left model: Samsung LC24RG50 res: 1920x1080
    hz: 144 dpi: 92 diag: 613mm (24.1")
  API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast
    gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia x11:
    drv: nvidia inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 575.64
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
    display-ID: :0.0
  API: Vulkan v: 1.4.313 surfaces: N/A device: 0 type: discrete-gpu
    driver: nvidia device-ID: 10de:2487 device: 1 type: cpu
    driver: mesa llvmpipe device-ID: 10005:0000
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info,wlr-randr x11: xdriinfo, xdpyinfo, xprop, xrandr

journalctl -b -1: jul 03 22:18:35 fedora kernel: Linux version 6.15.4-200.fc42.x86_64 (mockbuild@d - Pastebin.com

That’s due to a broken Fedora Qt package which breaks the KDE Plasma lockscreen. You can revert to the previous version of that package: KDE Plasma users - beware of new qt6-qtwayland version 6.9.1-2 (breaks lockscreen, may cause app crashes) - #2 by pg-tips

1 Like

Thanks man. Downgraded according to your instructions. Hope that at least rids me of that particular issue. Let’s see if it at all affects the other one (main one)…

Are you on fedora 40 still?
Can you update to either 41 or 42 as 40 is no longer being updated?

I am definitely on F42. As explained above, the first screenshot I just stole from google as I did not have my own.

Why would you do something so confusing?

:sweat_smile::sweat_smile: I literally clarified this twice in the original post (once in the text, the other time in the image alt text). I wanted to show exactly what I meant, but I cannot force the issue to occur so this is the best I could do while writing the post. Hence why, I clearly stated the screenshot was borrowed from google..