The new Microsoftslop copilot key always sends the following key-sequence when pressed:

copilot key down: left-shift-down left-meta-down f23-down f23-up left-meta-up left-shift-up
copilot key up: <null>

This means there’s no real key-up event when you release the key --> it can’t be used (properly) as a modifier like ctrl or alt.

The workaround is to send a pretend key-up event after a time delay, but then you mustn’t be too slow / fast when pressing a shortcut.

tldr: AI took a perfectly working modifier key from you.

— edit —
Some keyboards apparently do the “right” thing and don’t send the whole sequence at once, you can remap those properly with keyd, see: https://github.com/rvaiya/keyd/issues/1025#issuecomment-2971556563 / https://github.com/rvaiya/keyd/issues/825

copilot key down: left-shift-down left-meta-down f23-down
copilot key up: f23-up left-meta-up left-shift-up

this will still break left-shift + remapped copilot and left-meta + remapped copilot, but RCtrl remaps should work as expected

  • ageedizzle@piefed.caEnglish
    2·
    4 hours ago

    That sounds way beyond the average users technical expertise. But it sounds like it might work. If you manage to figure out how to do that please let me know

    • ominous ocelot@leminal.spaceEnglish
      1·
      2 hours ago

      Hit f2 or del or whatever the screen tells you during boot to enter the UEFI menu (or hold shift while clicking restart in w11 or w10 to reboot into uefi). Then search for an option to change the buttons behaviour to right ctrl instead of cockpit.

      I don’t own an ai Thinkpad, sorry.

      • ageedizzle@piefed.caEnglish
        1·
        2 hours ago

        Thanks for the info.

        I don’t own an AI Thinkpad either, I’m just thinking ahead for when I eventually have to purchase a new computer.