Hello, I confirm this is still present in latest bullseye having sddm version 0.19.0-2 (amd64)
Maybe this is somehow linked to https://github.com/systemd/systemd/issues/ 12345 ? Is that actually a sddm or a systemd bug ? Regards On Sat, 07 Mar 2020 20:55:57 +0000 Andy Wood <a...@bas.ac.uk> wrote: > Package: sddm > Version: 0.18.1-1 > Severity: important > Tags: patch > > Dear Maintainer, > > * What led up to the situation? > Installed version 0.18.1-1 as provided in bullseye [reboot] > > * What was the outcome of this action? > No login prompt on tty1 [but it is present on other tty's] > > * What outcome did you expect instead? > Normal login prompt on tty1 > > This seems to be caused by entries in /lib/systemd/system/sddm.service > > Changing: > Conflicts=getty@tty1.service getty@tty7.service > After=getty@tty1.service getty@tty7.service > > back to [as per the previous version]: > Conflicts=getty@tty7.service > After=getty@tty7.service > > fixes the problem. > > Andy. > > -- System Information: > Debian Release: bullseye/sid > APT prefers testing > APT policy: (900, 'testing'), (300, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages sddm depends on: > ii adduser 3.118 > ii debconf [debconf-2.0] 1.5.73 > ii libc6 2.29-10 > ii libgcc-s1 10-20200222-1 > ii libpam0g 1.3.1-5 > ii libqt5core5a 5.12.5+dfsg-9 > ii libqt5dbus5 5.12.5+dfsg-9 > ii libqt5gui5 5.12.5+dfsg-9 > ii libqt5network5 5.12.5+dfsg-9 > ii libqt5qml5 5.12.5-5 > ii libqt5quick5 5.12.5-5 > ii libstdc++6 10-20200222-1 > ii libsystemd0 244.3-1 > ii libxcb-xkb1 1.13.1-5 > ii libxcb1 1.13.1-5 > ii qml-module-qtquick2 5.12.5-5