Your message dated Fri, 31 Dec 2010 17:51:58 +0100
with message-id <[email protected]>
and subject line Re: Bug#488685: xserver-xorg-input-kbd: Acer TravelMate 2303M
: the 'Fn' key is inverted
has caused the Debian Bug report #488685,
regarding xserver-xorg-input-kbd: Acer TravelMate 2303M : the 'Fn' key is
inverted
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 [email protected]
immediately.)
--
488685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488685
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xserver-xorg-input-kbd
Version: 1:1.3.1-1
Severity: normal
Hi,
My laptop is an Acer TravelMate 2303M. There is a blue 'Fn' (function) key
to activate extra (blue) functions on some keys. For instance, the 'j' key is
also '1' by pressing keys 'Fn' plus 'j'
Now the 'Fn' is inverted : I have to press Fn+j keys to get a 'j'.
Without the 'Fn' key I get a '1'.
Here is the output of "xev" while pressing and releasing the 'j' key (i.e.
without the 'Fn' key):
KeyPress event, serial 34, synthetic NO, window 0x2600001,
root 0x55, subw 0x0, time 203540, (340,244), root:(344,290),
state 0x10, keycode 87 (keysym 0xffb1, KP_1), same_screen YES,
XLookupString gives 1 bytes: (31) "1"
XmbLookupString gives 1 bytes: (31) "1"
XFilterEvent returns: False
KeyRelease event, serial 34, synthetic NO, window 0x2600001,
root 0x55, subw 0x0, time 203670, (340,244), root:(344,290),
state 0x10, keycode 87 (keysym 0xffb1, KP_1), same_screen YES,
XLookupString gives 1 bytes: (31) "1"
XFilterEvent returns: False
Now, by pressing 'Fn+j' :
KeyPress event, serial 34, synthetic NO, window 0x2600001,
root 0x55, subw 0x0, time 205218, (340,244), root:(344,290),
state 0x10, keycode 44 (keysym 0x6a, j), same_screen YES,
XLookupString gives 1 bytes: (6a) "j"
XmbLookupString gives 1 bytes: (6a) "j"
XFilterEvent returns: False
KeyRelease event, serial 34, synthetic NO, window 0x2600001,
root 0x55, subw 0x0, time 205402, (340,244), root:(344,290),
state 0x10, keycode 44 (keysym 0x6a, j), same_screen YES,
XLookupString gives 1 bytes: (6a) "j"
XFilterEvent returns: False
As you can see, it should be the opposite.
However, on a text console, the 'Fn' behaves normally: 'j' means 'j'
and 'Fn+j' means '1'. Here is the "showkey" output:
0x24 (keycode 106 press)
0xa4
0x4f (keycode 49 press)
0xcf
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages xserver-xorg-input-kbd depends on:
ii libc6 2.7-10 GNU C Library: Shared libraries
ii xserver-xorg-core 2:1.4.1~git20080517-2 Xorg X server - core server
xserver-xorg-input-kbd recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, Dec 31, 2010 at 03:01:16PM +0100, Christophe Lohr wrote:
> Hi,
> Now I use a Dell Latitude D410, and no more an Acer TravelMate
> 2303M... So, I can't test it. I'm so sorry.
>
> Regards
> Happy new year!
OK closing the bug then...
If anyone owning an Acer TravelMate 2303M experience this bug, just
reopen it !
Best Regards
--
Julien Viard de Galbert <[email protected]>
http://silicone.homelinux.org/ <[email protected]>
--- End Message ---
