Hi guys! I have KDE Neon 6.2.3 running on my Surface Pro 7+, and up until now it’s been running rather smoothly, for years. But today I seem to be unable to fully boot anymore on normal mode. Linux will get stuck on the KDE spinning gear, with the gear frozen. And it becomes unresponsive, to open alternative consoles with control+alt+Fx, or even control+alt+del. The only thing that works is a force shutdown by holding the power button.

I tried with a previous kernel, with the same results (current is linux-image-6.10.10-surface-1, I have a generic 6.8.0-49, but it also freezes). I can boot in safe mode. It opens a different login screen, and after a failed attempt of opening lxde, it fails back to my usual KDE session, in safe graphics mode.

What can I test? How can I see what failed at boot?

  • anamethatisnt@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    22 days ago

    If a clean install also fails then I would start considering hardware fault.
    You could always check if you can boot Fedora Workstation with GNOME just in case but I think you should start looking for a replacement PC.

    • iturnedintoanewt@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      21 days ago

      I actually clicked on the replace partition option on the installer, instead of a full disk wipe. The profile did look brand new once I managed to login in safe mode, but I didn’t stay too long to check, as I just concluded hell, if it only boots in safe mode I might as well continue troubleshooting on the original install.

      Anyway…After going back to the original image (as I had it backed up anyway), I paid a bit more attention at that weird popup on safe mode as I logged in, mentioning it failed to launch startlxde. So I ran

      sudo dpkg --reconfigure sddm

      And on the menu, for some reason sddm wasn’t the first choice. After choosing it again, this time it went straight to the boot screen. Some other day I’ll check again whichever random login menu is installed, and remove it, as it clearly causes issues.