Bug#1129276: systemd: Getty not started after upgrade to 260~rc1

[Michael Biebl]

On Sat, 28 Feb 2026 17:26:11 +0100 Vincent Crevot 
<vincent.crevot at gmail.com> wrote:
> 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 think the proper solution is to run
`systemctl enable getty at .service` in systemd.postinst.

This will create a autovt at .service → getty at .service symlink thus and 
re-enable autospawning of gettys.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20260228/b134cec6/attachment.sig>