Bug 87906

Summary:	No keyboard input when console= set in lilo.conf to other than tty1
Product:	[Unmaintained] kdm	Reporter:	Roger Wilco <wilco>
Component:	general	Assignee:	kdm bugs tracker <kdm-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Slackware
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Roger Wilco 2004-08-24 08:44:12 UTC

Version:            (using KDE KDE 3.3.0)
Installed from:    Slackware Packages
OS:                Linux

I had the "console=tty6 CONSOLE=tty6" option in my lilo.conf, in effect redirecting all boot-up messages to tty6. After upgrading from 3.2.3 to 3.3.0, kdm would not accept any keystrokes (but on tty1 strange characters appear).

This happens no matter how kdm is started (manually from root command line or init 4 ie. graphic login)

The problem goes away if you remove the console= options from lilo.conf, but this is not a solution per se.

The system is a Slackware 10 with kernel 2.4.27 and XFree 4.4

Comment 1 Oswald Buddenhagen 2004-12-03 17:57:29 UTC

no matter what, i just can't reproduce it.
do you have new input on this issue?

Comment 2 Lari Lohikoski 2005-01-23 18:41:53 UTC

I'm having the same problem with kdm, though I'm using Grub instead of Lilo. My system is  Debian testing (kernel 2.6.8) and this problem appeared few days back when I upgraded my system. I'm not sure if also kdm got upgraded in this process. However there are no special settings in Grub, just the ordinary automatically created settings.

I've been unable to get kdm working back again, so I've been forced to move into using gdm.

The problem appears in the same way. When kdm starts, typing any key causes kdm to freeze for couple of seconds, even the clock in the login screen stops. No characters appear. Some strange characters appear in tty2 in my case. Switching to console using ctrl-alt-f1 doesn't work, the only way to continue from this situation is to choose "Login to console" and then restart kdm /etc/init/kdm restart. After starting kdm manually, it works correctly.

Comment 3 Oswald Buddenhagen 2005-01-24 08:19:39 UTC

On Sun, Jan 23, 2005 at 05:41:56PM -0000, Lari Lohikoski wrote:
> I'm having the same problem with kdm,
>
hmm, actually, this sounds pretty much like
http://bugs.kde.org/show_bug.cgi?id=91395 - please verify and report
back.

Comment 4 Lari Lohikoski 2005-01-24 17:48:29 UTC

> On Sun, Jan 23, 2005 at 05:41:56PM -0000, Lari Lohikoski wrote:
> > I'm having the same problem with kdm,
> hmm, actually, this sounds pretty much like
> http://bugs.kde.org/show_bug.cgi?id=91395 - please verify and report
> back.

Yes, it seems to be the same bug.

I just noticed that Debian's dpkg had created a new configuration file
"kdmrc.dpkg-new", which was bigger than the one it had
installed earlier. The earlier configuration didn't contain
ServerVTs-option, which this new one had. I replaced the my earlier
kdmrc (which had text "ConfigVersion=2.1") with the new
one("ConfigVersion=2.2"), and now kdm works again.

Maybe there has been a change in some of kdm's default values?

Comment 5 Oswald Buddenhagen 2005-01-24 23:45:36 UTC

On Mon, Jan 24, 2005 at 06:46:36PM +0200, Lari Lohikoski wrote:
> Maybe there has been a change in some of kdm's default values?
>
it's more than that.
the distros should run genkdmconf in their postinst scripts if the user
decides not to overwrite the old config completely.

Comment 6 Oswald Buddenhagen 2005-02-09 22:13:06 UTC


*** This bug has been marked as a duplicate of 91395 ***