Your message dated Sun, 15 Feb 2026 11:27:47 +0100
with message-id <[email protected]>
and subject line Re: Bug#1127995: linux: Boot hangs at flashing underscore
after libvirtd
has caused the Debian Bug report #1127995,
regarding linux: Boot hangs at flashing underscore after libvirtd
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1127995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127995
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
Thanks
-- System Information:
Debian Release: 13.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.12.69+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Hi Vivek,
On Sun, Feb 15, 2026 at 09:10:47AM +0000, Copper wrote:
[...]
> 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
Thanks for reporting back, in this case I will close the bug.
Note in future Debian releases (forky) the situation will likely be
handled better, as we introduced a base package to keep the kernel
image and headers in sync.
Regards,
Salvatore
--- End Message ---
