Bug#594089: keyboard-configuration: caps lock keycode problem
On Wed, 27 Oct 2010, Dmitry Torokhov wrote: First of all, the device appears to use duplicate usages for CapsLock/Favorites and RightShift/Previous so we better set up the duplicate usages quirk. I wonder how the other OS copes with diferent keys using the same usages. Jiri, any ideas? That thing I have been also wondering about when introducing the quirk for duplicate usages, but I haven't really found out. It's a bit odd. -- Jiri Kosina SUSE Labs, Novell Inc. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.lnx.2.00.1010291054410.6...@pobox.suse.cz
Bug#594089: keyboard-configuration: caps lock keycode problem
On Tue, Oct 26, 2010 at 05:04:44PM -0400, Tom Vier wrote:
On 10/26/2010 12:18 PM, Dmitry Torokhov wrote:
Hmm, it looks like it uses the same usages (MSC_SCAN) for
CapsLock/Favorites and RightShift/Previous... What does lsusb say about
the keyboard (VID/PID)?
The scroll wheel on the keyboard is a separate device:
Bus 005 Device 003: ID 046d:c30a Logitech, Inc. iTouch Composite
Bus 005 Device 002: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Thanks Tom. This device is handled by drivers/hid/hid-lg.c sub-driver
and there seem to be a few issues there, still I do not see how they can
produce the results you are seeing.
First of all, the device appears to use duplicate usages for
CapsLock/Favorites and RightShift/Previous so we better set up the
duplicate usages quirk. I wonder how the other OS copes with diferent
keys using the same usages. Jiri, any ideas?
Also, based on evtest data I only see presses/releases for one key (Caps
Lock, Right Shift, etc.) I do not see the presses for the additional
keys in the evtest stream so I am baffled as to where the additional
scancode is coming from... Do you have some funky keymap loaded?
Anything interesting in dumpkeys?
--
Dmitry
Input: hid-lgff - mark Logitech Elite as having duplicate reports
From: Dmitry Torokhov dmitry.torok...@gmail.com
Also make sure we clear bits when mapping keys to ensure that
hid-input will not try to add more keycodes.
Signed-off-by: Dmitry Torokhov d...@mail.ru
---
drivers/hid/hid-lg.c | 59 ++
1 files changed, 40 insertions(+), 19 deletions(-)
diff --git a/drivers/hid/hid-lg.c b/drivers/hid/hid-lg.c
index b629fba..2979b68 100644
--- a/drivers/hid/hid-lg.c
+++ b/drivers/hid/hid-lg.c
@@ -78,8 +78,8 @@ static __u8 *lg_report_fixup(struct hid_device *hdev, __u8
*rdesc,
return rdesc;
}
-#define lg_map_key_clear(c)hid_map_usage_clear(hi, usage, bit, max, \
- EV_KEY, (c))
+#define lg_map_key_clear(c) \
+ hid_map_usage_clear(hi, usage, bit, max, EV_KEY, (c))
static int lg_ultrax_remote_mapping(struct hid_input *hi,
struct hid_usage *usage, unsigned long **bit, int *max)
@@ -88,6 +88,7 @@ static int lg_ultrax_remote_mapping(struct hid_input *hi,
return 0;
set_bit(EV_REP, hi-input-evbit);
+
switch (usage-hid HID_USAGE) {
/* Reported on Logitech Ultra X Media Remote */
case 0x004: lg_map_key_clear(KEY_AGAIN);break;
@@ -168,8 +169,10 @@ static int lg_wireless_mapping(struct hid_input *hi,
struct hid_usage *usage,
case 0x102a: lg_map_key_clear(KEY_BACK);break;
case 0x102b: lg_map_key_clear(KEY_CYCLEWINDOWS);break;
case 0x102d: lg_map_key_clear(KEY_WWW); break;
- /* The following two are 'Start/answer call' and 'End/reject call'
- on the MX3200 */
+ /*
+* The following two are 'Start/answer call' and 'End/reject call'
+* on the MX3200
+*/
case 0x1031: lg_map_key_clear(KEY_OK); break;
case 0x1032: lg_map_key_clear(KEY_CANCEL); break;
case 0x1041: lg_map_key_clear(KEY_BATTERY); break;
@@ -195,17 +198,35 @@ static int lg_input_mapping(struct hid_device *hdev,
struct hid_input *hi,
struct hid_field *field, struct hid_usage *usage,
unsigned long **bit, int *max)
{
- /* extended mapping for certain Logitech hardware (Logitech cordless
- desktop LX500) */
+ /*
+* Extended mapping for certain Logitech hardware (such as
+* Logitech cordless desktop LX500)
+*/
static const u8 e_keymap[] = {
- 0,216, 0,213,175,156, 0, 0, 0, 0,
- 144, 0, 0, 0, 0, 0, 0, 0, 0,212,
- 174,167,152,161,112, 0, 0, 0,154, 0,
- 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
- 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
- 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
- 0, 0, 0, 0, 0,183,184,185,186,187,
- 188,189,190,191,192,193,194, 0, 0, 0
+ [ 1] = KEY_CHAT,
+ [ 3] = KEY_SOUND,
+ [ 4] = KEY_MOVE,
+ [ 5] = KEY_BOOKMARKS,
+ [10] = KEY_FILE,
+ [19] = KEY_CAMERA,
+ [20] = KEY_EXIT,
+ [21] = KEY_RECORD,
+ [22] = KEY_SCREENLOCK,
+ [23] = KEY_EJECTCD,
+ [24] = KEY_MACRO,
+ [28] = KEY_CYCLEWINDOWS,
+ [65] = KEY_F13,
+ [66] = KEY_F14,
+ [67] = KEY_F15,
+ [68] = KEY_F16,
+ [69] = KEY_F17,
+ [70] = KEY_F18,
+ [71] = KEY_F19,
+ [72] = KEY_F20,
+ [73] = KEY_F21,
+ [74] = KEY_F22,
+ [75] = KEY_F23,
+
Bug#594089: keyboard-configuration: caps lock keycode problem
Dmitry Torokhov, le Wed 27 Oct 2010 02:10:29 -0700, a écrit : Also, based on evtest data I only see presses/releases for one key (Caps Lock, Right Shift, etc.) I do not see the presses for the additional keys in the evtest stream so I am baffled as to where the additional scancode is coming from... Do you have some funky keymap loaded? Anything interesting in dumpkeys? Err, since the duplicates appear in scancodes already, is the content of dumpkeys really involved? Samuel -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101027120513.gt4...@const.famille.thibault.fr
Bug#594089: keyboard-configuration: caps lock keycode problem
On 10/27/2010 12:08 PM, Dmitry Torokhov wrote: On Wed, Oct 27, 2010 at 05:22:42PM +0200, Samuel Thibault wrote: Dmitry Torokhov, le Wed 27 Oct 2010 08:06:26 -0700, a écrit : Sure, but dumpkeys shows the table from scancodes to keycodes, not from input events to scancodes. I am just wondering if some of the translation is leaking even though the keyboard is in raw mode... OK, scratch that... Are there any other input devices? Anything connected via uinput and listening? What does /proc/bus/input/devices show? Maybe if Tom could compile and load evbug module it would show us where the additional events are coming form, becaus ethey surely are not generated by the keyboard itself (otherwise we'd have seen them in evtest output for that device). Minor correction to what I wrote earlier about the scroll wheel. That is actually my mouse. It says Dell but it's really made by Logitech. I just tried the console and what's funny is Favorites actually works as Capslock and Previous works as right-shift. X has the opposite problem. In case anyone missed it, Debian Stable works fine with this keyboard. The keyboard on the working Stable machine is exactly the same (same usb id's). I'm not familiar with the input stack, but in case it is a kernel problem, the difference is: Stable dist, working: Linux zero 2.6.26-2-amd64 #1 SMP Thu Sep 16 15:56:38 UTC 2010 x86_64 GNU/Linux Testing dist, not working: Linux tom 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux /proc/bus/input/devices on the problem machine: I: Bus=0017 Vendor=0001 Product=0001 Version=0100 N: Name=Macintosh mouse button emulation P: Phys= S: Sysfs=/devices/virtual/input/input0 U: Uniq= H: Handlers=mouse0 event0 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 I: Bus=0003 Vendor=046d Product=c016 Version=0110 N: Name=Logitech Optical USB Mouse P: Phys=usb-:00:13.0-1/input0 S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-1/5-1:1.0/input/input1 U: Uniq= H: Handlers=mouse1 event1 B: EV=17 B: KEY=7 0 0 0 0 B: REL=103 B: MSC=10 I: Bus=0019 Vendor= Product=0001 Version= N: Name=Power Button P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4 U: Uniq= H: Handlers=kbd event4 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name=Power Button P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5 U: Uniq= H: Handlers=kbd event5 B: EV=3 B: KEY=10 0 I: Bus=0010 Vendor=001f Product=0001 Version=0100 N: Name=PC Speaker P: Phys=isa0061/input0 S: Sysfs=/devices/platform/pcspkr/input/input6 U: Uniq= H: Handlers=kbd event6 B: EV=40001 B: SND=6 I: Bus=0003 Vendor=046d Product=c30a Version=0110 N: Name=Logitech Logitech USB Keyboard P: Phys=usb-:00:13.0-2/input0 S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.0/input/input9 U: Uniq= H: Handlers=kbd event2 B: EV=120013 B: KEY=10007 ff8007ff febeffdfffef fffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=046d Product=c30a Version=0110 N: Name=Logitech Logitech USB Keyboard P: Phys=usb-:00:13.0-2/input1 S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.1/input/input10 U: Uniq= H: Handlers=kbd mouse2 event3 B: EV=17 B: KEY=f f840334 60d8fafd01d008 1f 0 B: REL=103 B: MSC=10 -- Tom Vier t...@triadsys.com Senior Net/Sys Admin Triad Systems Engineering, Inc. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cc870bb.2050...@triadsys.com
Bug#594089: keyboard-configuration: caps lock keycode problem
On Wed, Oct 27, 2010 at 02:34:35PM -0400, Tom Vier wrote: On 10/27/2010 12:08 PM, Dmitry Torokhov wrote: On Wed, Oct 27, 2010 at 05:22:42PM +0200, Samuel Thibault wrote: Dmitry Torokhov, le Wed 27 Oct 2010 08:06:26 -0700, a écrit : Sure, but dumpkeys shows the table from scancodes to keycodes, not from input events to scancodes. I am just wondering if some of the translation is leaking even though the keyboard is in raw mode... OK, scratch that... Are there any other input devices? Anything connected via uinput and listening? What does /proc/bus/input/devices show? Maybe if Tom could compile and load evbug module it would show us where the additional events are coming form, becaus ethey surely are not generated by the keyboard itself (otherwise we'd have seen them in evtest output for that device). Minor correction to what I wrote earlier about the scroll wheel. That is actually my mouse. It says Dell but it's really made by Logitech. I just tried the console and what's funny is Favorites actually works as Capslock and Previous works as right-shift. X has the opposite problem. In case anyone missed it, Debian Stable works fine with this keyboard. The keyboard on the working Stable machine is exactly the same (same usb id's). I'm not familiar with the input stack, but in case it is a kernel problem, the difference is: Stable dist, working: Linux zero 2.6.26-2-amd64 #1 SMP Thu Sep 16 15:56:38 UTC 2010 x86_64 GNU/Linux Testing dist, not working: Linux tom 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux /proc/bus/input/devices on the problem machine: ... I: Bus=0003 Vendor=046d Product=c30a Version=0110 N: Name=Logitech Logitech USB Keyboard P: Phys=usb-:00:13.0-2/input0 S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.0/input/input9 U: Uniq= H: Handlers=kbd event2 B: EV=120013 B: KEY=10007 ff8007ff febeffdfffef fffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=046d Product=c30a Version=0110 N: Name=Logitech Logitech USB Keyboard P: Phys=usb-:00:13.0-2/input1 S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.1/input/input10 U: Uniq= H: Handlers=kbd mouse2 event3 B: EV=17 B: KEY=f f840334 60d8fafd01d008 1f 0 B: REL=103 B: MSC=10 Hmm, this keyboard registers 2 input devices... I wonder, if you press CapsLock/Favories and RightShift/Previous and monitor both event devices with evtest - will it report events on both devices at once? -- Dmitry -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101027192508.ga29...@core.coreip.homeip.net
Bug#594089: keyboard-configuration: caps lock keycode problem
On Wednesday, October 27, 2010 01:20:09 pm H Hartley Sweeten wrote: Wednesday, October 27, 2010 12:25 PM, Dmitry Torokhov wrote: I: Bus=0003 Vendor=046d Product=c30a Version=0110 N: Name=Logitech Logitech USB Keyboard P: Phys=usb-:00:13.0-2/input0 S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.0/input/input9 U: Uniq= H: Handlers=kbd event2 B: EV=120013 B: KEY=10007 ff8007ff febeffdfffef fffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=046d Product=c30a Version=0110 N: Name=Logitech Logitech USB Keyboard P: Phys=usb-:00:13.0-2/input1 S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.1/input/input10 U: Uniq= H: Handlers=kbd mouse2 event3 B: EV=17 B: KEY=f f840334 60d8fafd01d008 1f 0 B: REL=103 B: MSC=10 Hmm, this keyboard registers 2 input devices... I wonder, if you press CapsLock/Favories and RightShift/Previous and monitor both event devices with evtest - will it report events on both devices at once? I haven't really been following this thread but I think the two input devices is normal if the keyboard has multi-media keys. All the extra keys show up as a separate input device. You might get the CapsLock and RightShift events on one device and the Favorites and Previous events on the other. It is normal on sane devices however in this case there are ghost key presses coming from an unknown source. -- Dmitry -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201010271325.37935.dmitry.torok...@gmail.com
Bug#594089: keyboard-configuration: caps lock keycode problem
Wednesday, October 27, 2010 12:25 PM, Dmitry Torokhov wrote: I: Bus=0003 Vendor=046d Product=c30a Version=0110 N: Name=Logitech Logitech USB Keyboard P: Phys=usb-:00:13.0-2/input0 S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.0/input/input9 U: Uniq= H: Handlers=kbd event2 B: EV=120013 B: KEY=10007 ff8007ff febeffdfffef fffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=046d Product=c30a Version=0110 N: Name=Logitech Logitech USB Keyboard P: Phys=usb-:00:13.0-2/input1 S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.1/input/input10 U: Uniq= H: Handlers=kbd mouse2 event3 B: EV=17 B: KEY=f f840334 60d8fafd01d008 1f 0 B: REL=103 B: MSC=10 Hmm, this keyboard registers 2 input devices... I wonder, if you press CapsLock/Favories and RightShift/Previous and monitor both event devices with evtest - will it report events on both devices at once? I haven't really been following this thread but I think the two input devices is normal if the keyboard has multi-media keys. All the extra keys show up as a separate input device. You might get the CapsLock and RightShift events on one device and the Favorites and Previous events on the other. Hartley -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/0d753d10438da54287a00b027084269764819c6...@ausp01vmbx24.collaborationhost.net
Bug#594089: keyboard-configuration: caps lock keycode problem
On 10/25/2010 02:03 PM, Samuel Thibault wrote: Tom Vier, le Mon 25 Oct 2010 09:37:26 -0400, a écrit : On 10/25/2010 12:50 AM, Dmitry Torokhov wrote: On Sun, Oct 24, 2010 at 04:41:51PM +0200, Samuel Thibault wrote: 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 Hmm, the question is whether the real favorites key send the same usage and the fake one after caps lock. Any chance Tom could locate evtest utility and see what MSC_SCAN events being emitted? Sure. Here's caps-lock: Event: time 1288013671.633008, -- Report Sync Event: time 1288013674.171812, type 4 (Misc), code 4 (ScanCode), value 70039 Event: time 1288013674.171853, type 1 (Key), code 58 (CapsLock), value 1 Event: time 1288013674.171862, -- Report Sync Event: time 1288013674.172210, type 17 (LED), code 1 (CapsLock), value 1 Event: time 1288013674.299553, type 4 (Misc), code 4 (ScanCode), value 70039 Event: time 1288013674.299580, type 1 (Key), code 58 (CapsLock), value 0 Event: time 1288013674.299593, -- Report Sync Right-shift (the other problem key): Event: time 1288013798.388025, -- Report Sync Event: time 1288013800.742088, type 4 (Misc), code 4 (ScanCode), value 700e5 Event: time 1288013800.742130, type 1 (Key), code 54 (RightShift), value 1 Event: time 1288013800.742142, -- Report Sync Event: time 1288013800.861777, type 4 (Misc), code 4 (ScanCode), value 700e5 Event: time 1288013800.861812, type 1 (Key), code 54 (RightShift), value 0 Event: time 1288013800.861824, -- Report Sync Could you also post results when pressing the favorite and the prev internet keys of your keyboard? Samuel It's returning the same codes. Maybe what's going on here is that they never worked back in Stable and someone tried to fix those keys, not realizing they're the same codes as capslock and right-shift. I'll have to test it on my Stable machine tonight to see if those keys work or not, tho. Favorites: Event: time 1288041423.048839, -- Report Sync Event: time 1288041425.068704, type 4 (Misc), code 4 (ScanCode), value 70039 Event: time 1288041425.068742, type 1 (Key), code 58 (CapsLock), value 1 Event: time 1288041425.068754, -- Report Sync Event: time 1288041425.069105, type 17 (LED), code 1 (CapsLock), value 1 Event: time 1288041425.260313, type 4 (Misc), code 4 (ScanCode), value 70039 Event: time 1288041425.260343, type 1 (Key), code 58 (CapsLock), value 0 Event: time 1288041425.260347, -- Report Sync Previous: Event: time 1288041443.531447, -- Report Sync Event: time 1288041445.318877, type 4 (Misc), code 4 (ScanCode), value 700e5 Event: time 1288041445.318915, type 1 (Key), code 54 (RightShift), value 1 Event: time 1288041445.318932, -- Report Sync Event: time 1288041445.438567, type 4 (Misc), code 4 (ScanCode), value 700e5 Event: time 1288041445.438606, type 1 (Key), code 54 (RightShift), value 0 Event: time 1288041445.438629, -- Report Sync -- Tom Vier t...@triadsys.com Senior Net/Sys Admin Triad Systems Engineering, Inc. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cc6e9d8.8010...@triadsys.com
Bug#594089: keyboard-configuration: caps lock keycode problem
On 10/25/2010 02:25 PM, Dmitry Torokhov wrote: On Mon, Oct 25, 2010 at 08:03:20PM +0200, Samuel Thibault wrote: Could you also post results when pressing the favorite and the prev internet keys of your keyboard? Actually, if these are all the events that evtest reports when pressing CapsLock then I am confused where the favorites ghost press is coming from... They are not emitted by the device. Do you have a funky keymap loaded somewhere? Also, was 'showkey -s' issued while in X or in the text console? Console. I just ran it now and caps-lock has the same codes as favorites and right-shift has the same as previous. So it's not an X problem. -- Tom Vier t...@triadsys.com Senior Net/Sys Admin Triad Systems Engineering, Inc. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cc6eab5.9020...@triadsys.com
Bug#594089: keyboard-configuration: caps lock keycode problem
On Tue, Oct 26, 2010 at 10:46:48AM -0400, Tom Vier wrote: On 10/25/2010 02:03 PM, Samuel Thibault wrote: Tom Vier, le Mon 25 Oct 2010 09:37:26 -0400, a écrit : On 10/25/2010 12:50 AM, Dmitry Torokhov wrote: On Sun, Oct 24, 2010 at 04:41:51PM +0200, Samuel Thibault wrote: 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 Hmm, the question is whether the real favorites key send the same usage and the fake one after caps lock. Any chance Tom could locate evtest utility and see what MSC_SCAN events being emitted? Sure. Here's caps-lock: Event: time 1288013671.633008, -- Report Sync Event: time 1288013674.171812, type 4 (Misc), code 4 (ScanCode), value 70039 Event: time 1288013674.171853, type 1 (Key), code 58 (CapsLock), value 1 Event: time 1288013674.171862, -- Report Sync Event: time 1288013674.172210, type 17 (LED), code 1 (CapsLock), value 1 Event: time 1288013674.299553, type 4 (Misc), code 4 (ScanCode), value 70039 Event: time 1288013674.299580, type 1 (Key), code 58 (CapsLock), value 0 Event: time 1288013674.299593, -- Report Sync Right-shift (the other problem key): Event: time 1288013798.388025, -- Report Sync Event: time 1288013800.742088, type 4 (Misc), code 4 (ScanCode), value 700e5 Event: time 1288013800.742130, type 1 (Key), code 54 (RightShift), value 1 Event: time 1288013800.742142, -- Report Sync Event: time 1288013800.861777, type 4 (Misc), code 4 (ScanCode), value 700e5 Event: time 1288013800.861812, type 1 (Key), code 54 (RightShift), value 0 Event: time 1288013800.861824, -- Report Sync Could you also post results when pressing the favorite and the prev internet keys of your keyboard? Samuel It's returning the same codes. Maybe what's going on here is that they never worked back in Stable and someone tried to fix those keys, not realizing they're the same codes as capslock and right-shift. I'll have to test it on my Stable machine tonight to see if those keys work or not, tho. Favorites: Event: time 1288041423.048839, -- Report Sync Event: time 1288041425.068704, type 4 (Misc), code 4 (ScanCode), value 70039 Event: time 1288041425.068742, type 1 (Key), code 58 (CapsLock), value 1 Event: time 1288041425.068754, -- Report Sync Event: time 1288041425.069105, type 17 (LED), code 1 (CapsLock), value 1 Event: time 1288041425.260313, type 4 (Misc), code 4 (ScanCode), value 70039 Event: time 1288041425.260343, type 1 (Key), code 58 (CapsLock), value 0 Event: time 1288041425.260347, -- Report Sync Previous: Event: time 1288041443.531447, -- Report Sync Event: time 1288041445.318877, type 4 (Misc), code 4 (ScanCode), value 700e5 Event: time 1288041445.318915, type 1 (Key), code 54 (RightShift), value 1 Event: time 1288041445.318932, -- Report Sync Event: time 1288041445.438567, type 4 (Misc), code 4 (ScanCode), value 700e5 Event: time 1288041445.438606, type 1 (Key), code 54 (RightShift), value 0 Event: time 1288041445.438629, -- Report Sync Hmm, it looks like it uses the same usages (MSC_SCAN) for CapsLock/Favorites and RightShift/Previous... What does lsusb say about the keyboard (VID/PID)? -- Dmitry -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101026161820.ge13...@core.coreip.homeip.net
Bug#594089: keyboard-configuration: caps lock keycode problem
On 10/26/2010 12:18 PM, Dmitry Torokhov wrote: Hmm, it looks like it uses the same usages (MSC_SCAN) for CapsLock/Favorites and RightShift/Previous... What does lsusb say about the keyboard (VID/PID)? The scroll wheel on the keyboard is a separate device: Bus 005 Device 003: ID 046d:c30a Logitech, Inc. iTouch Composite Bus 005 Device 002: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse -v: Bus 005 Device 005: ID 046d:c30a Logitech, Inc. iTouch Composite Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046d Logitech, Inc. idProduct 0xc30a iTouch Composite bcdDevice 15.00 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 59 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 64 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 156 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 32 Bus 005 Device 002: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046d Logitech, Inc. idProduct 0xc016 Optical Wheel Mouse bcdDevice3.40 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 52 Report
Bug#594089: keyboard-configuration: caps lock keycode problem
On 10/25/2010 12:50 AM, Dmitry Torokhov wrote: On Sun, Oct 24, 2010 at 04:41:51PM +0200, Samuel Thibault wrote: 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 Hmm, the question is whether the real favorites key send the same usage and the fake one after caps lock. Any chance Tom could locate evtest utility and see what MSC_SCAN events being emitted? Thanks. Sure. Here's caps-lock: Event: time 1288013671.633008, -- Report Sync Event: time 1288013674.171812, type 4 (Misc), code 4 (ScanCode), value 70039 Event: time 1288013674.171853, type 1 (Key), code 58 (CapsLock), value 1 Event: time 1288013674.171862, -- Report Sync Event: time 1288013674.172210, type 17 (LED), code 1 (CapsLock), value 1 Event: time 1288013674.299553, type 4 (Misc), code 4 (ScanCode), value 70039 Event: time 1288013674.299580, type 1 (Key), code 58 (CapsLock), value 0 Event: time 1288013674.299593, -- Report Sync Right-shift (the other problem key): Event: time 1288013798.388025, -- Report Sync Event: time 1288013800.742088, type 4 (Misc), code 4 (ScanCode), value 700e5 Event: time 1288013800.742130, type 1 (Key), code 54 (RightShift), value 1 Event: time 1288013800.742142, -- Report Sync Event: time 1288013800.861777, type 4 (Misc), code 4 (ScanCode), value 700e5 Event: time 1288013800.861812, type 1 (Key), code 54 (RightShift), value 0 Event: time 1288013800.861824, -- Report Sync -- Tom Vier t...@triadsys.com Senior Net/Sys Admin Triad Systems Engineering, Inc. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cc58816.3090...@triadsys.com
Bug#594089: keyboard-configuration: caps lock keycode problem
Tom Vier, le Mon 25 Oct 2010 09:37:26 -0400, a écrit : On 10/25/2010 12:50 AM, Dmitry Torokhov wrote: On Sun, Oct 24, 2010 at 04:41:51PM +0200, Samuel Thibault wrote: 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 Hmm, the question is whether the real favorites key send the same usage and the fake one after caps lock. Any chance Tom could locate evtest utility and see what MSC_SCAN events being emitted? Sure. Here's caps-lock: Event: time 1288013671.633008, -- Report Sync Event: time 1288013674.171812, type 4 (Misc), code 4 (ScanCode), value 70039 Event: time 1288013674.171853, type 1 (Key), code 58 (CapsLock), value 1 Event: time 1288013674.171862, -- Report Sync Event: time 1288013674.172210, type 17 (LED), code 1 (CapsLock), value 1 Event: time 1288013674.299553, type 4 (Misc), code 4 (ScanCode), value 70039 Event: time 1288013674.299580, type 1 (Key), code 58 (CapsLock), value 0 Event: time 1288013674.299593, -- Report Sync Right-shift (the other problem key): Event: time 1288013798.388025, -- Report Sync Event: time 1288013800.742088, type 4 (Misc), code 4 (ScanCode), value 700e5 Event: time 1288013800.742130, type 1 (Key), code 54 (RightShift), value 1 Event: time 1288013800.742142, -- Report Sync Event: time 1288013800.861777, type 4 (Misc), code 4 (ScanCode), value 700e5 Event: time 1288013800.861812, type 1 (Key), code 54 (RightShift), value 0 Event: time 1288013800.861824, -- Report Sync Could you also post results when pressing the favorite and the prev internet keys of your keyboard? Samuel -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101025180320.ga4...@const.famille.thibault.fr
Bug#594089: keyboard-configuration: caps lock keycode problem
On Mon, Oct 25, 2010 at 08:03:20PM +0200, Samuel Thibault wrote: Tom Vier, le Mon 25 Oct 2010 09:37:26 -0400, a écrit : On 10/25/2010 12:50 AM, Dmitry Torokhov wrote: On Sun, Oct 24, 2010 at 04:41:51PM +0200, Samuel Thibault wrote: 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 Hmm, the question is whether the real favorites key send the same usage and the fake one after caps lock. Any chance Tom could locate evtest utility and see what MSC_SCAN events being emitted? Sure. Here's caps-lock: Event: time 1288013671.633008, -- Report Sync Event: time 1288013674.171812, type 4 (Misc), code 4 (ScanCode), value 70039 Event: time 1288013674.171853, type 1 (Key), code 58 (CapsLock), value 1 Event: time 1288013674.171862, -- Report Sync Event: time 1288013674.172210, type 17 (LED), code 1 (CapsLock), value 1 Event: time 1288013674.299553, type 4 (Misc), code 4 (ScanCode), value 70039 Event: time 1288013674.299580, type 1 (Key), code 58 (CapsLock), value 0 Event: time 1288013674.299593, -- Report Sync Right-shift (the other problem key): Event: time 1288013798.388025, -- Report Sync Event: time 1288013800.742088, type 4 (Misc), code 4 (ScanCode), value 700e5 Event: time 1288013800.742130, type 1 (Key), code 54 (RightShift), value 1 Event: time 1288013800.742142, -- Report Sync Event: time 1288013800.861777, type 4 (Misc), code 4 (ScanCode), value 700e5 Event: time 1288013800.861812, type 1 (Key), code 54 (RightShift), value 0 Event: time 1288013800.861824, -- Report Sync Could you also post results when pressing the favorite and the prev internet keys of your keyboard? Actually, if these are all the events that evtest reports when pressing CapsLock then I am confused where the favorites ghost press is coming from... They are not emitted by the device. Do you have a funky keymap loaded somewhere? Also, was 'showkey -s' issued while in X or in the text console? -- Dmitry -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101025182509.ga13...@core.coreip.homeip.net
Bug#594089: keyboard-configuration: caps lock keycode problem
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 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101024144150.gv24...@const.famille.thibault.fr
Bug#594089: keyboard-configuration: caps lock keycode problem
On Sun, Oct 24, 2010 at 04:41:51PM +0200, Samuel Thibault wrote: 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 Hmm, the question is whether the real favorites key send the same usage and the fake one after caps lock. Any chance Tom could locate evtest utility and see what MSC_SCAN events being emitted? Thanks. -- Dmitry -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101025045003.ga1...@core.coreip.homeip.net
Bug#594089: keyboard-configuration: caps lock keycode problem
-- Tom Vier t...@triadsys.com Senior Net/Sys Admin Triad Systems Engineering, Inc. 703-956-1535 office 703-984-9093 cell 703-404-0308 helpdesk On 09/07/2010 12:32 PM, Tom Vier wrote: On 09/03/2010 07:55 PM, Samuel Thibault wrote: Tom, le Mon 23 Aug 2010 11:43:53 -0400, a écrit : The model name is logimel, which is set in both /etc/default/keyboard and /etc/X11/xorg.conf. Which explains why Xorg has the behavior you describe: the logimel model includes the logitech base, which includes the common navigation keys, which makes XF86Back from 0xe0 0x6a, and XF86Favorites from 0xe0 0x66. Do you actually have navigation keys on your keyboard? I'm afraid we'll just have to blacklist it in the usb driver according to the usb ID. Samuel I have bunch of extra keys. 8) It's one of those internet keyboards with keys for: email sms webcam itouch search shipping home favorites, plus volume, track skip, play/pause, record. 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. caps lock, then right shift KeyPress event, serial 33, synthetic NO, window 0x2a1, root 0x1ae, subw 0x0, time 9213660, (161,-9), root:(337,884), state 0x12, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False PropertyNotify event, serial 33, synthetic NO, window 0x2a1, atom 0x11c (XKLAVIER_STATE), time 9213663, state PropertyNewValue KeyRelease event, serial 33, synthetic NO, window 0x2a1, root 0x1ae, subw 0x0, time 9213780, (161,-9), root:(337,884), state 0x12, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 33, synthetic NO, window 0x2a1, root 0x1ae, subw 0x0, time 9217955, (161,-9), root:(337,884), state 0x10, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False PropertyNotify event, serial 33, synthetic NO, window 0x2a1, atom 0x11c (XKLAVIER_STATE), time 9217958, state PropertyNewValue KeyRelease event, serial 33, synthetic NO, window 0x2a1, root 0x1ae, subw 0x0, time 9218091, (161,-9), root:(337,884), state 0x12, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 33, synthetic NO, window 0x2a1, root 0x1ae, subw 0x0, time 9220699, (161,-9), root:(337,884), state 0x12, keycode 36 (keysym 0xff0d, Return), same_screen YES, XLookupString gives 1 bytes: (0d) XmbLookupString gives 1 bytes: (0d) XFilterEvent returns: False KeyRelease event, serial 33, synthetic NO, window 0x2a1, root 0x1ae, subw 0x0, time 9220835, (161,-9), root:(337,884), state 0x12, keycode 36 (keysym 0xff0d, Return), same_screen YES, XLookupString gives 1 bytes: (0d) XFilterEvent returns: False -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c8e6861.1070...@triadsys.com
Bug#594089: keyboard-configuration: caps lock keycode problem
On 09/03/2010 07:45 PM, Samuel Thibault wrote: Tom Vier, le Fri 03 Sep 2010 16:35:47 -0400, a écrit : On 09/02/2010 03:46 PM, Samuel Thibault wrote: Hello, Tom Vier, le Thu 02 Sep 2010 15:11:49 -0400, a écrit : It says UNICODE mode and the codes for caps lock are: press: 0x3a 0xe0 0x66 repeat: 0x3a release: 0xba 0xe0 0x 0xe6 I guess? Yes. I also just discovered the right shift key goes back a page in iceweasel. Here are the right-shift codes: showkey -s: press: 0x36 0xe0 0x6a repeat: 0x36 release: 0xb6 0xe0 0xea All this looks like one of the few keyboard glitches that linux-2.6 fixes for some keyboards known to be bogus, while other keyboards do use these scancodes to report e.g. multimedia keys. Could you try showkey -s with the older, working kernel? Stable (2.6.26) which worked fine gives the same as Testing (2.6.32): When you say Stable, you mean both kernel and Xorg? Could you also run xev on your stable box? I mean the debian stable release. I'll try it on my home machine, which has the same logitech keyboard. press: 0x3a 0xe0 0x66 repeat: 0x3a release: 0xba 0xe0 0xe6 ...which makes me think it's an xorg problem, but I'm not familiar with how the whole keyboard stack works. It's a big mess :) I wonder why the logitech generates so many codes. It looks to me like a keyboard bug. Do you see any pattern, e.g. does the left shift key produce one too? Do the keys which do produce extra scancodes form any particular shape on the keyboard? The only problem keys are caps-lock and right-shift, both upon key press. Such bug should probably be fixed in the kernel, just like it is already in atkbd.c for some keyboards. Samuel Showkey looks almost identical between kernels tho. I'll check my machine at home and see what xev shows. -- Tom Vier t...@triadsys.com Senior Net/Sys Admin Triad Systems Engineering, Inc. 703-956-1535 office 703-984-9093 cell 703-404-0308 helpdesk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c866828.7040...@triadsys.com
Bug#594089: keyboard-configuration: caps lock keycode problem
On 09/03/2010 07:55 PM, Samuel Thibault wrote: Tom, le Mon 23 Aug 2010 11:43:53 -0400, a écrit : The model name is logimel, which is set in both /etc/default/keyboard and /etc/X11/xorg.conf. Which explains why Xorg has the behavior you describe: the logimel model includes the logitech base, which includes the common navigation keys, which makes XF86Back from 0xe0 0x6a, and XF86Favorites from 0xe0 0x66. Do you actually have navigation keys on your keyboard? I'm afraid we'll just have to blacklist it in the usb driver according to the usb ID. Samuel I have bunch of extra keys. 8) It's one of those internet keyboards with keys for: email sms webcam itouch search shipping home favorites, plus volume, track skip, play/pause, record. -- Tom Vier t...@triadsys.com Senior Net/Sys Admin Triad Systems Engineering, Inc. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c866913.3030...@triadsys.com
Bug#594089: keyboard-configuration: caps lock keycode problem
Tom Vier, le Tue 07 Sep 2010 12:32:19 -0400, a écrit : I have bunch of extra keys. 8) It's one of those internet keyboards with keys for: email sms webcam itouch search shipping home favorites, plus volume, track skip, play/pause, record. So there indeed is a favorites key, that makes it hard to blacklist its events. I guess it works on testing but not on stable? Would you be able to test the keyboard on windows? I'm starting to wonder whether your keyboard might just have become dirty and you didn't realize it because on stable favorites and back don't work by default anyway. Samuel -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100907200144.gc4...@const.famille.thibault.fr
Bug#594089: keyboard-configuration: caps lock keycode problem
Tom Vier, le Tue 07 Sep 2010 12:28:24 -0400, a écrit : Such bug should probably be fixed in the kernel, just like it is already in atkbd.c for some keyboards. Samuel Showkey looks almost identical between kernels tho. Yes, but the bug is actually in the keyboard, not in the kernel or in Xorg: they're just obeying the keyboard. The best place to fix it is thus the component that drives it. The difference between stable and testing is that testing now uses evdev by default, which doesn't need setkeycodes invocations to get multimedia keys working. Samuel -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100907202639.gt4...@const.famille.thibault.fr
Bug#594089: keyboard-configuration: caps lock keycode problem
On 09/02/2010 03:46 PM, Samuel Thibault wrote: Hello, Tom Vier, le Thu 02 Sep 2010 15:11:49 -0400, a écrit : It says UNICODE mode and the codes for caps lock are: press: 0x3a 0xe0 0x66 repeat: 0x3a release: 0xba 0xe0 0x 0xe6 I guess? Yes. I also just discovered the right shift key goes back a page in iceweasel. Here are the right-shift codes: showkey -s: press: 0x36 0xe0 0x6a repeat: 0x36 release: 0xb6 0xe0 0xea All this looks like one of the few keyboard glitches that linux-2.6 fixes for some keyboards known to be bogus, while other keyboards do use these scancodes to report e.g. multimedia keys. Could you try showkey -s with the older, working kernel? Samuel Stable (2.6.26) which worked fine gives the same as Testing (2.6.32): press: 0x3a 0xe0 0x66 repeat: 0x3a release: 0xba 0xe0 0xe6 ...which makes me think it's an xorg problem, but I'm not familiar with how the whole keyboard stack works. I tried a different usb keyboard (a Dell) under Testing and it works normally with iceweasel: press: 0x3a repeat: 0x3a release: 0x3b I wonder why the logitech generates so many codes. -- Tom Vier t...@triadsys.com Senior Net/Sys Admin Triad Systems Engineering, Inc. 703-956-1535 office 703-984-9093 cell 703-404-0308 helpdesk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c815c23.2070...@triadsys.com
Bug#594089: keyboard-configuration: caps lock keycode problem
Tom Vier, le Fri 03 Sep 2010 16:35:47 -0400, a écrit : On 09/02/2010 03:46 PM, Samuel Thibault wrote: Hello, Tom Vier, le Thu 02 Sep 2010 15:11:49 -0400, a écrit : It says UNICODE mode and the codes for caps lock are: press: 0x3a 0xe0 0x66 repeat: 0x3a release: 0xba 0xe0 0x 0xe6 I guess? Yes. I also just discovered the right shift key goes back a page in iceweasel. Here are the right-shift codes: showkey -s: press: 0x36 0xe0 0x6a repeat: 0x36 release: 0xb6 0xe0 0xea All this looks like one of the few keyboard glitches that linux-2.6 fixes for some keyboards known to be bogus, while other keyboards do use these scancodes to report e.g. multimedia keys. Could you try showkey -s with the older, working kernel? Stable (2.6.26) which worked fine gives the same as Testing (2.6.32): When you say Stable, you mean both kernel and Xorg? Could you also run xev on your stable box? press: 0x3a 0xe0 0x66 repeat: 0x3a release: 0xba 0xe0 0xe6 ...which makes me think it's an xorg problem, but I'm not familiar with how the whole keyboard stack works. It's a big mess :) I wonder why the logitech generates so many codes. It looks to me like a keyboard bug. Do you see any pattern, e.g. does the left shift key produce one too? Do the keys which do produce extra scancodes form any particular shape on the keyboard? Such bug should probably be fixed in the kernel, just like it is already in atkbd.c for some keyboards. Samuel -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100903234552.gk5...@const
Bug#594089: keyboard-configuration: caps lock keycode problem
Tom, le Mon 23 Aug 2010 11:43:53 -0400, a écrit : The model name is logimel, which is set in both /etc/default/keyboard and /etc/X11/xorg.conf. Which explains why Xorg has the behavior you describe: the logimel model includes the logitech base, which includes the common navigation keys, which makes XF86Back from 0xe0 0x6a, and XF86Favorites from 0xe0 0x66. Do you actually have navigation keys on your keyboard? I'm afraid we'll just have to blacklist it in the usb driver according to the usb ID. Samuel -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100903235540.ga9...@const
Bug#594089: keyboard-configuration: caps lock keycode problem
On 08/23/2010 11:59 AM, Samuel Thibault wrote: forcemerge 594089 593742 reassign 594089 linux-2.6 retitle 594089 caps lock keyboard code problem thanks Hello, Please do not submit another report for the same issue, just reassign. Sorry, didn't know I could. Tom, le Mon 23 Aug 2010 11:43:53 -0400, a écrit : KeyRelease event, serial 105, synthetic NO, window 0x341, root 0x110, subw 0x0, time 1729143, (166,-8), root:(190,128), state 0x12, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 106, synthetic NO, window 0x341, root 0x110, subw 0x0, time 1729166, (166,-8), root:(190,128), state 0x10, keycode 164 (keysym 0x1008ff30, XF86Favorites), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 106, synthetic NO, window 0x341, root 0x110, subw 0x0, time 1729166, (166,-8), root:(190,128), state 0x10, keycode 164 (keysym 0x1008ff30, XF86Favorites), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 106, synthetic NO, window 0x341, root 0x110, subw 0x0, time 1729168, (166,-8), root:(190,128), state 0x10, keycode 164 (keysym 0x1008ff30, XF86Favorites), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False That's very odd. I guess this is due either to an upgrade of linux-2.6 or an upgrade of xserver-xorg-input-evdev. At this stage I'd rather think about linux-2.6. Could you check in the linux console (without X) what happens with showkey -s ? (here it shows 0x3a 0xba) Samuel It says UNICODE mode and the codes for caps lock are: press: 0x3a 0xe0 0x66 repeat: 0x3a release: 0xba 0xe0 0x I also just discovered the right shift key goes back a page in iceweasel. Here are the right-shift codes: xev: KeyRelease event, serial 35, synthetic NO, window 0x481, root 0x110, subw 0x0, time 876874940, (169,-12), root:(199,150), state 0x11, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 35, synthetic NO, window 0x481, root 0x110, subw 0x0, time 876874941, (169,-12), root:(199,150), state 0x10, keycode 166 (keysym 0x1008ff26, XF86Back), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False showkey -s: press: 0x36 0xe0 0x6a repeat: 0x36 release: 0xb6 0xe0 0xea -- Tom Vier t...@triadsys.com Senior Net/Sys Admin Triad Systems Engineering, Inc. 703-956-1535 office 703-984-9093 cell 703-404-0308 helpdesk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c7ff6f5.3080...@triadsys.com
Bug#594089: keyboard-configuration: caps lock keycode problem
Hello, Tom Vier, le Thu 02 Sep 2010 15:11:49 -0400, a écrit : It says UNICODE mode and the codes for caps lock are: press: 0x3a 0xe0 0x66 repeat: 0x3a release: 0xba 0xe0 0x 0xe6 I guess? I also just discovered the right shift key goes back a page in iceweasel. Here are the right-shift codes: showkey -s: press: 0x36 0xe0 0x6a repeat: 0x36 release: 0xb6 0xe0 0xea All this looks like one of the few keyboard glitches that linux-2.6 fixes for some keyboards known to be bogus, while other keyboards do use these scancodes to report e.g. multimedia keys. Could you try showkey -s with the older, working kernel? Samuel -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100902194630.gh5...@const.famille.thibault.fr
Processed (with 1 errors): Re: Bug#594089: keyboard-configuration: caps lock keycode problem
Processing commands for cont...@bugs.debian.org: forcemerge 594089 593742 Bug#594089: keyboard-configuration: caps lock keycode problem Bug#593742: iceweasel: caps lock toggls bookmarks sidebar Mismatch - only Bugs in the same package can be forcibly merged: Bug 593742 is not in the same package as 594089 reassign 594089 linux-2.6 Bug #594089 [keyboard-configuration] keyboard-configuration: caps lock keycode problem Bug reassigned from package 'keyboard-configuration' to 'linux-2.6'. Bug No longer marked as found in versions console-setup/1.55. retitle 594089 caps lock keyboard code problem Bug #594089 [linux-2.6] keyboard-configuration: caps lock keycode problem Changed Bug title to 'caps lock keyboard code problem' from 'keyboard-configuration: caps lock keycode problem' thanks Stopping processing here. Please contact me if you need assistance. -- 594089: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.128257918812628.transcr...@bugs.debian.org
