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

Bug#295042: Keyboard problems under X



The following mail was sent to the wrong bug in error. Hope I get it
right this time ...

--- Weitergeleitete Nachricht / Forwarded Message ---
Date: Wed, 23 Feb 2005 19:32:04 +0100 (MET)
From: "Harald Geyer" <harald.geyer@gmx.at>
To: 295242@bugs.debian.org, braden@balthasar.tenament.com
Subject: 

Hi!

I ran into this while setting up a friends machine. Unfortunately there
is no internet there, so I couldn't look into the BTS there and now
I don't have the PC available. Sorry for the incomplete information!

Ad Braden: Can you confirm, whether the same problem shows up when
starting X with startx?

I believe that this bug is an instance of the problems described in
#169427, but here are the details:

I set up the machine with sarge-installer RC2, Kernel 2.4
The keyboard is ordinary pc105 on a PS2-Port.
The mouse is on USB.

After a few tries we got gpm running. (Sorry don't remember the
details, didn't expect any real trouble then.)

Issuing xstart as an ordinary user brougth up X without trouble.
I don't know, whether the keyboard worked at that time. My friend
pressed some key-combinations he doesn't remember. (They had some
effect at least.) At some point the keyboard went away. Neither
of Ctrl-Alt-Fn nor anything else showed any effect.

After terminating the running Gnome-Session using the mouse, we
got the ttys back, but the keyboard was in trouble there too:
To me it seems like the Ctrl-key was pressed the whole time
(d leading to eof (logout), s leading to Scroll_Lock - I don't
know a possibility to recover from that, ans Scroll_Lock itself
leading to "Show_State")

As we believed the keyboard configuration to be wrong, we tried a lot
of different things. But in all subsequent tries the keyboard was
broken under X from the very beginning (even after cold booting).
In some cases ttys worked well after the x server had terminated
and sometimes the above Ctrl-key problem showed up again. We can't
reproduce this reliably yet.

After reading #169427 I believe that the mouse setting is causing
that and IIRC we had the very same setting of "Configured Mouse"
and "Generic Mouse" as Braden has. I don't have access to the PC
ATM, so I can't investigate this further.

Hopefully this is useful to somebody. I'll send a follow up as
soon as I have access to the affected computer again.

Harald


-- 
Lassen Sie Ihren Gedanken freien Lauf... z.B. per FreeSMS
GMX bietet bis zu 100 FreeSMS/Monat: http://www.gmx.net/de/go/mail



Reply to: