Remapping the Copilot Key on Lenovo IdeaPad Slim 3 14ARP10 — No Events Detected (Help Needed)

[idanbarir]

Hi everyone, I’m using Zorin OS on a Lenovo IdeaPad Slim 3 14ARP10, and I’ve run into a very strange issue with the physical Copilot key on the keyboard.

I’m trying to remap this key to Left Ctrl, but I’ve discovered that the key does not behave like a normal keyboard key under Linux.

Here’s what I’ve tested so far:

• evtest → no event at all when pressing the Copilot key
• xev → no keypress event
• acpi_listen → no ACPI/WMI event
• udevadm monitor → no udev activity
• keyd / kmonad / hwdb → cannot detect or remap the key
• The key does not appear in /dev/input/event*
• It does not send a scancode, keycode, or ACPI interrupt

It seems that on this specific Lenovo model, the Copilot key is implemented as a firmware-level Windows-only hotkey, and Linux never receives any input event from it.

Before I give up completely — Has anyone with a Lenovo IdeaPad Slim 3 (or similar Ideapad models) managed to get the Copilot key to generate any detectable event under Linux?

If someone has:

• a kernel patch
• a WMI driver workaround
• a firmware setting
• or any method to expose this key to Linux as an input event

I would really appreciate your help.

Thanks in advance.

[Ponce-De-Leon]

Welcome to the Forum!

You could try Input Remapper. You can install it in Software Center or with the Terminal Command sudo apt install input-remapper or You can download the latest Version from the Github Page:

Release 2.2.1 · sezanzeb/input-remapper · GitHub

[swarfendor437]

Hi and welcome.

I used this in my search as Zorin is based on Ubuntu 24.04:

"Remapping the Copilot Key on Lenovo IdeaPad Slim 3 14ARP10 — No Events Detected (Help Needed) on Ubuntu 24.04"

Brave A.I. search via Mojeek gives:

" Remapping the Copilot key on a Lenovo IdeaPad Slim 3 14ARP10 running Ubuntu 24.04 is often impossible because the key is implemented as a firmware-level Windows-only hotkey that does not send any input events to the Linux kernel.

If the key is not detected by standard tools like evtest or xev , it is physically disconnected from the Linux input subsystem. In this specific scenario, standard remapping software such as keyd or evsieve will fail because there are no scan codes to intercept.

• Verification : Run sudo evtest or cat /dev/input/event* and press the Copilot key; if no output appears, the hardware does not communicate with Ubuntu.
• Alternative : If the key does register as a combination (typically LeftShift + LeftMeta + F23 ), you can remap it using keyd with the configuration f23+leftshift+leftmeta = M-t (or your desired shortcut).
• Conclusion : If no events are detected, the key cannot be remapped on Ubuntu for this specific Lenovo model, as the function is hard-coded in the Windows-only firmware.

AI-generated answer. Please verify critical facts."

[idanbarir]

@Ponce-De-Leon

Input Remapper

Just wanted to thank everyone who replied and tried to help — your suggestions pushed me in the right direction.

I ended up trying Input Remapper, as suggested, and it did work, but only after one important tweak that wasn’t obvious at first.

What made it work

Input Remapper was able to detect the Copilot key event on my Lenovo IdeaPad Slim 3 14ARP10, but it kept showing the message:

“The device was not grabbed”

As long as this message appears, the remapping won’t actually take effect.

The fix

The solution was to run Input Remapper under X11 (Xorg) instead of Wayland. Luckily, I was already using Xorg for other reasons, but the key point is:

• On X11, Input Remapper can grab the keyboard device
• On Wayland, it cannot, due to session-level restrictions

Once I launched Input Remapper on X11, the “device not grabbed” message disappeared, and the remapping worked perfectly.

Final result

The Copilot key on this model sends a strange combination:

Super L + Shift L + XF86TouchpadOff

Input Remapper was able to catch that sequence and map it cleanly to Control_L, giving me a fully functional Ctrl key in place of the Copilot key.

Everything now works reliably on startup using Autoload.

Thanks again to everyone who helped — hopefully this post will save someone else with the same Lenovo model a lot of time.