[Bug 58485] New: wine causes constant resets of USB-connection to keyboard.
http://bugs.winehq.org/show_bug.cgi?id=58485 Bug ID: 58485 Summary: wine causes constant resets of USB-connection to keyboard. Product: Wine Version: 10.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: roidal(a)googlemail.com Distribution: --- Created attachment 78936 --> http://bugs.winehq.org/attachment.cgi?id=78936 usb-errors After switching to a new Keyboard (be quiet! Light Mount Silent Tactile) the USB-connection is reseted once every second while wine is running. output from journalctl: kernel: usb 7-1.1: reset full-speed USB device number 5 using xhci_hcd This makes the keyboard unusable (for all applications not just wine) since key-events are not transmitted reliably anymore. At the moment the wine/windows-application is closed, the keyboard works fine again. There are some errors printed out from the hid-component (see atached stdout.txt). OS: Fedora 42 wine: 10.11-staging (from the wine-repos) mainboard: Gigabyte B650 Gaming X AX V2 -- 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=58485 Chiitoo <chiitoo(a)gentoo.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chiitoo(a)gentoo.org -- 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=58485 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|hid |-unknown Keywords| |hardware --- Comment #1 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Does the same thing occur with vanilla, non-staging Wine? -- 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=58485 --- Comment #2 from roidal(a)googlemail.com --- Yes, problem is the same with wine-stable-10.0(In reply to Ken Sharp from comment #1)
Does the same thing occur with vanilla, non-staging Wine?
Yes, same problem with wine-stable-10.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=58485 roidal(a)googlemail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #78936|0 |1 is obsolete| | --- Comment #3 from roidal(a)googlemail.com --- Created attachment 78942 --> http://bugs.winehq.org/attachment.cgi?id=78942 output with WINEDEBUG='trace+hid' Attach wine-output with trace enabled. -- 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=58485 --- Comment #4 from roidal(a)googlemail.com --- Created attachment 78943 --> http://bugs.winehq.org/attachment.cgi?id=78943 debug-output of xhci_hcd module Attach debug-output of the xhci_hcd module. -- 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=58485 roidal(a)googlemail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #78942|0 |1 is obsolete| | --- Comment #5 from roidal(a)googlemail.com --- Created attachment 78944 --> http://bugs.winehq.org/attachment.cgi?id=78944 output with WINEDEBUG='trace+hid' Accidentally uploaded the log from an older wine-version. Updated. -- 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=58485 roidal(a)googlemail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #6 from roidal(a)googlemail.com --- Seems like this is an HW-issue. The keyboard expose multiple HID-interfaces, but whenever a specific one of them is accessed via /dev/hidraw* it does not only seem to report wrong data back, but also crash. So i believe this bugreport can be closed. -- 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=58485 PseudoResonance <1702d92e-73ad-4b96-a6bc-b9853a369f90@otake.pw> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |1702d92e-73ad-4b96-a6bc-b98 | |53a369f90@otake.pw --- Comment #8 from PseudoResonance <1702d92e-73ad-4b96-a6bc-b9853a369f90@otake.pw> --- Can this be reopened? I appear to be having the same issue with (I believe) an internal USB keyboard in my laptop. Maybe it's an issue with the hardware design, but I also wonder if it's exhibiting a flaw in how WINE handles USB devices or something? I apologize for my lack of knowledge of WINE though, perhaps I am making an incorrect assumption as to how it handles USB. In my case, it's not as disruptive, however the resets every second coincide with significant stutter in games. -- 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=58485 --- Comment #9 from PseudoResonance <1702d92e-73ad-4b96-a6bc-b9853a369f90@otake.pw> --- Created attachment 79996 --> http://bugs.winehq.org/attachment.cgi?id=79996 WINEDEBUG='trace+hid' output Lenovo keyboard -- 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=58485 --- Comment #10 from PseudoResonance <1702d92e-73ad-4b96-a6bc-b9853a369f90@otake.pw> --- Created attachment 79997 --> http://bugs.winehq.org/attachment.cgi?id=79997 xhci.c debug log Lenovo keyboard -- 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=58485 --- Comment #11 from PseudoResonance <1702d92e-73ad-4b96-a6bc-b9853a369f90@otake.pw> --- Created attachment 79998 --> http://bugs.winehq.org/attachment.cgi?id=79998 'lsusb -v' Lenovo keyboard This 048d:c965 Integrated Technology Express, Inc. ITE Device appears to be the internal USB device associated with the keyboard and some other parts in Lenovo Legion 5 Pro 2021 laptops. -- 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=58485 --- Comment #12 from roidal@googlemail.com --- Can you check if the files /dev/hidraw* are user-accessible? On Fedora they are usually only read-, and writeable, for root, but some rpm's might change that to be accessible for everyone. If you remove the rights for your user to access these files, wine will not try to access them, which might be a workaround. -- 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=58485 --- Comment #13 from PseudoResonance <1702d92e-73ad-4b96-a6bc-b9853a369f90@otake.pw> --- I'm on EndeavourOS and /dev/hidraw0-3 are "crw-rw----+ root:root", whereas 4-6 are "crw------- root:root". Checking the ACLs, 0-3 give my user rw access. Not sure why... "setfacl -b /dev/hidraw3" does seem to fix the constant USB resets though, and additionally has fixed the awful stutter I was getting. Thanks for the tip! I do wonder why the ACLs are there and what the real issue is though. -- 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