http://bugs.winehq.org/show_bug.cgi?id=60059 Kagetaro078 <kagetaro1986@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kagetaro1986@gmail.com --- Comment #14 from Kagetaro078 <kagetaro1986@gmail.com> --- Created attachment 82308 --> http://bugs.winehq.org/attachment.cgi?id=82308 Test program (dinputtest.c), scripts and logs (NumLock on/off, with/without WH_KEYBOARD_LL hook) I can confirm this with Wine 11.19 and with current master (a15ee2cc, 2026-10-09: dlls/winex11.drv/keyboard.c is unchanged since 11.19), on Ubuntu 26.04.1 (KDE Plasma 6, Wayland session, Wine on XWayland) and in a plain Xvfb + openbox session. Besides the oscillating toggle state, applications also receive the fake lock key itself before every key: WM_KEYDOWN VK_NUMLOCK, and DIK_NUMLOCK from DirectInput. Plasma turns NumLock on at login, so it is on in X and off in Wine whenever a program starts. A game I use beeps on every key in its key binding screen because it gets NumLock first. Numbers from a small standalone test (attached dinputtest.c: window + DirectInput 8 keyboard, -hook installs a pass-through WH_KEYBOARD_LL hook; 14 keys sent through XTEST, no input method): - NumLock in X / hook: Wine 11.19: VK_NUMLOCK / DIK_NUMLOCK / toggle at end - on / hook: 29 / 28 / 0 (64-bit: 29 / 28 / 0) - on / no hook: 1 / 1 / 1 (64-bit: 0 / 0 / 1) - off / hook: 0 / 0 / 0 (64-bit: 0 / 0 / 0) - off / no hook: 0 / 0 / 0 (64-bit: 0 / 0 / 0) So with the hook the state is still wrong after 14 keys, and 29 fake NumLock key downs were delivered. On Windows 11 the same test with NumLock on (keys injected with SendInput) gives 0 / 0 and toggle 1, with and without the hook (logs in the archive). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.