SUSE tumbleweed gets me to login screen and then dies

I tried to login to my SUSE tumbleweed the other day and I got to the login screen, I logged in as normal and I saw the image of a light bulb with a spinning gear below it. After about 10 seconds the spinning gear stopped spinning and nothing happened.

I then tried to boot into recovery mode, and I need to slow down the scrolling to see where the error is?

I don’t know if we have the same problem.
In my case, I get a black screen with the cursor. I can move the cursor, so the PC isn’t dead. As an experiment, I right-clicked somewhere on the black screen and then went to the desktop/background menu.
I use Vallpaper to give my virtual screens a different background. It turns out that Vallpaper no longer works after the latest update. I selected Hunyango and immediately got my icons and taskbar back. But alas all my virtual screens have now the same background.

NVIDA involved???
What CPU? Desktop?
Saying it’s broke does not help

Oh sorry.
I’m using a Dell XPS 8940 desktop

kinfo
Operating System: openSUSE Tumbleweed 20260216
KDE Plasma Version: 6.6.0
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 6.18.9-1-default (64-bit)
Graphics Platform: X11
Processors: 16 × 11th Gen Intel® Core™ i7-11700 @ 2.50GHz
Memory: 16 GiB of RAM (15.3 GiB usable)
Graphics Processor 1: NVIDIA GeForce RTX 3060 Ti
Graphics Processor 2: Intel® Graphics

At the time of the first message I was using GPU 2 (Intel)
Now I’m back with GPU 1 (NVIDIA)

Vallpaper 6.0.3. There is no configuration options at all. So obviously Vallpaper can’t handle the latest Plasma update.

@tos4ever See https://store.kde.org/p/1197828 and read comments…

There will be no quick fix for this.

@Dr_Matt:

First – Welcome to the openSUSE Forums!


A couple of questions –

  • Is your openSUSE Tumbleweed system a new install?
  • Have you enabled SELinux?

Sanity check – my current daily desktop system:

 > kinfo
Operating System: openSUSE Tumbleweed 20260216
KDE Plasma Version: 6.6.0
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 6.18.9-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 8600G w/ Radeon 760M Graphics
Memory: 34 GB of RAM (32.8 GB usable)
Graphics Processor: AMD Radeon 760M Graphics
 > 
 > sestatus 
SELinux status:                 enabled
SELinuxfs mount:                /sys/fs/selinux
SELinux root directory:         /etc/selinux
Loaded policy name:             targeted
Current mode:                   enforcing
Mode from config file:          enforcing
Policy MLS status:              enabled
Policy deny_unknown status:     allowed
Memory protection checking:     actual (secure)
Max kernel policy version:      35
 > 

Most likely SSDM starting on VT1, on login Plasma Wayland starting, freezes, runs on other VT - #25 by JanW . Today’s snapshot fixed it.

Turns out it was a corrupted desktop.

@Dr_Matt:

Was the corruption due to some unfortunate content in the user’s ‘~/.cache/’ directory?

On your system, is the systemd “display-manager” an alias?

 > systemctl list-unit-files | grep -iE ' STATE |display|sddm'
UNIT FILE                                    STATE           PRESET
display-manager-legacy.service               disabled        enabled
display-manager.service                      alias           -
sddm.service                                 enabled         disabled
 > 
 > find /usr/lib/systemd/ -iname '*display*'
/usr/lib/systemd/system/display-manager-legacy.service
 >

No idea. I got someone else to fix it in the end.