Fedora 40 KDE Spin - crash to black screen

Ask Fedora
, , , , , ,
1

I recently installed Fedora 40 KDE Spin as dual boot with intention to move full-time from Windows 11 to the Fedora installation. This was done 2-3 weeks prior to the release of KDE 6/6.1. I experienced post install issues with Wayland and the Nouveau drivers, so I installed xorg/X11 and set it as my default display server, before also installing the RPMFusion AKmod nvidia drivers. I thought this fixed my issues, but unfortunately I am still experiencing the following two issues with the installation:

  1. Unexpected, seemingly unpredictable DE blackscreen

    • ~80% of crashes restore to SDDM login screen within a few minutes
    • Remaining 20% do not recover and require a hard reboot of the system
      • Occasionally shows a few characters of text on screen when this happens
    • I’ve tried looking through JournalCTL historical logs, but I’m not very versed in what I should be looking for
    • Deleted files at ~/.config/plasma* to try to reset plasma config
    • Behaviour exists under Wayland and X11
    • Might occur more frequently with certain flatpaks open, but unconfirmed

  2. No KDE session restore in X11

    • I believe this started around the time of the KDE Plasma 6 release, but my understanding is that Plasma 6 still supports session restore in X11

I appreciate any and all help, I’m really enjoying Fedora and would like to continue using it, but the sudden and unexpected, unceremonious closing of everything I’m working on between 1-10 times/week is getting frustrating.

2

That sounds suspiciously like OOM: OOM kills Plasma 6?

I had that happen regardless of 1TB swap, but I was intentionally doing something to really exhaust 16GB physical RAM in that one scenario (I barely exceed 8GB normally). Do you happen to know what your RAM usage was like before the black screen?

If I understand right Plasma 6 doesn’t support Session Restore, but I’m not certain if that’s a Wayland thing or with Plasma 6 in-general.

3

That sounds suspiciously like OOM: OOM kills Plasma 6?

It’s possible? I don’t recall my review with JournalCTL from the last time I was bothered to investigate turning up anything reaped or killed, but it’s entirely possible that I missed them. If you can advise a more efficient way to hunt through the old logs, I can see if I can turn anything up.

Though your post does indicate that this is on Plasma 6. It’s a little hazy at this point, so maybe take with a grain of salt, but I recall this behaviour extending to before the Plasma 6 update (I recall this as I had been waiting for the upgrade to hopefully resolve a few issues, I cannot positively say that this is one of them)

Do you happen to know what your RAM usage was like before the black screen?

I am unsure of exact numbers as I don’t monitor my RAM usage, though I can say that generally it does occur with what is likely slightly higher RAM usage. Most recent crash was last night, with the following running (from my memory):

  • Spotify (Flathub Repo)
  • Steam | Installing a 1-2GB game (Flathub Repo)
  • trilium (Flathub repo)
  • Okular (Fedora Linux Repo)
  • Firefox | Maybe 6 tabs open, just forums nothing intensive (Fedora Flatpaks Repo)

I’ve included the Flatpak repos used simply for clarity, I doubt they’re relevant.

System has 16GB of RAM

Let me know what else I can provide for looking into this! Thanks!

Edit: Meant to include that in regards to:

If I understand right Plasma 6 doesn’t support Session Restore, but I’m not certain if that’s a Wayland thing or with Plasma 6 in-general.

Based on the Plasma X11 and Wayland known significant issues pages, I believe the lack of session restore should only apply to Wayland, but I’m more than happy to accept if I’m incorrect.

4

I have edited my original post for brevity, though it still contains the same information as before.