Opening a new topic b/c unsure if related to similar current ones. I’m running TW with KDE and X11.
After zipper dup today, last was on Nov 30th, unsure what snapshot, getting black screens right after the initial spinning cog wheel, never reaching the login screen. Rolled back and incrementally updated with YaST SW everything except xorg-x11-server xorg-x11-server-extra xorg-x11-server-Xvfb, which gets me to a stable system. Checking journal, I see with newest xserver that sddm-greeter-qt6 is crashing, which then takes down xserver with it.
Possibly you may avoid the issue with a switch to LightDM or GDM using sudo update-alternatives --config default-displaymanager. If neither are offered, you may add with zypper or YaST. I suggest LightDM if you need to install one.
Thx for your quick reply! Yeah, substituting SDDM would likely get rid of its crash and its taking down xserver with it, which from my reading was/is(?) possibly triggered by SDDM’s breeze theme.
Since atm I’m back to a running system, with SDDM albeit w/o latest xserver packages, I’m hoping the next snapshots containing Qt6, SDDM, X11 or Breeze theming stuff might do away with this strange glitch. Figured I’d post my experience since I saw other people struggling with no login screens probably not related plymouth.
I guess the takeaway is, if you get no login screen, check system journal whether X11 is dying due to SDDM crash, and if you want to stay with SDDM, keep to previous xorg-x11 version (21.1.14-1.1 in my case) to get the login screen back.
For me SDDM works on every PC except my SusePrime Laptop.
For me it seems that something with Nvidia drivers, SDDM und SusePrime is not working.
Switching back to offload solves the SDDM issue for me, for some games then starting on igpu not a good solution.
For my configuration i could enter my password on the black screen and the desktop started without issues.
Hi, i´ve tried to downgrade Mesa from the before installed packman version without a change of this behaviour. It looks to me that these nvidia drivers are the problem again. Because it´s working without suse prime, it could be a matter that last week an update had issues in dracut creating the bootimage (had to make a hard reset) with the i915 driver, maybe this is the reason of this weird behaviour, allthough i don´t need i915 drivers.
Okay, i played with Suse-Prime.
The Problem occured only with my Optimus Laptop with AMD/NVIDIA Graphics.
With amd it worked for me, with nvidia not.
I wanted to try the offload mode, but this didn’t work.
I had to install bbswitch manually, then install x drivers for amd (the kernel drivers didn’t match) and stop Suse-Prime with prime-select unset and restart Suse-Prime with prime-select restore service.
Now bbswitch was recognized well and prime-select boot offload worked.
After that the Laptop bootet with login screen and games work.
Sounds for me like i made an mistake at first setup of Suse-Prime.
This works for my problem with a black login-screen and saves power.
Sorry for my late reaction, I didn’t find time to investigate further and was happy the system functioned w/o xorg-x11-server update from TW20241205. Since I hadn’t yet dup’ed to TW20241206 I excluded Mesa stuff from being part of the problem.
@Simonowski, I also have suse-prime installed on this notebook, so thx for adding that to the equation. In contrast to you, I couldn’t enter a password in the black screen b/c in my case SDDM greeter was truly gone (crashed SDDM process and SIGTERM to xserver as seen in systemd journal). But reviewing my notes, I can confirm that when I set up this older notebook I also had to install bbswitch manually for suse-prime offload to work correctly for my specific hw combo (i7-6820HQ with Intel HD Graphics 530 and Nvidia Quadro M1200). Glad it now also works for you.