GNOME Bugzilla – Bug 649816
Disabled accounts can be set to autologin
Last modified: 2011-09-30 12:39:44 UTC
Description of problem: Disabled accounts can be set to log in automatically. Version-Release number of selected component (if applicable): control-center-3.0.1.1-4.fc15 How reproducible: always Steps to Reproduce: 1. 'System settings' -> 'User Accounts' -> Add user 2. By default the account is disabled until you enter a password (see bug 703216) Actual results: Although the account is disabled it can be set to automatic login. This results in no login the next time you start GDM Expected results: 1. The autologin option should not be available for disabled accounts 2. Automatic login should be possible without passwords.
Bug 703216?
Never mind, it's bug 649814
Yes, bug 649814 is the correct one. Sorry for the typo. Bug 649814 is about accounts without password that cannot be enabled. This bug is about accounts that can be set to auto login although they are disabled.
*** Bug 649814 has been marked as a duplicate of this bug. ***
Ok, as Philippe pointed out in bug 649814 the two bugs were indeed related. Right after creation of an account the field "Password" reads "This account is disabled" (instead of "None" which is correctly displayed later), so *enabling* the account is seems logical. However disabling or enabling an account has *nothing* to do with the password. Even if you disable an account the password remains the same. This being said the disable/enable option should not be in the password dialog but in the accounts dialog. It should be a slider below "Password" and above "Automatic login". Automatic login should then only be greyed out and only become available if the account is really enabled. This would fix this bug and avoid confusion as in bug 649814. Does this make sense?
The following fix has been pushed: 64419bf users: prevent autologin for disabled users
Created attachment 194715 [details] [review] users: prevent autologin for disabled users gdm can't handle this currently, so prevent this situation from happening. Forcibly turning off the autologin when an account is disabled is a slightly odd side-effect, but good enough in practice.
The issue seems to still be there in 3.2.0...