Bug#1130765: Do not run systemctl enable getty at .service unconditionally on each upgrade
Michael Biebl
biebl at debian.org
Sat Mar 14 21:24:30 GMT 2026
Package: systemd
Version: 260~rc4-1
Severity: normal
I have kmscon installed and enabled:
# systemctl enable kmsconvt at .service
Created symlink '/etc/systemd/system/autovt at .service' → '/usr/lib/systemd/system/kmsconvt at .service'.
Created symlink '/etc/systemd/system/getty.target.wants/kmsconvt at tty1.service' → '/usr/lib/systemd/system/kmsconvt at .service'.
systemd.postinst runs "systemctl enable getty at .service" unconditionally,
which leads to the following error message
Failed to enable unit: File '/etc/systemd/system/autovt at .service' already exists and is a symlink to /usr/lib/systemd/system/kmsconvt at .service
bug systemctl also creates
/etc/systemd/system/getty.target.wants/getty at tty1.service
(via DefaultInstance=tty1)
getty at tty1.service and kmsconvt at tty1.service conflict with each other.
I thus suggest running "systemctl enable getty at .service" only on new
installs and as a one-upgrade upgrade.
The explicit "systemctl enable getty at tty1.service" can be dropped
accordingly.
More information about the Pkg-systemd-maintainers
mailing list