[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: gdm issues

It seems that this is a very old issue... ummm... I wonder why is it
back. Somebody forgot to apply some debian-specific patch?


I'm still looking for an answer. I can see in syslog there is a lot of
errors like:

May 17 23:46:53 box init: Id "5" respawning too fast: disabled for 5

I have not changed inittab (yes, run-level 5 is my default id); I'm not
sure what introduced this bad behavior yet. X is running on vts5 even
though I said not to dynamically allocate vts and the firstvts is set to
7. Go figure...

Any body has an idea what to do to fix this? Am i the only one
experiencing these problems?

On Sun, 2004-05-16 at 12:30 -0400, Luis M wrote:
> Hello all,
> Lately when I logout to login as a different user, gdm displays an error
> saying that another X server is running and it tries to start X no
> matter what I do. I have posted a few possible solutions in:
> http://www.wlug.org.nz/ApplicationErrorMessages
> (Scroll down to read about the error message).
> Essentially:
> Error:
> "There already appears to be an X server running on display :0.  Should
> I try another display number? ..."
> For my gdm.conf, I copy the factory-gdm.conf file and manually edited
> the entries I need (or care for). But essentially it matches my old
> gdm.conf. The new entries read as:
> [daemon]
> AlwaysRestartServer=true # this is ignored. if i put "false" it restarts
> X regardless
> FirstVT=7 # this seems to be the default anyway
> VTAllocation=false # this is ignored. No matter what you put here gdm
> tries to allocate a vts
> DoubleLoginWarning=false # this is ignored. no matter what you put here
> you still see a "you are logged in in another session" and gives you the
> 3 buttons to: Abort, Ignore, Login to last session. Abort works, the
> other two just take you back to gdm to re-login, and of course you see
> the same message until you CTRL+ALT+FN (where N is a number from 6 to
> 9), and you have to CTRL+ALT+BACKSPACE whatever X servers are running
> else where.
> I really don't know how to fix this problem. I believe the problem got
> introduced when I installed gnome-volume-manager, which pulls udev on
> me. 
> I enabled debug in gdm.conf and i can see in the syslog all kinds of
> things when things failed. The most curious of all is that udev seems to
> create and remove the vc* dev entries. Maybe X/gdm need those and when
> removed gdm has no way to close the X servers, so, it doesn't properly
> restart them? I don't know.
> Here is a list of what I have installed:
> ii  gdm        GNOME Display Manager
> ii  xserver-xfree8 4.3.0.dfsg.1-1 the XFree86 X server
> and running Gnome2.6 from the usual Experimental places (with all the
> latest bleeding edge stuff): Alioth and my favorite Debian mirror.
> Any help appreciated.
> P.S. is there a way that gdm 2.6 can be packaged? say as gdm2.6 or
> something for those of us who might want to take the plunge. I'm about
> to start compiling the source locally and install in /usr/local to see
> if that makes any difference. 
> -- 
> To UNSUBSCRIBE, email to debian-gtk-gnome-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: