Submission checklist

• I have searched existing issues and confirmed this is not a duplicate.
• I am using the latest available version of Noctalia.

Bug description

After upgrading from Noctalia V4 to V5, the brightness hotkeys (Fn+F5 and Fn+F6) stopped working on my Lenovo Legion Slim 7 (82K8).

The brightness slider in Noctalia still works correctly, and brightness can be adjusted using brightnessctl. However, pressing Fn+F5 or Fn+F6 does nothing.

I verified that the brightness keybindings are still present in my Niri configuration and that Lenovo-related kernel modules are loaded.

The issue did not occur on Noctalia V4.

Steps to reproduce

1. Boot into Noctalia V5.
2. Log in to a Niri session.
3. Press Fn+F5 or Fn+F6.
4. Observe that brightness does not change and no key event appears to be generated.

Expected behavior

Pressing Fn+F5 should decrease screen brightness and Fn+F6 should increase screen brightness, as it did in Noctalia V4.

Actual behavior

Fn+F5 and Fn+F6 do nothing.

The brightness slider works correctly, and brightness can still be changed using brightnessctl.

Other function keys are detected normally.

Logs / error output

No relevant errors appear in journalctl -kf when pressing Fn+F5 or Fn+F6.
Brightness bindings are present in ~/.config/niri/config.kdl:
XF86MonBrightnessUp allow-when-locked=true { spawn "brightnessctl" "--class=backlight" "set" "+10%"; }
XF86MonBrightnessDown allow-when-locked=true { spawn "brightnessctl" "--class=backlight" "set" "10%-"; }
Loaded Lenovo modules:
ideapad_laptop
lenovo_wmi_hotkey_utilities
lenovo_wmi_events

Noctalia version

V5

Compositor

Niri

Distribution

Arch-based

Environment information

Laptop: Lenovo Legion Slim 7 (82K8)
Kernel: 7.0.11-1-cachyos
Niri: 26.04-1.1
Installation method: Official CachyOS packages
GPU:
* AMD Radeon Vega (Cezanne iGPU)
* NVIDIA dGPU (hybrid graphics)

Additional context

I tested the same machine using KDE Plasma Wayland on the same installation, and Fn+F5 / Fn+F6 work correctly there.

Because the issue only occurs in Noctalia V5 and did not occur in Noctalia V4, I suspect this may be related to Noctalia V5, Niri integration, or input handling within the Noctalia session.