Bug 505641

Do you happen to have an update of the xkeyboard-config package too? What version do you have currently, and if possible, before the update?

Currently it is xkeyboard-config.noarch 2.44-1.fc42 fedora.

Judging from `dnf history info 87 | grep xkeyboard`, the update was

  Upgrade   xkeyboard-config-0:2.44-1.fc42.noarch                                    Dependency      fedora
  Replaced  xkeyboard-config-0:2.42-2.fc41.noarch                                    Dependency      @System

The following change in xkeyboard-config 2.43 may have broken your shortcuts:

> Map Hyper to Mod3 by default to make Super and Hyper independent modifiers. 

See: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/blob/master/ChangeLog.md?ref_type=heads#breaking-changes-6

But I am still puzzled why: do you have an option using Hyper activated? Could you copy your keyboard config `~/.config/kxkbrc` here ?

[$Version]
update_info=kxkb_variants.upd:split-variants,kxkb.upd:remove-empty-lists,kxkb.upd:add-back-resetoptions

[Layout]
DisplayNames=
LayoutList=us
LayoutLoopCount=-1
Model=pc98
Options=ctrl:swapcaps,altwin:left_meta_win
ResetOldOptions=true
ShowFlag=false
ShowLabel=true
ShowLayoutIndicator=true
ShowSingle=false
SwitchMode=Global
Use=true
VariantList=

Are you sure you want to use PC-98 layout US layout? The PC-98 is very much legacy hardware: https://en.wikipedia.org/wiki/PC-98.

This layout does not configure `Meta` nor `Super` nor `Hyper` modifiers by default. I wonder how your shortcuts worked in the first place. Did you uncheck an option when using the workaround you mentioned previously?

I am not aware of that entirely. Actually since roughly I got this computer and installed Fedora Plasma (32? I think, in 2020), I have never changed keyboard layout. This must be the default one. It has worked till the update without problem.

> Did you uncheck an option when using the workaround you mentioned previously?

No. From I got the computer till now the only option enabled was swapping caps lock and left ctrl. For the workaround I enabled the setting "Meta is mapped to Left Win"

You are absolutely right! After changing to Generic 101-key PC and disabling the workaround, meta key works again!

This is even more confusing now...... Did the update change the default layout?

BTW, I am using a keyboard as https://gameroom.lt/100212/royal-kludge-rk96-black-wireless-mechanical.jpg which have 96 keys. I don't seem to find the exact match in KDE settings, could you give some suggestions?

(In reply to Gathur Zent from comment #7)
> You are absolutely right! After changing to Generic 101-key PC and disabling
> the workaround, meta key works again!

Glad to know you fixed it!

Indeed, the key is that the *model* was set to `pc98`, resulting in applying a legacy US layout, with some keys missing and requiring options to set them.

The model you chose is unlikely to be default in your distro, so you chose it somehow.

Some guesses:
1. Unintentionally chose the model with an unlucky mouse wheel move.
2. Your layout is 96%, so maybe you chose it for the similarity.

> This is even more confusing now...... Did the update change the default
> layout?

I previously thought it was because of the change in the low-level encoding of some modifiers. But no, it is due to the fix that *actually* apply the legacy layout corresponding to the model.

So previously, you got the layout as if you chose the generic 101 model, but that was by chance due to a bug. Now that the bug is fixed, you get the layout that is correct for the keyboard model PC-98, but incorrect for you since it’s not the right model.

> 
> BTW, I am using a keyboard as
> https://gameroom.lt/100212/royal-kludge-rk96-black-wireless-mechanical.jpg
> which have 96 keys. I don't seem to find the exact match in KDE settings,
> could you give some suggestions?

The list of models is primarily for legacy hardware. You know, when there was no USB or such 😄. For modern keyboard, the generic 101/102/104/105 will do. You will not get a picture of your exact model, but the layout will work as expected.

>I previously thought it was because of the change in the low-level encoding of some modifiers. But no, it is due to the fix that *actually* apply the legacy layout corresponding to the model.
>So previously, you got the layout as if you chose the generic 101 model, but that was by chance due to a bug. Now that the bug is fixed, you get the layout that is correct for the keyboard model PC-98, but incorrect for you since it’s not the right model.

I see! This is very interesting information and thank you so much for helping me figuring out the reason and finding out the solution. I am truly grateful to your help!

>For modern keyboard, the generic 101/102/104/105 will do. You will not get a picture of your exact model, but the layout will work as expected.

Great! I'll stick to 101 then. Have a nice day! (I don't seem to have the right to close the issue)