-
Notifications
You must be signed in to change notification settings - Fork 56
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
BUG: numeric keypad no longer writes keys anymore #702
Comments
I have this issue too. Regardless of numlock state pressing numpad keys results in them functioning as arrow keys. Curiously the number 5 on the numpad works correctly. |
i'm experiencing the same issue. I installed numlockx and its status respect the keyboard leds. If numlock led is on, which means that I manually enable Numlock, it returns ON. The other way around works fine too. |
Same issue here with wired reddragon keyboard |
I tracked it down to commit 0491c4b which also includes an update to iced. iced was updated from pop-os/iced@0619950 to pop-os/iced@f2f9dfc. Unfortunately, there's ~42,000 lines changed between those two versions. I think it has something to do with the update to using winit events for the key events, but still not clear. |
After digging further it seems that the libcosmic update broke backwards compatibility and apps need to be updated. The value that used to be relied on,
cosmic-term and other apps were written to only look at I found a simple workaround that I think works for cosmic-term by just checking whether the named_key == modified_key, but I'm not sure if that will work for every other app. |
cosmic-edit is effected as well. |
I can write numbers in text inputs while holding
shift + &
for example, but the keypad no longer works (since some time now)The text was updated successfully, but these errors were encountered: