kmscon (10.0.3-1~bpo13+1) trixie-backports; urgency=medium

  Earlier kmscon backports, up to and including 10.0.1-1~bpo13+2, enabled
  kmsconvt@.service automatically when the package was installed for the
  first time. This points autovt@.service at kmscon and adds
  kmsconvt@tty1.service to getty.target next to getty@tty1.service. On
  trixie, display managers such as sddm and gdm3 only declare a conflict
  with getty@tty1.service, so they can end up fighting with kmscon over
  tty1 and the DRM device ("Cannot set drm master" in the journal).

  Starting with this version, kmscon is no longer enabled on new
  installations. Upgrades leave an existing setup alone, so a system on
  which an earlier backport enabled kmscon keeps it enabled.

  If you do not want kmscon to handle the virtual consoles, run

    systemctl disable kmsconvt@.service

  and agetty serves them again.

  If you want to keep kmscon but leave tty1 to a display manager, run

    systemctl mask kmsconvt@tty1.service

  If you want to keep kmscon and also use it on tty1, run

    systemctl disable getty@.service

  so that getty@tty1.service is no longer started next to kmscon. This
  also disables any getty@ttyN.service instances that you enabled by hand.
  When a system with kmscon enabled is later upgraded to Debian 14
  (forky), systemd enables getty@.service once more during the upgrade
  (see #1130765), so run "systemctl disable getty@.service" again after
  that upgrade if you use kmscon on tty1.

  The instructions in README.Debian ("systemctl disable autovt@.service"
  followed by "systemctl enable kmsconvt@.service") are meant for systems
  on which kmscon is not enabled yet. On a system that an earlier backport
  already enabled, the first command disables kmscon instead of agetty.

 -- Boyuan Yang <byang@debian.org>  Sat, 26 Sep 2026 23:35:35 -0400