Numlock should be on but acts as if it's off

[rmunn]

I have noticed strange behavior with the Numlock key in one specific app, Tellico, a book catalogue program. I usually have Numlock off because I prefer to use Home/End keys on my laptop keypad rather than holding down a Fn key combo, but when I launch Tellico, I turn Numlock on so I can enter ISBNs more easily. When I press Ctrl+I to open Tellico's ISBN search dialog (it can search for titles or authors too but I always use ISBNs), if I start typing on the numeric keypad, I discover that Numlock is off, and pressing (say) 4 on the keypad will move the cursor left instead of typing a 4. So I press Numlock... and the keypad 4 still acts like an arrow. I press Numlock again, and now the numeric keypad types numbers.

In other words, when I launch the Tellico Ctrl+I dialog, Tellico thinks Numlock is on, but Hyprland thinks Numlock is off. Or perhaps it's vice-versa; I'm not sure. At any rate, I have to press the Numlock key twice to toggle it. This only happens in Tellico; I haven't seen this behavior in any other software so far. Unfortunately, this laptop keyboard doesn't have a physical LED on the Numlock key so it's hard for me to know which mode it's in.

To reproduce:

1. Install Tellico (pacman -S tellico)
2. Create a new book database
3. Press Ctrl+I to launch the Tellico import dialog
4. Select ISBN from the dropdown if it's not already set
5. Type a couple digits in with the normal keyboard, not the numeric keypad
6. Press 4 on the numeric keypad. If it moves the cursor, press Numlock until it types a 4
7. Close the dialog
8. Repon the dialog by pressing Ctrl+I
9. Type 4 on the numeric keypad. Cursor won't move.
10. Type 12 on the regular keyboard
11. Type 4 on the numeric keypad. Cursor moves left one space because it was treated as left arrow.
12. Press Numlock once.
13. Type 4 on the numeric keypad. Cursor moves left one space because it was treated as left arrow.
14. Press Numlock one more time.
15. Type 4 on the numeric keypad. This time a 4 is typed into the search bar.

If you can't reproduce this behavior, then there's something idiosyncratic about my laptop and I'll need to investigate that further. But I suspect that what's happening is Tellico is trying to set Numlock to ON when the Ctrl+I dialog is launched, and Hyprland is behaving otherwise than what Tellico expects (perhaps treating that as a toggle rather than a "set to ON" command? Don't know, it's one possible explanation).

[vaxerski]

is it running in xwayland? I remember something about that.

[rmunn]

Sorry I missed this question two months ago. It's a QT app, so I tried with -platform wayland (native Wayland) and -platform xcb (which would use XWayland), and observed the same NumLock behavior both times (Tellico thinking NumLock is off when the rest of the system thinks it's on). I'll try to find the time to get more details, e.g. installing an OSD notification when I toggle NumLock on or off so I'll be certain about which state it should be in.

[rabiddoughnuts]

I have the same issue, in almost every app, I always have numlock on, because I NEVER use the other dumb inputs on it, especially since every keyboard already has arrow keys, why would I need another set? but I regularly have to turn off numlock, turn it back on, and then I can use it, but only until I press a keyboard key