[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#532253: marked as done (xkb-data: pc(pc105) maps <RWIN> instead of Super_R)

Your message dated Fri, 22 Apr 2022 17:02:01 +0200
with message-id <YmLDaVIymMJWuOMC@jcristau-z4>
and subject line Re: Bug#532253: xkb-data: pc(pc105) maps <RWIN> instead of Super_R
has caused the Debian Bug report #532253,
regarding xkb-data: pc(pc105) maps <RWIN> instead of Super_R
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.)


-- 
532253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532253
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: xkb-data,x11-xkb-utils
Version: 1.6-1
Severity: important

In /usr/share/X11/xkb/symbols/pc, one can read:

    key <LWIN> {	[ Super_L			]	};
    modifier_map Mod4   { <LWIN> };

    [...]
    key <RWIN> {	[ Super_R			]	};
    modifier_map Mod4   { <RWIN> };

And a couple of similar stanzas.

I use the following xkb definition for my keyboard:

    default xkb_keymap "mad_fr" {
	xkb_keycodes  { include "evdev+aliases(qwerty)" };
	xkb_types     { include "complete" };
	xkb_compat    { include "complete" };
	xkb_symbols   {
	    include "pc(pc105)+us+inet(logiaccess)"
	    replace key <CAPS> { [ Super_L,   Super_L   ] };
	    replace key <LWIN> { [ Super_L,   Super_L   ] };

	    replace key <RALT> { [ Multi_key, Multi_key ] };
	    replace key <RWIN> { [ Multi_key, Multi_key ] };
	    replace key <RCTL> { [ Insert,    Insert    ] };
	    replace key <MENU> { [ Multi_key, Multi_key ] };
	    modifier_map Lock    { Caps_Lock };
	    modifier_map Control { <LCTL>, Control_L };
	    modifier_map Mod1    { <LALT>, Alt_L };
	    modifier_map Mod2    { Num_Lock };
	    modifier_map Mod4    { <LWIN>, <CAPS>, Super_L };
	};
	xkb_geometry  { include "pc(pc105)" };
    };

    // vim:set ft=xkb:

Sadly, because <RWIN> is put in the modifier_map Mod4, even when I remap
<RWIN> to Multi_key, it remains in the modifier_map as <RWIN> which
yields really broken configuration for me. I've been forced to
temporarily add:

    modifier_map Mod5    { <RWIN> };

to avoid the problem, which yields a warning from xkbcomp because RWIN
is associated to two maps.

I would suggest to use Super_R in the Mod4 map (and Super_L for the same
reason, and probably some other similar fixes would be nice across the
files), or that xkbcomp provides some way to empty a given modifier_map,
instead of _only_ providing the "extend" semantics.

Without one or the other, it makes it pretty difficult to remap magic
keys, which is really important for some quite broken (as in badly
placed keys) laptop keyboards...

--- End Message ---
--- Begin Message --- 
Closing this old report, the requested change is clearly not happening,
and would have had to be submitted upstream anyway.

Cheers,
Julien

On Sun, Jun 07, 2009 at 11:18:53PM +0200, Pierre Habouzit wrote:
> Package: xkb-data,x11-xkb-utils
> Version: 1.6-1
> Severity: important
> 
> In /usr/share/X11/xkb/symbols/pc, one can read:
> 
>     key <LWIN> {	[ Super_L			]	};
>     modifier_map Mod4   { <LWIN> };
> 
>     [...]
>     key <RWIN> {	[ Super_R			]	};
>     modifier_map Mod4   { <RWIN> };
> 
> And a couple of similar stanzas.
> 
> I use the following xkb definition for my keyboard:
> 
>     default xkb_keymap "mad_fr" {
> 	xkb_keycodes  { include "evdev+aliases(qwerty)" };
> 	xkb_types     { include "complete" };
> 	xkb_compat    { include "complete" };
> 	xkb_symbols   {
> 	    include "pc(pc105)+us+inet(logiaccess)"
> 	    replace key <CAPS> { [ Super_L,   Super_L   ] };
> 	    replace key <LWIN> { [ Super_L,   Super_L   ] };
> 
> 	    replace key <RALT> { [ Multi_key, Multi_key ] };
> 	    replace key <RWIN> { [ Multi_key, Multi_key ] };
> 	    replace key <RCTL> { [ Insert,    Insert    ] };
> 	    replace key <MENU> { [ Multi_key, Multi_key ] };
> 	    modifier_map Lock    { Caps_Lock };
> 	    modifier_map Control { <LCTL>, Control_L };
> 	    modifier_map Mod1    { <LALT>, Alt_L };
> 	    modifier_map Mod2    { Num_Lock };
> 	    modifier_map Mod4    { <LWIN>, <CAPS>, Super_L };
> 	};
> 	xkb_geometry  { include "pc(pc105)" };
>     };
> 
>     // vim:set ft=xkb:
> 
> Sadly, because <RWIN> is put in the modifier_map Mod4, even when I remap
> <RWIN> to Multi_key, it remains in the modifier_map as <RWIN> which
> yields really broken configuration for me. I've been forced to
> temporarily add:
> 
>     modifier_map Mod5    { <RWIN> };
> 
> to avoid the problem, which yields a warning from xkbcomp because RWIN
> is associated to two maps.
> 
> I would suggest to use Super_R in the Mod4 map (and Super_L for the same
> reason, and probably some other similar fixes would be nice across the
> files), or that xkbcomp provides some way to empty a given modifier_map,
> instead of _only_ providing the "extend" semantics.
> 
> Without one or the other, it makes it pretty difficult to remap magic
> keys, which is really important for some quite broken (as in badly
> placed keys) laptop keyboards...
> 
>

--- End Message ---
Reply to: