On Sun, 15 Feb 2026 09:49:58 +0100 Salvatore Bonaccorso <[email protected]> wrote: > Control: tags -1 + moreinfo > > Hi, > > On Sat, Feb 14, 2026 at 09:10:48PM +0000, Vivek wrote: > > Source: linux > > Version: 6.12.69-1 > > Severity: important > > X-Debbugs-Cc: [email protected] > > > > Dear Maintainer, > > > > System boots successfully through services but hangs with flashing underscore after last [OK] message of "started libvirtd.service". > > > > No further progress to graphical login > > > > TTY 2-6 accessible > > > > systemctl status sddm shows active (running) initially > > journaljtl -u sddm -b only shows: > > > > Initializing > > Starting > > Logind interface found > > > > Main workaround was booting into older kernel 6.12.63 works perfectly > > Forcing DisplayServer=x11 does nothing > > > > Expected: SDDM login screen appearing > > > > Observed: Stuck flashing underscore post-libvirtd, no GUI > > > > Steps to reproduce: > > Boot with problematic kernel > > Observe boot messages reach libvirtd OK > > Flashing underscore present > > > > Hardware - > > I5 7500 > > MSI H110i PRO > > GTX 1050 2GB > > 32GB RAM > > Can you please provide the full boot log from the system boot where > you do not get the graphical login. You might be able to access the > log online if the system is accessible via ssh or retrospectively from > the system journal. > > Additially please provide the information gathered by 'reportbug > kernel' so we gather inforation on HW, system configuration, loaded > modules. > > Regards, > Salvatore > >
Hi Salvatore, thanks for your response I was able to fix the issue today after posting on Reddit ( https://www.reddit.com/r/debian/s/6nDh9hBZKW) The main issue was that the Nvidia drivers were not rebuilt for 6.12.69-1 because the linux-headers-amd64 metapackage was not installed. After installing it and forcing dkms rebuild with sudo apt update && sudo apt install linux-headers-amd64 && sudo dkms autoinstall The system booted normally with the SDDM greeter So this was not in fact a kernel bug but a symptom of user error since the Nvidia dkms dependency was not on my system Unfortunately I cannot provide the information requested since the system is functional again Feel free to close this bug if you would like to Thanks for your time Kind regards, Vivek
