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 324337 - can't disable "automatic" or "timed" log-in features.
can't disable "automatic" or "timed" log-in features.
Status: RESOLVED FIXED
Product: gdm
Classification: Core
Component: general
2.13.x
Other Linux
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2005-12-17 15:59 UTC by Sebastien Bacher
Modified: 2005-12-25 01:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Sebastien Bacher 2005-12-17 15:59:21 UTC
This bug has been opened here: http://bugzilla.ubuntu.com/show_bug.cgi?id=21139

"Just installed a fresh copy of Dapper Flight-2, and I notice a werid problem
with GDM.

I enabled the "timed log-in" option, and also the "automatic" log-in.
It works fine.
Problem: I then disabled both options, but it has no effect. That is, it will
still log me automatically when I start the machine, and if I log-out, it will
log me back in automatically after 30 seconds.

I thought maybe it could be a problem in gdm-setup which perhaps failed to
update the gdm configuration file properly, but no.
Here are the relevant (I think?!) lines of /etc/gdm/gdm.conf

[daemon]
# Automatic login, if true the first local screen will automatically logged
# in as user as set with AutomaticLogin key.
AutomaticLoginEnable=false
AutomaticLogin=vincent

# Timed login, useful for kiosks.  Log in a certain user after a certain
# amount of time
TimedLoginEnable=false
TimedLogin=vincent
TimedLoginDelay=30

According to that file, I have indeed disabled both automatic and timed log-in.
But gdm somehow acts as if they were still enabled !

Anything I can do to help, just ask..."
Comment 1 Brian Cameron 2005-12-21 01:47:10 UTC
This is strange.  Did you restart the gdm daemon by running gdm-restart or rebooting the machine?  You can try running the following command:

gdmflexiserver --command="GET_CONFIG daemon/AutomaticLoginEnable" 

and similar commands for the other keys.  This will tell you what the daemon thinks the values are set to.  Is the GDM daemon telling you that it thinks the values are true or false?

I bet if you blank the AutomaticLogin and TimedLogin values it will disable it.
What version of GDM are you using?  
Comment 2 Sebastien Bacher 2005-12-23 10:04:20 UTC
(In reply to comment #1)
> This is strange.  Did you restart the gdm daemon by running gdm-restart or
> rebooting the machine?  

The machine has reboot quite a bunch of time since the update

> gdmflexiserver --command="GET_CONFIG daemon/AutomaticLoginEnable" 
> 
> and similar commands for the other keys.  This will tell you what the daemon
> thinks the values are set to.  Is the GDM daemon telling you that it thinks the
> values are true or false?

$ gdmflexiserver --command="GET_CONFIG daemon/AutomaticLoginEnable" OK false

$ gdmflexiserver --command="GET_CONFIG daemon/TimedLoginEnable" OK false


> I bet if you blank the AutomaticLogin and TimedLogin values it will disable it.

Clearing the AutomaticLogin does the trick

> What version of GDM are you using?  

current tarball, 2.13.0.3
Comment 3 Brian Cameron 2005-12-25 01:27:43 UTC
I can recreate this problem, and I just fixed it in CVS head.