Re: gdm/xdm/login.app weirdnesses
[ cross-posting is not welcomed, btw ]
On Thu, May 20, 1999 at 04:05:23AM -0500, solomon@temple.dhis.org wrote:
> I'm running potato and till recently was running XDM with login.app to
> give the login screen a nice clean look. Then GDM (Gnome Display
> Manager) showed up in unstable so i grabbed it. Next time i rebooted,
> it gave me the gnome login screen and my mouse works, but for some odd
> reason it disables my keyboard. The kb works through bootup but once
> it goes to the gdm login screen my led lights won't even come on & off.
gdm is fighting with getty over the keyboard. I'd guess there's a file
called /etc/X11/gdm/Xservers. You'll need to modify the entry for the local
server and add "vt7" to it, like this:
:0 local /usr/bin/X11/X vt7
(of course, replace vt7 with whatever it's ok for your system)
> The only possible thing i can think of that i might have done was put
> login.app into the wrong runlevel or something...when i initially
> installed login.app it tried to configure before X and XDM were
> configured so it told me to configure later with some config script
> somewhere. When it ran, it asked me which runlevel to put login.app
> into. I know nothing about runlevels, and was given the options 2345
> ...i chose 2.
Login.app is launched by init. The configuration script tries to guess some
sane configuration and suggests that.
> When i decided to install GDM i removed login.app fearing problems; when
> i removed it, it spit some things out about the runlevel stuff.
on removal, it tries to leave things in a sane state. So far, I haven't got
any bug reports regarding this. I'm pretty sure it works ok. (I tested it
under several configurations more than a few dozen times)
> Is it simply a bug in GDM? I suppose i'll see...
it's a bug in ... in ... no, wait, it's not really a bug. It's a deficency
in the start up process. Basically, *dm should be run after everything
else, namely, after the getty's are spawned. This is not the case. *dm is
launched _almost_ after everything. But as you and several other people
have found out, "almost" doesn't do it.
Reply to: