[Bug 57123] New: Wine crashes when input devices are plugged / unplugged
https://bugs.winehq.org/show_bug.cgi?id=57123 Bug ID: 57123 Summary: Wine crashes when input devices are plugged / unplugged Product: Wine-staging Version: 9.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: germanapps(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- When I plug or unplug my mouse (or connect / disconnect my bluetooth mouse, it doesn't matter), wine always crash regardless of the running application. The bug has developed gradually. First version that crashes only on unplugging was 9.4. Since version 9.11 wine crashes on both plugging and unplugging. Tests were done by creating a completely new prefix for each tested version. The error message wine prints into console: X Error of failed request: XI_BadDevice (invalid Device parameter) Major opcode of failed request: 131 (XInputExtension) X Error of failed request: XI_BadDevice (invalid Device parameter) Major opcode of failed request: 131 (XInputExtension) Minor opcode of failed request: 3 (X_OpenDevice) Device id in failed request: 0x7600001 Serial number of failed request: 262 Current serial number in output stream: 262 Minor opcode of failed request: 3 (X_OpenDevice) Device id in failed request: 0x8200001 Serial number of failed request: 238 Current serial number in output stream: 238 The last version without the bug is 9.3. -- 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=57123 --- Comment #1 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Does it occur in vanilla Wine? Please attach the full console output. A regression test is also needed. https://wiki.winehq.org/Regression_Testing -- 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=57123 --- Comment #2 from Herman Tafintsev <germanapps(a)gmail.com> --- (In reply to Ken Sharp from comment #1)
Does it occur in vanilla Wine?
Please attach the full console output.
A regression test is also needed. https://wiki.winehq.org/Regression_Testing
Well, it's a vanilla Wine. I don't use PlayOnLinux, Lutris or some other tools or wine builds. If by vanilla you mean wine-stable, then it probably doesn't, since it uses 9.0 version. I can still test it, if needed. Full console output doesn't have anything out of the ordinary, except for the posted bit. Should I try to capture logs with some special WINEDEBUG flags? If yes, then tell me which flags and i'll do 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.
https://bugs.winehq.org/show_bug.cgi?id=57123 --- Comment #3 from Zeb Figura <z.figura12(a)gmail.com> --- The request is to test in upstream, non-staging wine, but the development branch (not stable), sometimes packaged as "wine-devel" or something similar. -- 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=57123 --- Comment #4 from Herman Tafintsev <germanapps(a)gmail.com> --- (In reply to Zeb Figura from comment #3)
The request is to test in upstream, non-staging wine, but the development branch (not stable), sometimes packaged as "wine-devel" or something similar.
wine-devel 9.4, 9.15, 9.16 -- no bug in these versions. It appears one of the wine-staging patches introduced this bug. -- 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