Hello,
I am reporting a problem, hoping this is known and has a simple solution.
I am using Wine (staging) on Debian 12, making music with REAPER, some native plugins and Yabridge for some other Windows VST plugins.
Since updating to Wine-staging 9.19 - and 9.20 also - wine is no longer starting at all, reverting to Wine 9.18 staging all is good.
Even the "wine explorer", "wine uninstaller" or "winecfg" commands from a terminal window simply hang.
My Debian 12 installation is on an external drive, and it runs fine - wine included - on another PC
I found today by accident that if I unplug my Huion Kamvas Pro 13 tablet (for which I never had to install anything to have it detected and used as second monitor) Wine returns working.
I also tried to install official Huion drivers and, after rebooting, all is the same: just having the tablet connected prevents Wine from starting.
Is there something I can do or test, other than getting back to Wine pre 9.19 or not connecting the tablet, to solve this problem?
Thanks in advance,
Mario
Issue (conflict?) with Wine-staging (from 9.18) and Huion tablet
Re: Issue (conflict?) with Wine-staging (from 9.18) and Huion tablet
Additional info: I don't need to actually detach the device, simply telling Debian to not use it as additional display is enough to be able to run Wine correctly.
These are the errors I get when trying a simple "wine explorer" command...
0080:fixme:hid:build_joystick_report_descriptor More than 8 absolute axes found, ignoring.
0080:fixme:wineusb:query_id Unhandled ID query type 0x5.
0080:fixme:wineusb:query_id Unhandled ID query type 0x5.
0080:fixme:wineusb:query_id Unhandled ID query type 0x5.
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: 0xa200003
Serial number of failed request: 346
Current serial number in output stream: 346
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: 0xb200004
Serial number of failed request: 293
Current serial number in output stream: 293
Thanks,
Mario
These are the errors I get when trying a simple "wine explorer" command...
0080:fixme:hid:build_joystick_report_descriptor More than 8 absolute axes found, ignoring.
0080:fixme:wineusb:query_id Unhandled ID query type 0x5.
0080:fixme:wineusb:query_id Unhandled ID query type 0x5.
0080:fixme:wineusb:query_id Unhandled ID query type 0x5.
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: 0xa200003
Serial number of failed request: 346
Current serial number in output stream: 346
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: 0xb200004
Serial number of failed request: 293
Current serial number in output stream: 293
Thanks,
Mario
Re: Issue (conflict?) with Wine-staging (from 9.18) and Huion tablet
I can reproduce this failure whenever I switch to a different X11 session virtual console on linux, using Control+Alt+F2 etc. When I return to the original session where the Wine application was running, I find that the process is dead and something like this is printed:
No tablet device is connected when it happens. I am using a mouse and keyboard.
The fact that it looks like an input device error and triggers when I switch VCs suggests to me that Wine no longer gracefully handles temporary loss of permission to an input device.
This regression is problematic for those of us who switch VCs a lot, as it causes data loss in regular applications and progress loss in games.
Disclosure: I have have not yet tested with a pure wine-staging build. I'm currently using wine-staging 10 builds for the Bottles project, which have additional patches. For example, those published here: https://github.com/Kron4ek/Wine-Builds
Code: Select all
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: 0xabc
Serial number of failed request: 1234
Current serial number in output stream: 1234
The fact that it looks like an input device error and triggers when I switch VCs suggests to me that Wine no longer gracefully handles temporary loss of permission to an input device.
This regression is problematic for those of us who switch VCs a lot, as it causes data loss in regular applications and progress loss in games.
Disclosure: I have have not yet tested with a pure wine-staging build. I'm currently using wine-staging 10 builds for the Bottles project, which have additional patches. For example, those published here: https://github.com/Kron4ek/Wine-Builds
Re: Issue (conflict?) with Wine-staging (from 9.18) and Huion tablet
Update:
I have reproduced the crash on VC switch using official winehq builds. The bug is present in wine-staging 9.4 and later, but not wine-stable or wine-devel.
Upstream bug reports:
https://bugs.winehq.org/show_bug.cgi?id=57808
https://bugs.winehq.org/show_bug.cgi?id=57123
I have reproduced the crash on VC switch using official winehq builds. The bug is present in wine-staging 9.4 and later, but not wine-stable or wine-devel.
Upstream bug reports:
https://bugs.winehq.org/show_bug.cgi?id=57808
https://bugs.winehq.org/show_bug.cgi?id=57123