After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 690164 - UI for Adding Users Interface enhancement/fix
UI for Adding Users Interface enhancement/fix
Status: RESOLVED INCOMPLETE
Product: gnome-control-center
Classification: Core
Component: User Accounts
3.4.x
Other Linux
: Normal enhancement
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-12-13 15:56 UTC by mle
Modified: 2013-06-13 07:18 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description mle 2012-12-13 15:56:28 UTC
gnome-control-center                          1:3.4.2-2 LMDE (Debian Testing)
Gnome Version 3.4.2


My request is that when creating new users the next step is NOT "account disabled" by default. 

Because there is no visual cue, it took me a while to find that clicking the words ellicited a drop down list of password modes. 
(Once I discovered that it was clickable, I can see how well it is designed. I love that I can set it so that new users can choose their own password - Very Good feature.) 
I suggest that it there is some visual cue that shows that there is a drop down and/or that there is an additional dialogue during user creation that then ensures that the Admin chooses the required new user password status.  Setting to disabled is not logical to the extent that I thought it was broken.  The context is that I have just created a new user so why would their account be disabled by default? : )  My fix was to go back to the CLI to create the accounts.  I thought it was a bug and started bug hunting/filing.
Comment 1 Bastien Nocera 2012-12-17 15:10:22 UTC
The UI's been changed for the password generation in GNOME 3.6.
Please check whether this is fixing the problem for you.
Comment 2 Tobias Mueller 2013-06-13 07:18:53 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!