mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Samuel Thibault <sthibault@debian.org>
To: Tom Vier <tom@triadsys.com>
Cc: 594089@bugs.debian.org, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org, dtor@mail.ru
Subject: Re: Bug#594089: keyboard-configuration: caps lock keycode problem
Date: Sun, 24 Oct 2010 16:41:51 +0200	[thread overview]
Message-ID: <20101024144150.GV24091@const.famille.thibault.fr> (raw)
In-Reply-To: <4C8E6861.1070502@triadsys.com>

The short story is: Tom's keyboard sends all that when he presses caps
lock:

press: 0x3a 0xe0 0x66
repeat: 0x3a
release: 0xba 0xe0 0xe6

0xe0 0x66 happens to be the "favorites" key on his keyboard with
internet navigation keys.  I thus believe there's a bug in his keyboard
that needs to be filtered at the kernel level.

The long story can be read on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594089

Tom Vier, le Mon 13 Sep 2010 14:07:29 -0400, a écrit :
> Here's xev from Stable. It looks like in Testing that some of the extra 
> key codes that show up in showkey are getting interpreted as additional 
> key presses in Testing's xorg but not Stable's.

Yes, as I said in a previous mail, squeeze Xorg now interprets the
internet scancodes by default, while it wouldn't in lenny and previous,
thus not showing the bug.

Samuel

       reply	other threads:[~2010-10-24 14:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100823154353.2805.13525.reportbug@tom.tse>
     [not found] ` <20100903235540.GA9149@const>
     [not found]   ` <4C866913.3030201@triadsys.com>
     [not found]     ` <4C8E6861.1070502@triadsys.com>
2010-10-24 14:41       ` Samuel Thibault [this message]
2010-10-25  4:50         ` Dmitry Torokhov
2010-10-25 13:37           ` Tom Vier
2010-10-25 18:03             ` Samuel Thibault
2010-10-25 18:25               ` Dmitry Torokhov
2010-10-26 14:50                 ` Tom Vier
2010-10-26 14:46               ` Tom Vier
2010-10-26 16:18                 ` Dmitry Torokhov
2010-10-26 21:04                   ` Tom Vier
2010-10-27  9:10                     ` Dmitry Torokhov
2010-10-27 12:05                       ` Samuel Thibault
     [not found]                         ` <99F91536-4413-430C-9932-7CEF6AB656DB@gmail.com>
2010-10-27 15:22                           ` Samuel Thibault
2010-10-27 16:08                             ` Dmitry Torokhov
2010-10-27 18:34                               ` Tom Vier
2010-10-27 19:25                                 ` Dmitry Torokhov
2010-10-27 20:20                                   ` H Hartley Sweeten
2010-10-27 20:25                                     ` Dmitry Torokhov
2010-10-29  8:55                       ` 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=20101024144150.GV24091@const.famille.thibault.fr \
    --to=sthibault@debian.org \
    --cc=594089@bugs.debian.org \
    --cc=dtor@mail.ru \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tom@triadsys.com \
    /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

all inboxes | Powered by JetHome®