Your message dated Wed, 04 Mar 2026 15:03:58 +0000
with message-id <[email protected]>
and subject line Bug#1129276: fixed in systemd 260~rc2-1
has caused the Debian Bug report #1129276,
regarding systemd: Getty not started after upgrade to 260~rc1
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.)


-- 
1129276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1129276
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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: 

* [email protected] gained an [Install] and must now be explicitly enabled
  to be active.

So one now has to run "systemctl enable [email protected] && 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

--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 260~rc2-1
Done: Luca Boccassi <[email protected]>

We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Luca Boccassi <[email protected]> (supplier of updated systemd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 04 Mar 2026 13:40:07 +0000
Source: systemd
Architecture: source
Version: 260~rc2-1
Distribution: unstable
Urgency: high
Maintainer: Debian systemd Maintainers 
<[email protected]>
Changed-By: Luca Boccassi <[email protected]>
Closes: 1129276
Changes:
 systemd (260~rc2-1) unstable; urgency=high
 .
   * Remove build-depend on rsync, meson is new enough
   * Enable getty@ via packaging scriptlets, not static anymore (Closes:
     #1129276)
   * Update upstream source from tag 'upstream/260_rc2' Update to upstream
     version '260~rc2' with Debian dir
     9c39b1f4781cb5ab95271453bfa0b453e971da5b
     Fixes:
     https://github.com/systemd/systemd/security/advisories/GHSA-6pwp-j5vg-5j6m
   * Install new files
Checksums-Sha1:
 40e1d7a3b60e981a861502d147b91b22a764ae5d 8634 systemd_260~rc2-1.dsc
 64f3e5ac37981110c4757b78e8415b1d8df57aa9 17531526 systemd_260~rc2.orig.tar.gz
 318d6f3a1d737acda062db544931aba218adb9cd 185032 systemd_260~rc2-1.debian.tar.xz
 68403aaa1710d91e84b96ef0cd488221bc6c9e3f 14633 
systemd_260~rc2-1_source.buildinfo
Checksums-Sha256:
 034400395faf6ebaa97f5d83a5579f70296b5f5923d57d790e2cdb728178ecf2 8634 
systemd_260~rc2-1.dsc
 a4232d479b8e19f63ef907df06d148bc32b4f872d212bb60739cf045a89475c6 17531526 
systemd_260~rc2.orig.tar.gz
 522e21d3f717e12615c7bec2bab00604c80839dc26fe9d7d82558bddb5fc9c08 185032 
systemd_260~rc2-1.debian.tar.xz
 6b94e63c034ac4fe449447c029f5acb5fde3682d669a5c1e63591618f1d578ed 14633 
systemd_260~rc2-1_source.buildinfo
Files:
 c01f5d88cf636fa4db22a2f1ba74536d 8634 admin optional systemd_260~rc2-1.dsc
 1a5d29eeea6b0ae298c58c7a20d9ca8d 17531526 admin optional 
systemd_260~rc2.orig.tar.gz
 fa8e44a79d85ed4425409b1d0a9c2659 185032 admin optional 
systemd_260~rc2-1.debian.tar.xz
 83faafc7a1b57c95d9f320f78e986a7c 14633 admin optional 
systemd_260~rc2-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmmoQ1ERHGJsdWNhQGRl
Ymlhbi5vcmcACgkQKGv37813JB42CxAAkLp9eiC8j5TfqeIjLF185XFgiHX0iZen
SbpTUZDD6lljpw0nhHdGhUKhNh8CeiuALqmKnG1S2KxsNZ/Oz5EAPZdD3cWbA2TX
rrFvVbfRkSA0mLz2CLqHBc2EXrMKVazkD8y50GR4p2WL8MTe+gRhmdj2LahZt/j7
ujnRV1VF4zAvtAsbNV4EOozuFHPHbvuhh0GNgC6n/fgtFyRTQ3g65gDMZ/RE1UNW
jXpDHrtONcWB6ns/qx5g3WHynGEYmTax0RXaT8yRb6MS5GcYg4VD675LWEH9zAuP
oS6KQVRrqMGOZXwAIjnDhPYFQrH6elU7yZawQ4HivDfL3ike89kPLAYMY/iRTvFi
qM9+EalKCVUrB6psdhbFo7Z/QWX8Kkgbio1wKoSR2yGtWTeYjpui69qdxBiK2UGd
LSZs3WMVZWWp4swXnJ3ovBveP7MEq+qPYdK327DQmtV3m6p3Rkg1J7rLH5BJ5ucI
2sngYj6Wp9nOqsqvSj4ZuvlbW766XwvATKrlgbXT2K2YpxwmKFpQrDP4Xp27UlOG
zMsq4zxD/u6AXLHWPnv0Wx2I1Tv3rd+vnvgJE0UWWOpY1NEJawWv6QG1y8IDfraj
AJC1tosw5jByUJFdpLb98Xsyrmz9veb/GnTxvTwJil7U7rM0tnqm0gMQdZgbfamY
pdHJ5wYJseA=
=nZa/
-----END PGP SIGNATURE-----

Attachment: pgpsPrB7XtWW6.pgp
Description: PGP signature


--- End Message ---

Reply via email to