GNOME Bugzilla – Bug 347101
gdmsetup: autologin user ignored if typed from keyboard
Last modified: 2006-12-07 20:15:56 UTC
I want to configure autologin or timed login in gdmsetup (2.14.9). Choosing the username from the dropdown list works perfectly. The widget allows me to enter the username from the keyboard. If I choose this method (it's faster for me to type some characters than to move my hand to the mouse, search from a list, move my hands back...) then the username is not remembered, not even if I type a username that is present on the list. It is simply ignored what I type in this input field. Either the usernamed typed should be properly saved to gdm.conf, or the widget should be replaced by a simple list where keyboard input is disallowed hence the only possibility is to select from the list.
*** Bug 321941 has been marked as a duplicate of this bug. ***
Yes, this is a known bug (refer to duplicate). The current way it works is confusing, and it should be fixed. I'd gladly accept a patch to make this work better. Also note bug #343206 which is a related problem that should also be fixed.
i can confirm this bug. it still exists in gnome 2.16.1
Indeed i have noticed this too. Besides being able to type & select existing users in the drop-down list one should be also able to type commands that can be run through the automatic logon (the latter is going to be a little bit tricky). Hopefully this should be fixed in conjunction with bug #334186
Some more comments: General Tab ----------- + Perhaps "Visual feedback" checkboxes should be on Security tab since this relates to how password field looks? It affects security because someone can look over your head and see how many characters are in your password if visual feedback is turned on. Slightly more secure to leave this off, though it might look worse. However, for some users (like with a11y needs), the feedback may be important to have on. + The "Note" in the "Command" section says you can add different commands separated by semicolons, but it isn't clear where you do this? Perhaps the comment should be more clear about how the "Add" button works. The comment doesn't explain the Add button at all. + Perhaps setting Commands (halt/reboot/shutdown/custom) should be on its own tab? + Should have better labels to explain difference between Label/LRlabel/Text/Tooltip in the Command section when setting Custom Commands. + Should be an easier way to see which commands are enabled/disabled than looking at them and seeing if the Path value is blank. Perhaps the drop-down list should say "(enabled)" or "(disabled)" after the command name. So you would see "Halt command (enabled)" in the list. + When I change custom commands, I see these messages sent to the terminal. Should these debug messages be removed? Could not access configuration key <customcommand/CustomCommand0=> Using compiled in value <> for <customcommand/CustomCommand0=> + In "Default session" I see "foo" listed twice, even though I don't have any sessions named "foo" in my configuration files. Is this an error? Also I see "Failsafe _GNOME" and "Failsafe _Terminal". Probably should avoid putting the + "GtkRC Path" label should probably be "GtkRC file" since you specify a file, not a path. Security Tab ------------ + "Check directory owner", "never place cookies on NFS", "login retry delay", "relax permissions", and "always restart server" maybe should have better labels so it is more clear what these choices do. Note relax permissions can only have 3 values (0,1,2) so checkboxes with the three choices would probably be better here. No need for the end-user to know that in the config file the choices are stored as 0,1,2. 0 - Only allow login if user $HOME directory permissions are secure (default value). 1 - Allow login if group write permissions on user's $HOME directory. 2 - Allow login if all write permissions on user's $HOME directory. + On Security tab might be nicer if Automatic/Timed were below Security section? + Might be nice if the label for Minimal UID mentioned that the default is "100", so if user changes it they can set it back to the default if they want without having to remember the original value. User's Tab ---------- + Probably should be some message in the Users tab to indicate that setting MinimalUID on the Security tab affects what users can be added to Include/IncludeAll. Configure Xserver ----------------- I like the new Priority spinbutton on the "Configure Xserver" popup dialog (from the "Security" tab). The values should go from -20 to +20 rather than 0-100.
Fixed in CVS head. Ignore previous comment (#5) which was intended for a different bug (334186) and can also be seen in that bug.