Greetings
Rotschopf
--
Es ist nichts sicher, ausser dass nichts sicher ist, und nicht einmal das.
--
To UNSUBSCRIBE, email to debian-lap...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
I've had a similar problem with gdm. I solved it by removing gdm and
installing a different version of gdm. I'm sorry I can't be more
specific, but I've forgotten the versions involved.
To remove gdm you'll have to log in in non-X mode. You probably already
know how to do this, but if not, boot up in "single mode." That is, if
you're using Lilo and your Debian entry is called "Linux", when you see
the Lilo prompt press Shift and type "Linux single" and then press
enter. You'll boot up into a non-X, non-network mode, and you can then
log in as root and type "apt-get remove gdm." Then go to Debian's web
site and use the package search feature to find the different versions
of gem available. Pick a different one, download and try it (install it
with dpkg -i).
Good luck.
Tony
Make sure that gdm isn't trying to start on a VT that has a getty
running on it. If you can ssh/telnet into your machine try (as root)
"fuser -v /dev/tty?" which should tell you if this is happening. I had
the same problem and I had to change the line that said "0=Standard"
to "0=Standard vt7" in the "[servers]" section of gdm.conf.
HTH
dt
--
Dave Thayer | If trees could scream, would we be so cavalier about
Denver, Colorado USA | cutting them down? We might, if they screamed all
da...@thayer-boyle.com | the time, for no good reason. - Jack Handey