suddenly passwordless autologin doen’t work any longer - I have to provide a password. It had worked after installation.
yast → user management → expert options shoe the correct user and login without password is set
in /etc/sysconfig/displaymanager DISPLAYMANAGER_AUTOLOGIN shows the correct user and DISPLAYMANAGER_PASSWORD_LESS_LOGIN=“yes”
I’m using KDE/plasma.
/etc/sddm.conf does not exist and /etc/sddm.conf.d is empty
any suggestions how I can achiev the passwordless autologin again?
is it possible that the installed window manager are in conflict?
in the lower left of the login screen, plasma (X11) is shown. is that correct?
in /etc/sysconfig/displaymanager: DISPLAYMANAGER_XSERVER=“Xorg”
is that correct?
which logfiles might give me an indication of why autologin is not working?
which packages might affect the autologin behavior?
Here’s what I have, it’s from TW but that should not matter
knurpht@Lenovo-P16:/etc/sddm.conf.d> more kde_settings.conf
[Autologin]
Relogin=false
Session=default.desktop
User=
[General]
HaltCommand=
RebootCommand=
[Theme]
Current=breeze-openSUSE
[Users]
MaximumUid=60000
MinimumUid=1000
knurpht@Lenovo-P16:/etc/sddm.conf.d>
Again AFAIK, you need to add your username after the User=
my kde_settings.conf is the same.
my username is set.
for Session= I tried default.desktop as well as kde-plasma
in a different installation where autologin is working, /etc/sddm.conf.d is empty and /etc/sddm.conf does not exist.
…
I remember that once quite a while ago, installing components of a different window manager than KDE caused problems with the KDE default login behavior.
Normally, the config files represent the settings from the GUI. But could you doublecheck:
YaST-> User and Group managment-> dropdown menu in lower right corner “Login settings”
I had checked. the settings are the same.
(there is no option for Session in yast)
Remove the checkmark in YaST settings, apply, redo the checkmark, apply and restart your machine. Any change?
Do you have the same issue with a fresh user profile?
It didn’t make a difference.
I tried further to remove all users but one - no difference
enable it in yast and in KDE, I have it that way so that I get wifi autoconnect and auto login (KDE auto login can work at the same time as YAST autologin in my experience)
is it possible that somehow a different display manager (xdm or icewm ) has taken over sddm?
… I just read in a german forum that someone had a similar problem after installing nvidia drivers (he couldn’t solve it). my problem occured as well after installing nvidia drivers.
how can that be related?
/usr/sbin/update-alternatives --config default-displaymanager
gives
There are 3 choices for the alternative default-displaymanager (providing /usr/lib/X11/displaymanagers/default-displaymanager).
Selection Path Priority Status
------------------------------------------------------------
* 0 /usr/lib/X11/displaymanagers/sddm 25 auto mode
1 /usr/lib/X11/displaymanagers/console 5 manual mode
2 /usr/lib/X11/displaymanagers/sddm 25 manual mode
3 /usr/lib/X11/displaymanagers/xdm 10 manual mode
what is the difference between auto and manual mode for sddm?
Like for any other alternative, “manual” means “use this” and “auto” means “use the best priority”.
The man update-alternative page says:
Link groups are in automatic mode when they are first introduced to the system. If the system administrator makes changes to the system’s automatic settings, this will be noticed the next time update-alternatives is run on the changed link’s group, and the group will automatically be switched to manual mode.
(easy to look up by yourself).
I don’t understand what choices the best priority is selected from when sddm is selected.
Anyway: setting sddm manual mode made it! autologin is working.
I am not able to deduct from this passage what features may allow one of the modes to allow autologin while the other one doesn’t
Neither am I. It is very strange because sddm is sddm, auto mode or not.
I can only guess that the change some way or another made sddm “think” that it is called for the first time and thus initialized things, e.g. re-reading it’s configuration. But that is only a guess and it should of course answer it’s config always.
autologin stopped working again.
displaymanager is still at sddm manual.
what happened inbetween was a kernel update.
or maybe setting the display manager to sddm manual didn’t have an effect and it was accidental that autologin worked worked for whatever other reason