Bug#409612: xlibs-data: Modifier mappings broken
In gmane.comp.window-managers.ion.general, you wrote: Since Tuomo has symbols/pc/pc, I feel he is using old xkbdata instead of xkeyboard-config. So first thing he should do is upgrading to some recent version of xkeyboard-config. Otherwise our fixes would not make sense. I'm using whatever is in Etch, and as stated in another reply to the Debian maintainer, I'm unlikely to be upgrading Linux, or *nix, ever. It has become too painful. Maybe some people on the Ion list can of more help, but ... PS. This whole thread is spread and fucked up over many different mailing lists and recipients. I apparently only got this post, because news.gmane.org shows shows through NNTP the post for gmane.comp.window-managers.ion.general, because the address of that list is in the headers, and it got the post through another list, although the post never actually got on the list (requiring subscription, to combat spam). But I can't reply to that list, because they've not allowed posting through gmane, even if subscription wasn't required, which I don't know. Mailing list architecture is fucked up, and should be more based on subscription to threads than lists/groups. -- Tuomo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409612: xlibs-data: Modifier mappings broken
On 2007-09-23 19:46 +0200, Mohammed Adnène Trojette wrote:
I forwarded your bug upstream. And upstream is asking to try commenting
the lines
key SUPR {[ NoSymbol, Super_L ] };
modifier_map Mod4 { SUPR };
in symbols/pc
(please see http://bugs.freedesktop.org/show_bug.cgi?id=12526)
There appears to be absolutely no effect. Xmodmap still reports
the same broken configuration. Not that I have a symbols/pc file
either, but symbols/pc/pc.
(No, I can't be arsed to register on the webshit known as bugzilla
to reply there. Projects that only provide webshit contact for reporting
bugs, apparently do not want to know of them. That is why I originally
reported this with Debian's reportbug.)
--
Tuomo
Bug#409612: xlibs-data: Modifier mappings broken
On Mon, Sep 24, 2007 at 05:37:28PM +0300, Tuomo Valkonen wrote: snip There appears to be absolutely no effect. Xmodmap still reports the same broken configuration. Not that I have a symbols/pc file either, but symbols/pc/pc. snip -- Tuomo Tuomo already stated that he doesn't use xkb, so changing the xkb config files isn't going to really solve anything for him. I can say that on my home machine I do get the doubled Super_L keysym but can't at the moment test commenting those lines out, but I will when I get home this evening. -Etan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409612: xlibs-data: Modifier mappings broken
Since Tuomo has symbols/pc/pc, I feel he is using old xkbdata instead of xkeyboard-config. So first thing he should do is upgrading to some recent version of xkeyboard-config. Otherwise our fixes would not make sense. Cheers, Sergey On Mon, 2007-09-24 at 10:49 -0400, Etan Reisner wrote: On Mon, Sep 24, 2007 at 05:37:28PM +0300, Tuomo Valkonen wrote: snip There appears to be absolutely no effect. Xmodmap still reports the same broken configuration. Not that I have a symbols/pc file either, but symbols/pc/pc. snip -- Tuomo Tuomo already stated that he doesn't use xkb, so changing the xkb config files isn't going to really solve anything for him. I can say that on my home machine I do get the doubled Super_L keysym but can't at the moment test commenting those lines out, but I will when I get home this evening. -Etan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409612: xlibs-data: Modifier mappings broken
(Quoting full post, because Cc:ing to the Ion list.) On 2007-09-23 03:01 +0200, Mohammed Adnène Trojette wrote: tag 409612 moreinfo thanks On Sun, Feb 04, 2007, tuomov wrote: The modifier mappings in stock keyboard layouts are broken. For details, I'll just attach the Ion FAQ entry below from http://iki.fi/tuomov/ion/faq/entries/Modifier_releases.html. (I have not myself experienced that problem, though -- I don't use Xkb crud at all, because customisation of Xkb based layouts is too laboursome, difficult, undocumented etc. -- but users have experienced it on various systems, and this seems the easiest channel to report the problem.) --- _Ion doesn't notice that a modifier has been released (in actions that use like `kpress_wait`, such as META+C, or in “grabmenus”)._ This is most likely to be an X bug/keyboard misconfiguration, when you have changed the “META” key of Ion to Mod4, or something else that supposed has one of the Win-keys bound to it. For some reason, some Xorg comes with some totally broken stock keyboard layouts that define multiple keycodes for the `Super_L` and such “keysyms”, one of them spurious. However, various part of X or Xlib can not handle that, and report the wrong keycode when queried.sup1/sup To check if this is the case, first run `xmodmap` to check what key is bound to the Mod4 (or perhaps Mod3 depending on the configuration) modifier. You may see a line like this: mod4Super_L (0x7f), Hyper_L (0x80) The number 0x7f=127 is the keycode, and this is highly likely the wrong keycode. Check with `xmodmap -pke|grep Super_L` to see what keycodes have `Super_L` bound to them. If you see something like this, your keymap is misconfigured: keycode 115 = Super_L keycode 127 = NoSymbol Super_L The keycode 115 is the keycode for the real left Win key, and 127 is spurious. However, the modifier subsystem only seems to see the latter. Putting the following commands in `~/.Xmodmap` and runnning `xmodmap ~/.Xmodmap` should fix the issue. You may also want/need to repeat for the other Win keys (`Hyper_L` and 0x80=127 in our example case). remove mod4 = Super_L keycode 127 = NoSymbol add mod4 = Super_L (The `remove` command is needed for some reason to not confuse X.) Unless your system configuration is totally weird (and I wouldn't put it past systems built to run Gnome), next time you start X, `~/.Xmodmap` should be loaded automatically. On a working modifier configuration running `xmodmap` should display a line like below (0x73 following `Super_L` being the important part). mod4Super_L (0x73) --- Hello, does this bug apply to Debian's Xorg? Is it still a problem with the recent Xorg versions in Debian? What is the output of the following command? % xprop -root | grep XKB (I don't use ion myself.) -- Mohammed Adnène Trojette Does recent mean something later than etch? In that case I can't help now, and unlikely in the future either (because the present 2.6.14 kernel and etch setup is likely to be my last Linux setup ever unless something marvellous happens, which seems unlikely). In any case, the output from that command is _XKB_RULES_NAMES(STRING) = xfree86, logicdp, fi, nodeadkeys, ctrl:nocaps But, as mentioned above, I don't actually use Xkb crud at all myself (thanks to the use of ISO_Level3_Shift instead of Mode_Switch, only the latter of which can be customised easily with xmodmap, Xkb configuration itself being cryptic and ultra-complex like almost anything recent in *nix). Maybe some people on the Ion list can be of more help; I just reported this bug because nobody else seemed to be arsed to. -- Tuomo
Bug#409612: xlibs-data: Modifier mappings broken
On Sun, Sep 23, 2007, Tuomo Valkonen wrote:
Does recent mean something later than etch? In that case I can't
help now, and unlikely in the future either (because the present
2.6.14 kernel and etch setup is likely to be my last Linux setup
ever unless something marvellous happens, which seems unlikely).
In any case, the output from that command is
_XKB_RULES_NAMES(STRING) = xfree86, logicdp, fi, nodeadkeys,
ctrl:nocaps
But, as mentioned above, I don't actually use Xkb crud at all myself
(thanks to the use of ISO_Level3_Shift instead of Mode_Switch, only
the latter of which can be customised easily with xmodmap, Xkb
configuration itself being cryptic and ultra-complex like almost
anything recent in *nix).
Maybe some people on the Ion list can be of more help; I just reported
this bug because nobody else seemed to be arsed to.
I forwarded your bug upstream. And upstream is asking to try commenting
the lines
key SUPR {[ NoSymbol, Super_L ] };
modifier_map Mod4 { SUPR };
in symbols/pc
(please see http://bugs.freedesktop.org/show_bug.cgi?id=12526)
--
Mohammed Adnène Trojette
Processed: Re: Bug#409612: xlibs-data: Modifier mappings broken
Processing commands for [EMAIL PROTECTED]: tag 409612 moreinfo Bug#409612: xlibs-data: Modifier mappings broken There were no tags set. Tags added: moreinfo thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409612: xlibs-data: Modifier mappings broken
Package: xlibs-data Version: 1:7.1.0-11 Severity: important The modifier mappings in stock keyboard layouts are broken. For details, I'll just attach the Ion FAQ entry below from http://iki.fi/tuomov/ion/faq/entries/Modifier_releases.html. (I have not myself experienced that problem, though -- I don't use Xkb crud at all, because customisation of Xkb based layouts is too laboursome, difficult, undocumented etc. -- but users have experienced it on various systems, and this seems the easiest channel to report the problem.) --- _Ion doesn't notice that a modifier has been released (in actions that use like `kpress_wait`, such as META+C, or in “grabmenus”)._ This is most likely to be an X bug/keyboard misconfiguration, when you have changed the “META” key of Ion to Mod4, or something else that supposed has one of the Win-keys bound to it. For some reason, some Xorg comes with some totally broken stock keyboard layouts that define multiple keycodes for the `Super_L` and such “keysyms”, one of them spurious. However, various part of X or Xlib can not handle that, and report the wrong keycode when queried.sup1/sup To check if this is the case, first run `xmodmap` to check what key is bound to the Mod4 (or perhaps Mod3 depending on the configuration) modifier. You may see a line like this: mod4Super_L (0x7f), Hyper_L (0x80) The number 0x7f=127 is the keycode, and this is highly likely the wrong keycode. Check with `xmodmap -pke|grep Super_L` to see what keycodes have `Super_L` bound to them. If you see something like this, your keymap is misconfigured: keycode 115 = Super_L keycode 127 = NoSymbol Super_L The keycode 115 is the keycode for the real left Win key, and 127 is spurious. However, the modifier subsystem only seems to see the latter. Putting the following commands in `~/.Xmodmap` and runnning `xmodmap ~/.Xmodmap` should fix the issue. You may also want/need to repeat for the other Win keys (`Hyper_L` and 0x80=127 in our example case). remove mod4 = Super_L keycode 127 = NoSymbol add mod4 = Super_L (The `remove` command is needed for some reason to not confuse X.) Unless your system configuration is totally weird (and I wouldn't put it past systems built to run Gnome), next time you start X, `~/.Xmodmap` should be loaded automatically. On a working modifier configuration running `xmodmap` should display a line like below (0x73 following `Super_L` being the important part). mod4Super_L (0x73) --- sup1/sup `XKeysymToKeycode` in particular can only return one keycode. However, `XGetModifierMapping` should be able to report more, but for some reason doesn't. Maybe it uses the former. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14 Locale: LANG=C, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Versions of packages xlibs-data depends on: ii libx11-6 2:1.0.0-8 X11 client-side library ii xbitmaps 1.0.1-2Base X bitmaps ii xcursor-themes1.0.1-4Base X cursor themes xlibs-data recommends no packages. -- no debconf information
