[Bug 56030] New: Left 4 Dead 2 Version 2.2.0.0 Keyboard / Mouse inputs not properly recognized.
https://bugs.winehq.org/show_bug.cgi?id=56030 Bug ID: 56030 Summary: Left 4 Dead 2 Version 2.2.0.0 Keyboard / Mouse inputs not properly recognized. Product: Wine Version: 9.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hibbsncc1701(a)gmail.com Distribution: --- With Wine-9.0-rc1 Left 4 Dead 2 Version 2.2.0.0 does not properly recognize keyboard / mouse inputs. It seems that in some cases key state changes are ignored. I.e. The key "gets stuck" in the last read state. Causing behaviors like the player not moving despite any of the WSAD keys being held down, continuing to move in a single direction, or the player constantly firing / reloading / switching a weapon (similar to a turbo controller) despite the mouse having only been clicked / scrolled once (and the mouse not having a turbo mode). This seems to happen about once every ~15-20 seconds. Making the game unplayable. It also seems that the only way for the key to be "unstuck" is to change it's state while the game is getting input. For example, If the player is stuck firing a weapon, the player needs to manually fire the weapon again (Mouse1 by default) and release the key before the game ignores input again to make the weapon stop firing. Simply doing nothing will *not* fix the key state as far as the game is concerned. It should be noted that mouse movement does not seem to be affected by this. As the player can still use mouse look normally despite the above behaviors. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56030 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick(a)piezo-forte.be --- Comment #1 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, I wonder if the underlying cause is similar to bug 33296 that has hit me recently. If your system happens to be using ibus, can you try to temporarily disable it and check the issue? It can be switched off/on while playing by opening a terminal in the background, switching to it and running 'ibus exit' or 'ibus start'. The effect, if any, should be immediately noticeable in game. Regards. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56030 --- Comment #2 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, On second though, ibus should not affect mouse buttons, so this won't probably work. Regards. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56030 --- Comment #3 from Patrick Hibbs <hibbsncc1701(a)gmail.com> --- (In reply to Olivier F. R. Dierick from comment #2)
Hello,
On second though, ibus should not affect mouse buttons, so this won't probably work.
Regards.
Hello, Strangely enough it does. Exiting ibus more or less fixes the issue, even the mouse button input, but for some reason restarting ibus while the game is still running *doesn't* cause the issue to occur again. Even weirder is that even changing the selected ibus input method after exiting and restarting ibus still doesn't cause the issue to reoccur. The only way to get the issue to reoccur again is to end the current desktop session (logout) and start a new one. (Re-login.) So although ibus seems to have something to do with it, ibus itself is not the direct cause of the issue. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56030 --- Comment #4 from Patrick Hibbs <hibbsncc1701(a)gmail.com> --- (In reply to Patrick Hibbs from comment #3)
The only way to get the issue to reoccur again is to end the current desktop session (logout) and start a new one. (Re-login.) So although ibus seems to have something to do with it, ibus itself is not the direct cause of the issue.
To clarify: logout means end the current X11 desktop session. Exiting wine and restarting it doesn't cause the issue to reoccur after exiting and restarting ibus. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56030 --- Comment #5 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, My Desktop Environment on Debian 12 is gnome-shell 43.9. While reading about ibus, I saw that it's the default input-method of gnome-shell. I don't have any other input-method installed, so maybe it's picking it up automatically when I restart ibus. What is your DE? Regards. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56030 --- Comment #6 from Patrick Hibbs <hibbsncc1701(a)gmail.com> --- (In reply to Olivier F. R. Dierick from comment #5)
Hello,
My Desktop Environment on Debian 12 is gnome-shell 43.9. While reading about ibus, I saw that it's the default input-method of gnome-shell. I don't have any other input-method installed, so maybe it's picking it up automatically when I restart ibus.
What is your DE?
Regards.
I use Xfce 4.18, same distro. In my case, I installed ibus manually. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56030 --- Comment #7 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, I searched the web for information about disabling ibus for specific applications and found this: https://bbs.archlinux.org/viewtopic.php?id=142307 Then here is what I did: Made sure that the other workarounds were removed; Opened a new terminal; ran 'export' to check for the existence of those variables (I only found XMODIFIERS="@im=ibus"); ran 'unset XMODIFIERS'; Launched the application with the usual wine command; The issue wasn't present. The advantage is that ibus stays available to other applications while playing. Regards. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=56030 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=57121 -- 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 (1)
-
WineHQ Bugzilla