It sounds like your /tmp is not being cleared. It is on a tmpfs, on a real disk? Is it mounted with relatime?
Also - why did you decide to use this bug when it is clearly different? Your system boots -- to text mode. Totally different bug that I reported a number of weeks ago (and which was subsequently fixed). Anand On Fri, Nov 13, 2009 at 11:23 PM, beggi dot com <beggij...@gmail.com> wrote: > I have this problem or at least something similar. To put it blunt; gdm > does not start. > > When I start up the computer I get lock-up, blank screen and no response from > the keyboard. After few reboots I usually get the multi-user login, that is. > After few seconds of the white logo splash-screen the computer switches to > text mode and I get: > *Stopping the Firestarter firewall. > *Stopping NTP sever ntp > *Starting the NTP server ntp > > and after that the normal CL login. I have tried to start the gdm from > the command line, but it does not work. If I try to start it as a normal > user I get: > > ** (gdm-binary:2896): WARNING **: Failed to acquire > org.gnome.DisplayManager: Connection ":1.100" is not allowed to own the > service "org.gnome.DisplayManager" due to security policies in the > configuration file > > ** (gdm-binary:2896): WARNING **: Could not acquire name; bailing out > > If I tried to start it as root (sudo gdm) I got: > gdm-binary[2798]: WARNING: Unable to find users: no seat-id found > gdm-binary[2798]: WARNING: GdmDisplay: display lasted 0.038765 seconds > gdm-binary[2798]: WARNING: GdmDisplay: display lasted 0.037873 seconds > gdm-binary[2798]: WARNING: GdmDisplay: display lasted 0.040206 seconds > gdm-binary[2798]: WARNING: GdmDisplay: display lasted 0.037905 seconds > gdm-binary[2798]: WARNING: GdmDisplay: display lasted 0.038138 seconds > gdm-binary[2798]: WARNING: GdmDisplay: display lasted 0.038734 seconds > gdm-binary[2798]: WARNING: GdmLocalDisplayFactory: maximum number of X > display failures reached: check X server log for errors > But I found that this is due to the /tmp/.X0-lock if I delete it I can run > the gdm, buts it behave exactly like it does when I start the machine in a > normal way. > > I have learned, by change, that the only way to get the gdm to start is > to login to the multi-user login, delete the /tmp/.X0-lock file, run > startx as myself, stop the GUI by login me out using the System -> Log > out *user* menu function and then run sudo gdm. > > > I tried to change the "start on" stanza in /etc/init/gdm.conf, Scott mentions > above, but it did not help. The output from "cat /proc/cmdline" is: > root=UUID=2e38cdfc-ed51-4217-b6bf-968eaeb364af ro quiet splash > > > Any ideas > > -- > gdm does not start after bootup > https://bugs.launchpad.net/bugs/447226 > You received this bug notification because you are a direct subscriber > of the bug. > > -- gdm does not start after bootup https://bugs.launchpad.net/bugs/447226 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
