Bugzilla – Bug 1221507
sddm fails to start with DisplayServer=wayland - always attempts to use tty1
Last modified: 2024-06-07 11:42:07 UTC
VERSION_ID="20240314" S | Name | Summary | Type ---+-----------------------------+-----------------------------------+------ i+ | kcm_sddm | A sddm control module for KDE | пакет i+ | kcm_sddm-lang | Translations for package kcm_sddm | пакет i+ | plasma6-sddm-theme-openSUSE | SDDM theme for openSUSE | пакет i+ | sddm | QML-based display manager (Qt5) | пакет i | sddm-branding-openSUSE | openSUSE branding for SDDM (Qt5) | пакет i | sddm-greeter-qt5 | SDDM Greeter for Qt5 themes | пакет i | sddm-greeter-qt6 | SDDM Greeter for Qt6 themes | пакет i | sddm-qt6-branding-openSUSE | Plasma 6 branding for SDDM | пакет bor@uefi:~> cat /etc/sddm.conf.d/wayland.conf [General] DisplayServer=wayland bor@uefi:~> loginctl SESSION UID USER SEAT TTY STATE IDLE SINCE 10 1000 bor - pts/0 active no - 1 sessions listed. bor@uefi:~> мар 16 21:30:47 uefi sddm[1192]: Initializing... мар 16 21:30:47 uefi sddm[1192]: Starting... мар 16 21:30:47 uefi sddm[1192]: Logind interface found мар 16 21:30:47 uefi sddm[1192]: Adding new display... мар 16 21:30:47 uefi sddm[1192]: Loaded empty theme configuration мар 16 21:30:47 uefi sddm[1192]: Using VT 1 мар 16 21:30:47 uefi sddm[1192]: Display server started. мар 16 21:30:48 uefi sddm[1192]: Reading from "/usr/local/share/wayland-sessions/plasmawayland.desktop" мар 16 21:30:48 uefi sddm[1192]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop" мар 16 21:30:48 uefi sddm[1192]: Session "/usr/share/wayland-sessions/plasmawayland.desktop" selected, command: "/usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland" for VT 1 мар 16 21:30:49 uefi sddm-helper[1245]: [PAM] Starting... мар 16 21:30:49 uefi sddm-helper[1245]: [PAM] Authenticating... мар 16 21:30:49 uefi sddm-helper[1245]: [PAM] returning. мар 16 21:30:49 uefi sddm[1192]: Authentication for user "bor" successful мар 16 21:30:54 uefi sddm-helper[1245]: pam_unix(sddm-autologin:session): session opened for user bor(uid=1000) by bor(uid=0) мар 16 21:30:54 uefi sddm-helper[1245]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: pam_sm_open_session мар 16 21:30:54 uefi sddm-helper[1245]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: open_session called without kwallet5_key мар 16 21:30:55 uefi sddm-helper[1245]: [PAM] Preparing to converse... мар 16 21:30:55 uefi sddm-helper[1245]: [PAM] Conversation with 1 messages мар 16 21:30:55 uefi sddm[1192]: Authentication information: SDDM::Auth::INFO_UNKNOWN "Last login: Sat Mar 16 21:24:37 MSK 2024 on tty1" мар 16 21:30:57 uefi sddm-helper[1245]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland" мар 16 21:30:57 uefi sddm-helper[1318]: Failed to take control of "/dev/tty1" ("root"): Operation not permitted Well, tty1 of course belongs to agetty. In X11 mode SDDM is using setUpNewVt() which calls IOCTL VT_OPENQRY while in Wayland mode it starts with vt1 and checks whether there is logind session using it. Of course there is no logind session so it always assumes vt1 is available.
> Well, tty1 of course belongs to agetty. In X11 mode SDDM is using setUpNewVt() which calls IOCTL VT_OPENQRY while in Wayland mode it starts with vt1 and checks whether there is logind session using it. Of course there is no logind session so it always assumes vt1 is available. Yeah, that makes absolutely no sense. Can you file a report upstream instead (if there isn't one already)?
(In reply to Fabian Vogt from comment #1) > > Yeah, that makes absolutely no sense. Can you file a report upstream instead > (if there isn't one already)? There are far too many of them already. https://github.com/sddm/sddm/issues/1844 https://github.com/sddm/sddm/issues/1807 https://github.com/sddm/sddm/issues/1889 And likely more just by browsing titles.
(In reply to Andrei Borzenkov from comment #2) > (In reply to Fabian Vogt from comment #1) > > > > Yeah, that makes absolutely no sense. Can you file a report upstream instead > > (if there isn't one already)? > > There are far too many of them already. > > https://github.com/sddm/sddm/issues/1844 > > https://github.com/sddm/sddm/issues/1807 > https://github.com/sddm/sddm/issues/1889 > > And likely more just by browsing titles. I see... Should be relatively easy to fix, I'll try after the current round of regressions is over.
Just checking in here - are we close to having this resolved? https://github.com/sddm/sddm/pull/1932
I’m struggling with the same issue, and literally tried out everything, but nothing seems to help. To clarify, I have a testing computer, with an nvidia card in it, using G06 propietary drivers, and tumbleweed (of course sddm / plasma) and the sddm autologin works. On my main computer (almost same setup) the autologin does not work, and for context I never had any issues with sddm wayland autologins on other distros (for example endeavourOS!). I’ve wasted 2 days of figuring out what is causing this but to no avail… It seems its TW related (again saying this because I’ve got it proovenly working on other distros) I see that there are multiple issues opened for ages. What could cause this issue, and also how come that autologin works on one machine, and doesnt work on another?! Any fix coming please? I really want to use opensuse as my main distro
*** Bug 1226053 has been marked as a duplicate of this bug. ***
*** Bug 1202078 has been marked as a duplicate of this bug. ***