Bugzilla – Bug 1226053
SDDM + Wayland + Autologin not working
Last modified: 2024-06-07 12:30:55 UTC
Overview: Whenever I set autologin to on for the SDDM with Wayland, it never auto logs in, but waits for my password instead; - OR sometimes ends up with a black screen showing only the mouse pointer. Steps to Reproduce: System Settings > Startup and Shutdown > Login Screen (SDDM) > Behavior > Tick automatically log in as user fill out username and select Wayland > click Apply. Actual Results: Reboot, and the login screen appears, not auto logging in, but waiting for password input; - OR hanging with a black screen with the mouse pointer only visible. Expected Results: User should be automatically logged in to the desktop within the Wayland session. Additional Information: I also tried to use both YaST sysconfig editor and Yast User and Group manager to customize autologin methods, to no avail. System info: Operating System: openSUSE Tumbleweed 20240605 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 Manufacturer: MSI Product Name: MS-7972 System Version: 2.0
Possible dup of: boo 1202078 boo 1200436
(In reply to hui from comment #1) > Possible dup of: > boo 1202078 > boo 1200436 Already checked these, but seeing those "related" bug reports opened ~1-2+ years, I'm sure that its related to opensuse because: on my endeavouros installment sddm works out of the box for wayland autologin. Isn't it something to do with the opensuse's "custom" way of using sddm configs which reside within the /usr/lib/sddm/sddm.conf.d/* instead of the "regular" /etc/sddm.conf.d/ ? Observation: on a fresh installment, the /etc/sddm.conf.d is empty, but when customizing the SDDM from within plasma's settings, /etc/sddm.conf.d/kde_settings.conf gets generated (which is a normal behaviour) - however, when this file gets generated the autologin stops. If I remove this file, the autologin works thanks to Opensuse's /etc/sysconfig/displaymanager - however this approach only lets autologin for X11 sessions by default, and there seems no way to changing that. Observation2: I have a testing machine, where the autologin right into wayland just simply works after setting it auto within the same SDDM plasma settings.
kcm_sddm is supposed to write kde_settings.conf as well as /etc/sysconfig/displaymanager. Can you verify that the latter has the right value set for DISPLAYMANAGER_AUTOLOGIN?
(In reply to Fabian Vogt from comment #3) > kcm_sddm is supposed to write kde_settings.conf as well as > /etc/sysconfig/displaymanager. > Can you verify that the latter has the right value set for > DISPLAYMANAGER_AUTOLOGIN? Sure: DISPLAYMANAGER_AUTOLOGIN="vajdao" Also, you mentioned kcm_sddm, should it get installed by default distro install process? Because now I checked with zypper, and its not installed (checked zypper history log, it wasn't mentioned anywhere). However sddm-kcm6 is installed, so basically this is how my zypper se -s sddm looks like: LANG=C zypper se -s kcm Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+------------------------+---------+-------------+--------+----------- | fcitx5-configtool-kcm6 | package | 5.1.5-1.1 | x86_64 | repo-oss i | flatpak-kcm6 | package | 6.0.5-1.1 | x86_64 | repo-oss i | flatpak-kcm6-lang | package | 6.0.5-1.1 | noarch | repo-oss | kcm_fcitx5 | package | 5.1.5-1.1 | x86_64 | repo-oss | kcm_sddm | package | 5.27.10-1.3 | x86_64 | repo-oss | kcm_sddm-lang | package | 5.27.10-1.3 | noarch | repo-oss | kcmutils-devel | package | 5.116.0-1.1 | x86_64 | repo-oss | kcmutils-imports | package | 5.116.0-1.1 | x86_64 | repo-oss | kf5-kcm-fcitx | package | 0.5.6-4.2 | x86_64 | repo-oss | kf5-kcm-fcitx-icons | package | 0.5.6-4.2 | noarch | repo-oss i | kf6-kcmutils | package | 6.2.0-1.1 | x86_64 | repo-oss | kf6-kcmutils-devel | package | 6.2.0-1.1 | x86_64 | repo-oss i | kf6-kcmutils-imports | package | 6.2.0-1.1 | x86_64 | repo-oss i | kf6-kcmutils-lang | package | 6.2.0-1.1 | noarch | repo-oss i | libKF5KCMUtils5 | package | 5.116.0-1.1 | x86_64 | repo-oss i | libKF5KCMUtils5-lang | package | 5.116.0-1.1 | noarch | repo-oss i | libKF5KCMUtilsCore5 | package | 5.116.0-1.1 | x86_64 | repo-oss i | libKF6KCMUtils6 | package | 6.2.0-1.1 | x86_64 | repo-oss i | libKF6KCMUtils6-lang | package | 6.2.0-1.1 | noarch | repo-oss i | libKF6KCMUtilsCore6 | package | 6.2.0-1.1 | x86_64 | repo-oss i | libKF6KCMUtilsQuick6 | package | 6.2.0-1.1 | x86_64 | repo-oss i | sddm-kcm6 | package | 6.0.5-1.1 | x86_64 | repo-oss i | sddm-kcm6-lang | package | 6.0.5-1.1 | noarch | repo-oss | sssd-kcm | package | 2.9.5-1.2 | x86_64 | repo-oss i | trash_kcm | package | 24.05.0-1.1 | x86_64 | repo-oss i | wacomtablet-kcm6 | package | 6.0.5-1.1 | x86_64 | repo-oss i | wacomtablet-kcm6-lang | package | 6.0.5-1.1 | noarch | repo-oss
(In reply to Örs from comment #4) > (In reply to Fabian Vogt from comment #3) > > kcm_sddm is supposed to write kde_settings.conf as well as > > /etc/sysconfig/displaymanager. > > Can you verify that the latter has the right value set for > > DISPLAYMANAGER_AUTOLOGIN? > > Sure: > DISPLAYMANAGER_AUTOLOGIN="vajdao" Ok, so that should work. I wonder whether it's really autologin not working if configured with the KCM or it's a duplicate of the already mentioned bug reports, which just make autologin (very) unreliable. Please attach the journal for the boot until attempted autologin. > Also, you mentioned kcm_sddm, should it get installed by default distro > install process? sddm-kcm6 is the correct one kcm_sddm is just the package name for Plasma 5.
(In reply to Fabian Vogt from comment #5) > (In reply to Örs from comment #4) > > (In reply to Fabian Vogt from comment #3) > > > kcm_sddm is supposed to write kde_settings.conf as well as > > > /etc/sysconfig/displaymanager. > > > Can you verify that the latter has the right value set for > > > DISPLAYMANAGER_AUTOLOGIN? > > > > Sure: > > DISPLAYMANAGER_AUTOLOGIN="vajdao" > > Ok, so that should work. > > I wonder whether it's really autologin not working if configured with the > KCM or it's a duplicate of the already mentioned bug reports, which just > make autologin (very) unreliable. > > Please attach the journal for the boot until attempted autologin. > > > Also, you mentioned kcm_sddm, should it get installed by default distro > > install process? > > sddm-kcm6 is the correct one kcm_sddm is just the package name for Plasma 5. I hope this will be helpful, if no please tell me what other commands should I input to my terminal for journal :) I used: sudo journalctl -b (is there a GUI or a more easy way of extracting journals btw via YaST maybe?) https://paste.opensuse.org/pastes/12967b80a584
any progress @Fabian Vogt ? could you gather any info from the journal?
(In reply to Örs from comment #6) > I hope this will be helpful, if no please tell me what other commands should > I input to my terminal for journal :) I used: sudo journalctl -b (is there > a GUI or a more easy way of extracting journals btw via YaST maybe?) > https://paste.opensuse.org/pastes/12967b80a584 > sddm-helper[1660]: Failed to take control of "/dev/tty1" ("root"): A művelet nem engedélyezett Yeah, bug 1221507. Unfortunately not trivial to fix without cooperation from systemd. *** This bug has been marked as a duplicate of bug 1221507 ***
(In reply to Fabian Vogt from comment #8) > (In reply to Örs from comment #6) > > I hope this will be helpful, if no please tell me what other commands should > > I input to my terminal for journal :) I used: sudo journalctl -b (is there > > a GUI or a more easy way of extracting journals btw via YaST maybe?) > > https://paste.opensuse.org/pastes/12967b80a584 > > > sddm-helper[1660]: Failed to take control of "/dev/tty1" ("root"): A művelet nem engedélyezett > > Yeah, bug 1221507. Unfortunately not trivial to fix without cooperation from > systemd. > > *** This bug has been marked as a duplicate of bug 1221507 *** Thanks, I see that its resolved upstream, but can't see the resolution - can you send us a source just to see its progress? Also any info about when it comes into tumbleweed?
(In reply to Örs from comment #9) > (In reply to Fabian Vogt from comment #8) > Thanks, I see that its resolved upstream, but can't see the resolution - can > you send us a source just to see its progress? Also any info about when it > comes into tumbleweed? It's "RESOLVED UPSTREAM" in the sense that any development happens upstream. There's no fix yet.