From: Kieran <kieran@ihateaol.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: uk keyboard broken by input updates?
Date: Mon, 12 Jan 2004 10:21:04 +0000 [thread overview]
Message-ID: <40027510.1080600@ihateaol.co.uk> (raw)
In-Reply-To: <1073901824.29420.14.camel@bnocera.surrey.redhat.com>
I have exactly the same problem using 2.6.1 and an IBM USB keyboard, not
really had a chance to look into it yet though.
> Hello,
>
> 2.6.1 broke the ~/# key on my UK keyboard, when it used to work fine on
> 2.6.0. The key is now acting as Print Screen/SysRq. The keyboard is
> connected as PS/2 (though it is also plugged as USB, it's a Logitech
> wireless keyboard, with the receiver being the same for the mouse and
> keyboard).
>
> I didn't look at the changes made to the input layer in details. Could
> anyone shed some light on this problem?
>
> Cheers
next prev parent reply other threads:[~2004-01-12 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 10:03 uk keyboard broken by input updates? Bastien Nocera
2004-01-12 10:21 ` Kieran [this message]
2004-01-12 10:32 ` Vojtech Pavlik
2004-01-12 19:36 ` Kieran
2004-01-12 21:15 ` Bastien Nocera
2004-01-23 8:58 ` Bastien Nocera
2004-01-23 9:29 ` Andrew Morton
2004-01-23 9:37 ` Bastien Nocera
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=40027510.1080600@ihateaol.co.uk \
--to=kieran@ihateaol.co.uk \
--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