From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
I must be lucky, works just fine for me with SDDM configured for Wayland only, autologin to a Wayland session.
max-p@media ~ % cat /etc/sddm.conf
[Autologin]
User=max-p
Session=plasma
#Session=plasma-bigscreen
Relogin=true
[General]
DisplayServer=wayland
Same here. No trouble with sddm.
Mind sharing what your distro and version are? The problem seems to be present on Fedora and OpenSUSE mostly, from what I can see of the issues posted online.
As far as I can tell, sddm.conf is the legacy conf location and the more recent SDDM/KDE versions are now placing the settings in /etc/sddm.conf.d/kde_settings.conf...not that that itself should matter much here.
Arch. That leads me to believe it's possibly a configuration issue. Mine is pretty barebones, it's literally just that one file.
AFAIK the ones in sddm.conf.d are for useful because the GUI can focus on just one file without nuking other user's configurations. But they all get loaded so it shouldn't matter.
The linked bug report seems to blame PAM modules, kwallet in particular which I don't think I've got configured for unlock at login since there's no password to that account in the first place.
Thanks for the info. I don't enable the Kwallet service at all either, so I don't think that would be it, but who knows. At any rate, I rechecked my config and even moved the settings to /etc/sddm.conf without success. It seems I'm not alone at least, so I'll just stick with GDM until I can troubleshoot further.
I am using Fedora 40 Kinoite with autologin on SDDM, no trouble and never had.
Interesting. I followed the documentation from the various distros (Arch, Debian, and openSUSE), and added the following to /etc/sddm.conf.d/10-autologin.conf:
[Autologin]
Relogin=false
Session=plasma (I've also tried plasma.desktop here)
User=thayer
I've confirmed that plasma.desktop exists in /usr/share/wayland-sessions/ and it's the session I normally select regardless of DM used.
I've also tried placing the autologin text in /etc/sddm.conf, /etc/sddm.conf.d/autologin, and the default /etc/sddm.conf.d/kde_settings.conf. No matter where it's saved, the settings are ignored and I'm brought right back to the greeter upon reboot. Nothing is logged in journald and SDDM doesn't write to its own log in /var/log.
I've also tried the above with and without the KDE Wallet service enabled (I normally keep it disabled).
If I use the System Settings GUI to set the above details (via Colors & Themes > Login Screen (SDDM) > Behavior), the System Settings app crashes upon close. I've had multiple updates since rebasing to Kinoite, so the chance of a corrupted package is nil.
Something is definitely afoot.
This bug is so old and tbh its a big f*** y** for KDE developement or whoever is responsible for this shitshow called SDDM. Its the reason my desktop pc is running LDM for multiple years now, since I stumbled over this.
But yeah, we need more KDE specific tools tralalala, instead of a working login manager.
If you want to interact as little as possible with the display manager, try using lightdm, it will also autologin and it's lighter than gdm.
That was my first choice alternative, but I had no success with any of the available LightDM greeters under Fedora 40 Kinoite (autologin, slick or gtk). They all resulted in a "Failed to start seat: seat0" error, even after ensuring logind-check-graphical=true was set. I may give it another go when I have the time.
Oh I just installed lightdm in arch, disabled whatever I had, enables that service and activated the autologin by writing my username in some files I don't remember anymore. And that was it.
Due to some hardware issues I had I even had no service enabled and used to start it manually from a non GUI environment every time I logged on, and it worked fine. Now it's properly enabled though.