Remap So-Called "Copilot Key"?

Ask Fedora
21

Right. Ironically, the xkeyboard-config change has defeated the change in KDE Frameworks 6.18, which assumed the key would continue to be treated as Meta+Shift+F23 and would have allowed it to be used for shortcuts in KDE Plasma.

It’s now more awkward in KDE because Qt doesn’t have a keycode for XF86Assistant:

The KDE dev there says:

And this is not simple to get, because Qt support oldish platforms, Redhat 8.6 released 3 years ago. Qt for Linux/X11 | Qt 6.10 .

So this XF86Assistant will take years to be there. Unless we go through some hoops.

22

XF86Assistant has been available since xorgproto-2021.2 (presumably roughly the same for libxkbcommon), so over 4 years now. That doesn’t help with RHEL8 but RHEL9 and newer have it at least. But because it’s remapped in XKB it’s possible to remap it back to plain F23 via XKB too to make the KDE workaround work again. Might be worth filing an xkeyboard-config issue to have this as an option for this use-case.

23

Ummmmm… I know they are removing it to remap it to something else soon. Hmmmmm…

24

Who’s “they”?

25

The people at the manufactures and Windows themself. They are removing it for good.

26

Interesting, do you have a source please?

27

Windows (and Fedora) are removing the Copilot key!

28

That’s a Windows-specific software change, not something at the hardware or BIOS level.

The video makes no mention of Fedora, nor is Fedora in its title. It’s very poor etiquette to give a link a deceptive title in the way that you did.

29

It might be fixed with Plasma 6.8 or later KF6 or 7 version.

30

Source?

31

input-remapper is the best way to remap it. But, Plasma might fix it at later point. as no sources say.

32

Useful thread on the challenges around this in Plasma.

33

Screenshot_20260810_135244
Screenshot_20260810_1352441366×676 112 KB

check out TechPerson3033 - KDE Discuss ( click expand on the page)