Bug 413377

Summary:	Setting auto-login for a user does not change config files
Product:	[Applications] systemsettings	Reporter:	Rik Mills <rikmills>
Component:	kcm_users	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	nate, wojtasjd
Priority:	NOR
Version:	5.16.4
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:

Description Rik Mills 2019-10-24 00:05:03 UTC

SUMMARY

Setting auto-login for a user appears to work, but it does not alter the config file. Hence auto-login does not work, and returning to user-manager show it as unset for the user.

STEPS TO REPRODUCE
1. Set auto-login for a user
2. Authorise this for the user, then to alter the sddm config. It appears to apply.
3. Try to auto-login, or reload user-manager. Observed that the setting did not apply.

OBSERVED RESULT

Config remains unaltered


EXPECTED RESULT

Autologin enabled for that user

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon
KDE Plasma Version: 5.17.1
KDE Frameworks Version: 5.63
Qt Version: 5.13.1

ADDITIONAL INFORMATION

I should also note that sddm-config KCM can successfully set the config file, if you use that to enable auto-login.

Comment 1 WojtasJD 2019-10-25 19:08:25 UTC

I can confirm this behavior on two machines with KDE neon 5.17.1 installed - in my case I cannot switch off auto-login for a user in "user-manager":

1. Issue this command from Konsole:
$ kcmshell5 user_manager

2. Unset auto-login for a user
3. After entering password (ID: org.freedesktop.accounts.user-administration) Konsole throws this:
QDBusArgument: read from a write-only object
QDBusArgument: read from a write-only object
QDBusArgument: read from a write-only object

4. After entering password (ID: org.kde.kcontrol.kcmsddm.save) Konsole throws this:
Warning from helper: QFSFileEngine::open: No file name specified
Warning from helper: Empty filename passed to function

5. Close and open "user-manager" - setting is not saved.

Comment 2 Nate Graham 2020-01-21 16:16:42 UTC


*** This bug has been marked as a duplicate of bug 342722 ***