[Bug 57958] New: Caps lock issue when holding Caps lock with other key and Caps lock state was already on
https://bugs.winehq.org/show_bug.cgi?id=57958 Bug ID: 57958 Summary: Caps lock issue when holding Caps lock with other key and Caps lock state was already on Product: Wine Version: 10.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: daniel.gaba(a)protonmail.com Distribution: --- Hello, most of the time when holding Caps lock with another button game will register double click first on CAPS LOCK. In "Arma 3" and in "Arma: Reforger" CapsLock is used as push to talk button for radio and you are often holding it alongside other buttons. How to reproduce: 1. Caps lock state need to be on. 2. Hold other key, for example W for walking forward 3. Hold CAPS LOCK 4. In Arma 3 it will start broadcasting for ms and stop and after 1s it will start broadcasting again. In Arma: Reforger this will toggle between Squad <-> Platoon radio instead because it detected double click on Caps Lock. Game will ignore you are still holding caps lock. There is small chance that bug will not trigger. There is also possibility that game may mistakenly detect that you are still holding the Caps Lock key after releasing it, causing it to continue broadcasting until you press it again. I don't know how to reproduce this one. This is very common issue for Arma players on Linux. OS: Opensuse Tumbleweed Kernel version: 6.13.6-1-default KDE plasma Version: 6.3.2 Wayland Wine 10.3 but issue also happens on Proton 7,8 and 9 I tested it also with wayland driver and I was not able to reproduce it. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57958 --- Comment #1 from DanielGGGG <daniel.gaba(a)protonmail.com> --- Created attachment 79444 --> http://bugs.winehq.org/attachment.cgi?id=79444 Keyboard debug I am not sure if this is usefull. Full debug output in attachment I run notepad via wine 10.16 WINEDEBUG=+key,+keyboard ./wine notepad &>> /tmp/output2.log 1. Caps lock state is off 2. Press and hold W button 3. Press and hold Caps Lock button 4. Release Caps lock button 5. Release W button On pressing CAPS LOCK generated input 00f8:trace:key:X11DRV_send_keyboard_input hwnd 0x1006e vkey=0014 scan=003a flags=0000 And while releasing CAPS LOCK it generated 00f8:trace:key:X11DRV_send_keyboard_input hwnd 0x1006e vkey=0014 scan=003a flags=0002 In this case there is no issue. 1. Caps lock state is on 2. Press and hold C button 3. Press and hold Caps Lock button 4. Release Caps lock button 5. Release C button In this case on pressing caps lock it generated 1 input 00f8:trace:key:X11DRV_send_keyboard_input hwnd 0x1006e vkey=0014 scan=003a flags=0000 and after few lines it generated 2 more caps lock inputs 00f8:trace:key:X11DRV_send_keyboard_input hwnd 0x1006e vkey=0014 scan=003a flags=0002 00f8:trace:key:X11DRV_send_keyboard_input hwnd 0x1006e vkey=0014 scan=003a flags=0000 and on Caps lock key release it generate Caps lock input X11DRV_send_keyboard_input hwnd 0x1006e vkey=0014 scan=003a flags=0002 and after few lines it generate 2 more caps lock input 00f8:trace:key:X11DRV_send_keyboard_input hwnd 0x1006e vkey=0014 scan=003a flags=0000 00f8:trace:key:X11DRV_send_keyboard_input hwnd 0x1006e vkey=0014 scan=003a flags=0002 This cause issue in games that have use CAPS LOCK button. I also saw simillar bug report where I also posted my findings. https://bugs.winehq.org/show_bug.cgi?id=58371 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57958 DanielGGGG <daniel.gaba@protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|10.3 |10.20 --- Comment #2 from DanielGGGG <daniel.gaba@protonmail.com> --- bump -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57958 DanielGGGG <daniel.gaba@protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|10.20 |11.0 --- Comment #3 from DanielGGGG <daniel.gaba@protonmail.com> --- Still happening with wine 11.0 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57958 Maotong Zhang <zmtong1988@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zmtong1988@gmail.com --- Comment #4 from Maotong Zhang <zmtong1988@gmail.com> --- The current design of the adjust_lock_state() function requires sending data twice to synchronize the key state. What problems are there when Caps Lock is in the enabled state now? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57958 --- Comment #5 from DanielGGGG <daniel.gaba@protonmail.com> --- In Arma 3 holding Caps lock is used as push to talk when you hold it but when you do double tap it will toggle your microphone on and you can talk until you double tap Caps lock again. This can be annoying for people you play with if your microphone is always on and you don't notice it. In Arma Reforger is holding Caps lock is also used as push to talk but double tap switch radio channels from Squad <-> Platoon In another bug report someone mentioned issue in Battlefield 2 https://bugs.winehq.org/show_bug.cgi?id=58371 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57958 --- Comment #6 from Maotong Zhang <zmtong1988@gmail.com> --- Could you test if the issue still occurs after uninstalling the input method? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57958 --- Comment #7 from DanielGGGG <daniel.gaba@protonmail.com> --- I don't understand what you mean by "uninstalling the input method". -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57958 --- Comment #8 from Maotong Zhang <zmtong1988@gmail.com> --- (In reply to DanielGGGG from comment #7)
I don't understand what you mean by "uninstalling the input method".
No need to test. This two-step state needs to be preserved, otherwise there will be a toggle issue. If you’re only toggling Caps Lock, you can add a hook to check it. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57958 --- Comment #9 from DanielGGGG <daniel.gaba@protonmail.com> --- Wayland backend doesn't have this issue only x11 backend. Maybe same synchronization method could be implemented on x11 backend? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57958 imccluney@comcast.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |imccluney@comcast.net --- Comment #10 from imccluney@comcast.net --- See https://gitlab.winehq.org/wine/wine/-/merge_requests/11315. It includes a patch for a problem very similar to what you described. I created the patch after I ran into issues with Caps Lock while testing Star Wars Episode I: Racer the other day. In this case, Caps Lock is supposed to cycle through different map styles of the current track, but sometimes Wine it would register two presses if another key is then pressed. Now Wine adjusts the lock states of Caps Lock, Num Lock, and Scroll Lock only when the lock states on the keyboard have actually been changed outside the program, consistent with the comments in keyboard.c. It can be confirmed that the patch works by running the patched Wine with WINEDEBUG=trace+keyboard in Bash and testing a program such as Notepad++, which is what I used. -- 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.
participants (2)
-
WineHQ Bugzilla -
WineHQ Bugzilla