Bug: XF86RefreshRateToggle key is eaten and not passed through.

[RedstoneTrail]

Requirements

• I've searched platform-specific issues, issues and discussions to see if this has been reported before.
• My issue does not involve multiple simultaneous key presses, OR it does but I've confirmed it is not key rollover or ghosting.

Describe the bug

My laptop keyboard has a refresh rate toggle key (fn + r). This key works normally and I have it set up in Hyprland to cycle through available refresh rates for power saving on battery.

Using evtest, I can detect presses of this key coming from /dev/input/by-path/pci-0000:00:1f.0-platform-VPC2004:00-event -> /dev/input/event6 (Ideapad extra buttons).

If I do not specify excusively /dev/input/by-path/pci-0000:00:14.0-usb-0:12:1.0-event-kbd -> /dev/input/event23 (the rest of the keyboard), then the refresh rate key does not work. It appears that the key input is not passed through from kanata.

Relevant kanata config

(defcfg
  process-unmapped-keys no
  linux-dev /dev/input/by-path/pci-0000\:00\:14.0-usb-0\:12\:1.0-event-kbd
)

(defsrc)

(deflayermap (base-layer)
  caps lctl
  f23 rctl
)

To Reproduce

With a keyboard featuring a refresh rate toggle key, try to use it without having it excluded from the linux-dev or equivalent setting in defcfg.

Expected behavior

Refresh rate toggle input is passed through to the window manager or app as without kanata.

Kanata version

kanata 1.9.0 (from nixpkgs unstable)

Debug logs

I realise this issue explicitly includes the relevant fix in my case, but I thought it would be worth mentioning for people who this is a real issue/annoyance for.

Operating system and I/O mechanism

Linux

Additional context

No response

[jtroo]

You could also use the device exclude defcfg item.

Would need debug logs to show which of the following is happening:

• Kanata is reading but not forwarding the key
  • in which case this is a bug that needs to be fixed
• Kanata is forwarding the key, but desktop processes are not handling it due to it coming from the Kanata device instead of original device
  • in which case Kanata can't do much about it