Your message dated Wed, 22 Apr 2009 11:40:04 -0400
with message-id <20090422154004.gi8...@morgul.net>
and subject line Re: Bug#525081: xserver-xorg-input-kbd: keycode for windows
keys has changed
has caused the Debian Bug report #525081,
regarding xserver-xorg-input-kbd: keycode for windows keys has changed
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 ow...@bugs.debian.org
immediately.)
--
525081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525081
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-input-kbd
Version: 1:1.3.2-3
Severity: normal
Hello. I'm not 100% sure that I'm submitting this bug against the right
package, but figure this is a good place to start. Please feel free to
re-assign.
Sometime between lenny and current sid, the keycode and keysym generated
by the Windows key on my Thinkpad X300 changed. On the same hardware,
if I boot to a lenny installation and run xev, I see the following
output when pressing the windows key:
KeyPress event, serial 31, synthetic NO, window 0x3600001,
root 0x69, subw 0x0, time 50752, (-302,603), root:(610,631),
state 0x0, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 34, synthetic NO, window 0x3600001,
root 0x69, subw 0x0, time 51048, (-302,603), root:(610,631),
state 0x40, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
On a sid system, the same thing shows the different keysym and keycode
values:
KeyPress event, serial 31, synthetic NO, window 0x3e00001,
root 0xb4, subw 0x0, time 833661, (-348,734), root:(484,759),
state 0x0, keycode 133 (keysym 0xff20, Multi_key), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: True
KeyRelease event, serial 34, synthetic NO, window 0x3e00001,
root 0xb4, subw 0x0, time 833901, (-348,734), root:(484,759),
state 0x0, keycode 133 (keysym 0xff20, Multi_key), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
This breaks the ability to use xkb to map useful functionality to the
windows keys (e.g. setxkbmap -option altwin:meta_win)
Please don't hesitate to ask for more info.
noah
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.29-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages xserver-xorg-input-kbd depends on:
ii libc6 2.9-7 GNU C Library: Shared libraries
ii xserver-xorg-core 2:1.6.1-1 Xorg X server - core server
xserver-xorg-input-kbd recommends no packages.
xserver-xorg-input-kbd suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, Apr 22, 2009 at 05:20:39PM +0200, Julien Cristau wrote:
> > After finding this in the Xorg.0.log:
> > Option "xkb_options" "lv3:ralt_switch,compose:lwin,grp:alt_shift_toggle"
> >
> > It occurred to me to try clearing out the xkbd options with "setxkbmap
> > -option", which seemed to do the right thing.
> >
> > So, the question is, where is the default xkb_options options getting
> > set,
>
> In /etc/default/console-setup, the XKBOPTIONS variable.
>
> > and why is it getting this value?
> >
> The default as far as I can tell from console-setup's config script is
> to not have any compose:foo option. So I can't see any way for
> console-setup to have picked that up except if you had it set previously
> in xorg.conf, or selected it manually. But maybe I'm missing something.
OK, so this is likely somehow my fault, and not a bug. Reconfiguring
console-setup fixed things for me.
I've closed this bug. Thanks for you help.
noah
signature.asc
Description: Digital signature
--- End Message ---
