Your message dated Fri, 7 May 2010 15:23:25 +0200 with message-id <20100507132325.GH12965@radis.liafa.jussieu.fr> and subject line Re: Bug#580643: [general] Chicony KU-0420 (Targus Slim Internet Media USB Keyboard) generates two incorrect symbols has caused the Debian Bug report #580643, regarding [general] Chicony KU-0420 (Targus Slim Internet Media USB Keyboard) generates two incorrect symbols to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 580643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580643 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: [general] Chicony KU-0420 (Targus Slim Internet Media USB Keyboard) generates two incorrect symbols
- From: Filipus Klutiero <chealer@gmail.com>
- Date: Fri, 07 May 2010 08:51:12 -0400
- Message-id: <[🔎] 4BE40CC0.3070507@gmail.com>
Package: general Severity: minor The media player and my computer keys on the Chicony KU-0420 (aka Targus Slim Internet Media USB Keyboard) are generating wrong symbols (with XKeyboardConfig 1.8). The first generates XF86Tools instead of XF86AudioMedia and the second generates XF86Explorer instead of XF86MyComputer.The keys generate keycodes 179 and 152. This once worked with XKeyboardConfig 1.5. I reported the bug as a regression in 1.8, but here is the answer from XKeyboardConfig's maintainer: https://bugs.freedesktop.org/show_bug.cgi?id=27606This system is different from the one on which I verified things were working. The "regression" (on my system's side) may be due to switching from kbd to evdev, if I understand Sergey correctly. But I don't remember which keyboard driver I was using, and trying to use the kbd driver doesn't help (all special keys don't work). If I understand Sergey correctly, this should be assigned to Linux.--- System information. --- Architecture: i386 Kernel: Linux 2.6.32-4-686 Debian Release: squeeze/sid 990 testing security.debian.org 990 testing ftp.ca.debian.org 500 unstable ftp.ca.debian.org 500 stable deb.opera.com 1 experimental ftp.ca.debian.org
--- End Message ---
--- Begin Message ---
- To: Filipus Klutiero <chealer@gmail.com>, 580643-done@bugs.debian.org
- Subject: Re: Bug#580643: [general] Chicony KU-0420 (Targus Slim Internet Media USB Keyboard) generates two incorrect symbols
- From: Julien Cristau <jcristau@debian.org>
- Date: Fri, 7 May 2010 15:23:25 +0200
- Message-id: <20100507132325.GH12965@radis.liafa.jussieu.fr>
- In-reply-to: <[🔎] 4BE40CC0.3070507@gmail.com>
- References: <[🔎] 4BE40CC0.3070507@gmail.com>
On Fri, May 7, 2010 at 08:51:12 -0400, Filipus Klutiero wrote: > Package: general > Severity: minor > > The media player and my computer keys on the Chicony KU-0420 (aka Targus Slim Internet Media USB Keyboard) are > generating wrong symbols (with XKeyboardConfig 1.8). The first generates > XF86Tools instead of XF86AudioMedia and the second generates XF86Explorer > instead of XF86MyComputer. > > The keys generate keycodes 179 and 152. This once worked with > XKeyboardConfig 1.5. I reported the bug as a regression in 1.8, but > here is the answer from XKeyboardConfig's maintainer: > https://bugs.freedesktop.org/show_bug.cgi?id=27606 > > This system is different from the one on which I verified things > were working. The "regression" (on my system's side) may be due to > switching from kbd to evdev, if I understand Sergey correctly. But I > don't remember which keyboard driver I was using, and trying to use > the kbd driver doesn't help (all special keys don't work). If I > understand Sergey correctly, this should be assigned to Linux. > This is not debian-user, so closing the bug. You can use the evtest program to see what scancode the kernel reports for those keys, and get things fixed in the kernel or udev (see the files in /lib/udev/keymaps) if they're not correct. Cheers, JulienAttachment: signature.asc
Description: Digital signature
--- End Message ---