Bug#1129276: systemd: Getty not started after upgrade to 260~rc1
Vincent Crevot
vincent.crevot at gmail.com
Sat Feb 28 16:26:11 GMT 2026
Package: systemd
Version: 260~rc1-2
Severity: normal
Tags: upstream
With the graphical target active, getty used to be started on demand on
virtual consoles 1 to 6. This was quite useful for debugging problems
with the graphical session : with gdm started on tty1 and a GNOME
session on tty2 I could then switch to tty3 and login from there.
This is no longer case and it seems to be related to this entry in the
systemd 260~rc1 changelog:
* getty at .service gained an [Install] and must now be explicitly enabled
to be active.
So one now has to run "systemctl enable getty at tty3.service && systemctl
daemon-reload" to get the same functionality.
I feel this could at least warrant an entry in the NEWS file of the
package.
Thanks
-- Package-specific info:
-- System Information:
Debian Release: forky/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.18.15+deb14-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii libc6 2.42-13
ii libssl3t64 3.5.5-1
ii libsystemd-shared 260~rc1-2
ii libsystemd0 260~rc1-2
ii mount 2.41.3-4
Versions of packages systemd recommends:
ii dbus [default-dbus-system-bus] 1.16.2-4
ii linux-sysctl-defaults 4.15
ii login 1:4.16.0-2+really2.41.3-4
pn systemd-cryptsetup <none>
ii systemd-timesyncd [time-daemon] 260~rc1-2
Versions of packages systemd suggests:
ii libtss2-tcti-device0t64 [libtss2-tcti-device0] 4.1.3-5
ii polkitd 127-2
pn systemd-boot <none>
ii systemd-container 260~rc1-2
pn systemd-homed <none>
pn systemd-repart <none>
pn systemd-resolved <none>
pn systemd-userdbd <none>
Versions of packages systemd is related to:
ii dbus-user-session 1.16.2-4
pn dracut <none>
ii initramfs-tools 0.150
ii libnss-systemd 260~rc1-2
ii libpam-systemd 260~rc1-2
ii udev 260~rc1-2
-- no debconf information
More information about the Pkg-systemd-maintainers
mailing list