-
-
Notifications
You must be signed in to change notification settings - Fork 905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Numlock not enabled when explicitly set #6573
Comments
Are you using a display manager? I had some strange numlock behavior similar to this when using lemurs. As soon as I removed it and went back to launching from console the behavior went away. No clue if it was related to the dm or some other dependency. |
Yes, i forgor : I use greetd-agreety the most dubious way I could figure out. I autologin my user, launch Hyprland then launch my pretty hyprlock as an unsafe login manager (after setting numlock_by_default of course). |
I have the same issue (the numlock LED is on, but numbers don't work, I have to press numlock twice) on very minimal system - I don't use any login manager or screen locker, just plain Hyprland. Interestingly, the numlock doesn't break on startup, but instead it breakes every time Hyprland reloads the config file. The issue doesn't seem to be related to mkinitcpio-numlock in any way, I have tried it with and without the mkinitcpio hook. |
I'm facing the same problem. The problem started to occur about two updates ago (the current version of my package installed from the ArchLinux repository: Hyprland 0.41.2-1). Also, about two updates ago, Hyprland did not support controlling the numlock indicator on my keyboard, and I had to use the "brightnessctl -d 'input34::numlock' set 1" binding to achieve this functionality. However, as soon as I installed the Hyprland updates, it began to support the management of this. But along with this, the problem described above also appeared. Has anyone found a solution? |
Bug or Regression?
Regression
System Info and Version
System/Version info
Description
Hello,
I set numlock_by_default = true in my config file but since 0.40.0, even though my keyboard led indicates numlock enabled, I have to press it twice to get it working.
How to reproduce
I got the same issue on a fresh install by copying my config. It also might be related to mkinitcpio-numlock which is enabled on my system.
Update : Even weirder, it did not happend when starting my laptop on battery.
Crash reports, logs, images, videos
No response
The text was updated successfully, but these errors were encountered: