Out of nowhere (I don’t know, maybe I did touch something and didn’t realize) my KDE Plasma desktop doesn’t boot up properly. After logging using emptty, the usual KDE loading screen appears and then a black screen shows out, the cursor is also visible, but nothing else.

I move my cursor to the top-left corner and the program to create a new desktop works. I create a new desktop but so is a black screen. I can change to a tty using Ctrl+Alt+F1 and then go back to plasma using Ctrl+Alt+F7.

Have somebody had the same issue before?

  • CPU: AMD Ryzen 5600X
  • GPU AMD RX 7600
  • Distro: Void Linux
  • Linux Kernel: 6.18

I can’t remember the version of emptty nor KDE Plasma, Im not with my PC right now, I do the post to know some quick fixes to try once I get home.

Thank you for your attention.

  • HelloRoot@lemy.lol
    link
    fedilink
    English
    arrow-up
    4
    ·
    18 hours ago

    Change into a tty, check your journalctl and see if there are any related errors for the current boot.

    journalctl -b -p err
    
  • Offbus@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    14 hours ago

    I’ve had this happen on a newer Dell laptop and an Asus atx build. For both machines, a BIOS upgrade to the latest from their respective OEMs immediately restored functionality.

  • blackbrook@mander.xyz
    link
    fedilink
    arrow-up
    1
    ·
    14 hours ago

    Do you have any possibility to log in as a different user or even create a new user to log in as? I wonder of some plasma config file could be corrupted.

  • sneaky@r.nf
    link
    fedilink
    English
    arrow-up
    1
    ·
    13 hours ago

    This happens to me once in a while with Fedora KDE. Usually right after a kernel update and I can resolve by going back to the previous kernel for a few days. Always guessed it was the AMD GPU driver.

  • ApertureUA@lemmy.today
    link
    fedilink
    arrow-up
    1
    ·
    6 hours ago

    Does KRunner (Alt + F2 default, sometimes Super + R in configs) still run? Try launching “plasmashell” from there. Or a terminal emulator so that you can see the logs of plasmashell, and maybe attach a debugger…