From: Mark Hounschell <markh@compro.net>
To: Chris Holvenstot <cholvenstot@comcast.net>
Cc: Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.24-git15 Keyboard Issue?
Date: Wed, 06 Feb 2008 08:23:16 -0500 [thread overview]
Message-ID: <47A9B4C4.7010809@compro.net> (raw)
In-Reply-To: <1202302978.9058.13.camel@popeye>
Chris Holvenstot wrote:
> I built 2.6.24-git15 this morning and seem to have picked up a little
> “funny” along the way – occasionally what should be a single key stroke
> ends up spraying multiple characters on to my screen.
>
>
> By this I mean I type “w” and get “wwwwwwwww” or whatever.
>
>
> This has happened a number of times with random keys so I don't think
> that it is a sticky key and I did not see this on previous builds.
>
>
> Has anyone else had this happen to them? While they were sober that
> is.
>
This or similar has been going on for over a year now. At least on SuSE distros.
See https://bugzilla.novell.com/show_bug.cgi?id=223561
Comment 22 in particular.
Regards
Mark
next prev parent reply other threads:[~2008-02-06 13:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 13:02 2.6.24-git15 Keyboard Issue? Chris Holvenstot
2008-02-06 13:23 ` Mark Hounschell [this message]
2008-02-06 13:28 ` Jiri Kosina
2008-02-06 13:49 ` Chris Holvenstot
2008-02-06 13:54 ` Jiri Kosina
2008-02-06 16:36 ` Kristoffer Ericson
2008-02-06 17:24 ` Chris Holvenstot
2008-02-07 9:18 ` Jiri Kosina
2008-02-07 9:51 ` Chris Holvenstot
2008-02-07 10:44 ` Chris Holvenstot
2008-02-07 10:51 ` Jiri Kosina
2008-02-07 12:29 ` Thomas Gleixner
2008-02-07 15:07 ` Chris Holvenstot
2008-02-07 16:13 ` Thomas Gleixner
2008-02-07 16:45 ` Chris Holvenstot
2008-02-07 17:46 ` Thomas Gleixner
2008-02-08 5:36 ` Chris Holvenstot
2008-02-09 9:56 ` Thomas Gleixner
2008-02-09 10:37 ` Chris Holvenstot
2008-02-09 13:59 ` Thomas Gleixner
2008-03-28 10:15 ` Thomas Gleixner
2008-03-28 11:20 ` Chris Holvenstot
2008-03-28 11:24 ` Jiri Kosina
2008-03-28 11:34 ` Chris Holvenstot
2008-02-08 15:08 ` Jiri Kosina
2008-02-08 23:25 ` Jiri Kosina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47A9B4C4.7010809@compro.net \
--to=markh@compro.net \
--cc=cholvenstot@comcast.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox