Bug 12526

Try commenting the lines

    key <SUPR> {        [ NoSymbol, Super_L     ]       };
    modifier_map Mod4   { <SUPR> };

in symbols/pc

I have tried to comment this line but it does exactly thing as before. Any other idea?

What do you see in xmodmap now?

xmodmap -pke|grep Super_L

(In reply to comment #3)
> What do you see in xmodmap now?
> 
> xmodmap -pke|grep Super_L
> 

keycode 115 = Super_L
keycode 127 = NoSymbol Super_L

That is very odd. The keycode 127 is SUPR and once you commented it out, it should be gone. Could you please do xkbcomp :0 -xkb out.xkb and attach out.xkb here?

Commenting out those from my symbols/pc file does correct the output of 'xmodmap -pke | grep Super_L' so that it only has the 'keycode 115 = Super_L' entry but it also removes Super_L from the mod4 line in the output of 'xmodmap'. Which makes sense since I assume that is what the modifier_map line I commented out is about, but that leaves me with a mod4 entry of "mod4 Hyper_L (0x80)" which is slightly less than desired.

Sergey: Anything else you want me to try or need me to do? Also, do you not have this happening on the machines you have access to? Or is this a debian only issue somehow?

For reference an xkb.out generated from the command you suggested has in it a "<SUPR> = 127;" line in it but does not have a "modifier_map Mod4 { <SUPR> };" line in it.

What if you add (after those two commented out lines)

modifier_map Mod4   { Super_L };

Bugzilla Upgrade Mass Bug Change

NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO.

  - benjsc
    fd.o Wrangler

I just tried commenting out those two lines and adding the line 

  modifier_map Mod4   { Super_L };

With xmodmap I get

  mod4        Super_L (0x73),  Hyper_L (0x80)

and 

  $ xmodmap -pke | grep Super_L
  keycode 115 = Super_L

This is on a fully updated Debian unstable.

I should probably add that before I had exactly the same output as the previous reporter (i.e. two lines with xmodmap -pke | grep Super_L).

>   $ xmodmap -pke | grep Super_L
>   keycode 115 = Super_L
So, this is what's expected isn't it? Is this the behaviour you want?

As per the Ion FAQ entry, I guess so.

I came into this because I've had problems after I updated my Debian unstable system recently. I've configured GNOME/Metacity to use Windows key + F1 to switch desktop, and sometimes when I switch desktop with that combination, X or something in X gets to a state where it thinks the Windows key is depressed all the time. Hitting or holding the Windows key doesn't help it out of the mess.

This means that the system is completely broken. I can't use the keyboard because everything I press is interpreted as a keystroke beginning with Super, and I can't use the mouse because Super + mouse click means "move window" so the application underneath never gets the click. I've found no way out other than to kill and restart X. Really annoying, as you might imagine. It never happened before the update.

I hope it's caused by this bug. After I patched the symbols/pc file, I've not experienced any trouble. But that's only a couple of hours of testing. I'll test it some more and report back if the problem occurs again.

Another idea. Could you please try returning symbols/pc to original state - and using XkbOptions altwin:super_win and altwin:alt_super_win. They should have similar effect.
I would be very interested in your results.

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/5.