3803a880e8
Generally a user-changed operation will be uninteresting, but if the user is currently in the user list and the account changes to locked, we want to remove it from the list, or if the user is not in the list and the account changed to unlocked, we want to add it to the list. This fixes the case where a new user account created in gnome-control-center does not appear in the user list. The password mode is set in the new account immediately after it is created, but the operations are not atomic, so the login dialog considers the new user account when it is still locked and rejects it from being displayed, then immediately afterwards the account is unlocked. This commit causes the login dialog to show the account when this occurs. The containsUser() check here is not strictly necessary, but reduces spurious calls to addUser() and removeUser(), since there's no easy way to check if the locked status of the account has changed (as it's much easier to connect to one signal on the UserManager than to notify::locked on each User object). https://bugzilla.gnome.org/show_bug.cgi?id=758568 |
||
---|---|---|
.. | ||
authPrompt.js | ||
batch.js | ||
fingerprint.js | ||
loginDialog.js | ||
oVirt.js | ||
realmd.js | ||
util.js |