[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200910122200.18064.dhazelton@enter.net>
Date: Mon, 12 Oct 2009 22:00:17 -0400
From: Daniel Hazelton <dhazelton@...er.net>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: Nix <nix@...eri.org.uk>,
"Justin P. Mattock" <justinmattock@...il.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Boyan <btanastasov@...oo.co.uk>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Ed Tomlinson <edt@....ca>,
" Frédéric L. W. Meunier"
<fredlwm@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
Subject: Re: [Bug #14388] keyboard under X with 2.6.31
On Monday 12 October 2009 07:38:41 pm Alan Cox wrote:
> > So it seems likely to me that this is a kernel bug, somewhere, and the
> > TTY layer seems like a good place to look (OK, a horrible place, but a
> > *likely* place).
>
> Somewhere around 2.6.29-30 various things went funny in the keyboard
> layer for me - notably characters "bleeding" across console switches.
Possibly not even related... I was seeing a similar problem in .26 or so and
it turned out to be caused, IIRC, by SCIM (in Gnome) and the KDE "Input
Methods" system. However my problem might not be related, because this even
stopped Alt-SysRq-K from working - and it only happened if I was holding down
a "modifier key" for a longer than average (say 30 seconds). I never reported
this because I soon after got tired of that distro (I was giving it a try at
the urging of friends) and replaced it.
The problem has not re-occurred since.
DRH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists