No. That value just tells gdm how long to wait for X to start up before deciding that X has hung, to kill it and try starting it again. So my guess is that if the machine is slow:
1. X takes longer to start than GdmXserverTimeout allows, because other background processes started during boot are getting themselves initialized and keeping the system busy. 2. gdm kills X and tries to start it again. 3. By this time, most of the background processes have finished initializing, so X starts up quickly enough this time to avoid getting killed by gdm. 4. I'm guess that for some reason, gdm doesn't honor the autologin after having killed X once. If I get a little time I'll take a look in the gdm source to see if that's a correct explanation... Steve -- Jaunty's GDM Autologin doesn't work anymore https://bugs.launchpad.net/bugs/370541 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
