https://bugs.winehq.org/show_bug.cgi?id=57524
Bug ID: 57524 Summary: Commit c9592bae7f475c1b208de0a72ed29e94e3017094 breaks VKB Gladiator support Product: Wine Version: 10.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: dixonte+winehq@stc-networks.com Distribution: ---
Created attachment 77574 --> https://bugs.winehq.org/attachment.cgi?id=77574 Combined output from running 'wine control' before and after c9592bae7
I tested 10.0rc1 and found that neither of my VKB Gladiator sticks, nor my Fanatec pedals, would show up in wine control or in games. Upon further investigation it seems that commit c9592bae7f475c1b208de0a72ed29e94e3017094 is causing the issue.
Interestingly, if I unplug the sticks and wait a while before reopening wine control, the Fanatec pedals will show up. But if the sticks are plugged in, no controllers show up.
I've attached the console output from running wine control with the sticks and pedals connected, from builds of wine-staging as at commit 9b1381fc785a3ff8c3cc82e7339ebe29d12003ed (the commit immediately before, where the sticks are both visible and so are the pedals), and as at commit c9592bae7f475c1b208de0a72ed29e94e3017094.
The issue seems to be related to using hidraw, as disabling it will allow all devices to show up.
As an aside, I was testing 10.0rc1 originally because in 9.22 the sticks will stop working after a random period of time (between 10 minutes and multiple hours). I wouldn't be surprised if this was somehow related but I'm not sure what I can do to debug that issue.
https://bugs.winehq.org/show_bug.cgi?id=57524
T E Dixon dixonte+winehq@stc-networks.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Commit |Commit |c9592bae7f475c1b208de0a72ed |c9592bae7f475c1b208de0a72ed |29e94e3017094 breaks VKB |29e94e3017094 breaks VKB |Gladiator support |Gladiator HIDRAW support
https://bugs.winehq.org/show_bug.cgi?id=57524
Rémi Bernon rbernon@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rbernon@codeweavers.com
--- Comment #1 from Rémi Bernon rbernon@codeweavers.com --- Thanks for the report, could you make a log with WINEDEBUG=+hid,+dinput?
https://bugs.winehq.org/show_bug.cgi?id=57524
Rémi Bernon rbernon@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |c9592bae7f475c1b208de0a72ed | |29e94e3017094 Keywords| |regression
https://bugs.winehq.org/show_bug.cgi?id=57524
--- Comment #2 from T E Dixon dixonte+winehq@stc-networks.com --- Created attachment 77575 --> https://bugs.winehq.org/attachment.cgi?id=77575 Output with WINEDEBUG=+hid,+dinput from commit c9592bae7f475c1b208de0a72ed29e94e3017094
Here it is. Would you like the same from commit 9b1381fc785a3ff8c3cc82e7339ebe29d12003ed as well? I'll have to rebuild it first.
https://bugs.winehq.org/show_bug.cgi?id=57524
T E Dixon dixonte+winehq@stc-networks.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Gentoo
https://bugs.winehq.org/show_bug.cgi?id=57524
--- Comment #3 from Rémi Bernon rbernon@codeweavers.com --- Created attachment 77577 --> https://bugs.winehq.org/attachment.cgi?id=77577 possible fix
This probably helps? I missed that we could receive reports before the device has been started from the NT point of view, also accessing the device desc probably needed to be done within the CS.
https://bugs.winehq.org/show_bug.cgi?id=57524
--- Comment #4 from T E Dixon dixonte+winehq@stc-networks.com --- (In reply to Rémi Bernon from comment #3)
Created attachment 77577 [details] possible fix
This probably helps? I missed that we could receive reports before the device has been started from the NT point of view, also accessing the device desc probably needed to be done within the CS.
I've applied this patch to 10.0rc1, and it seems to resolve my issue. Thanks!
Any suggestions on how to debug the random disconnect issue that may or may not be related? It happens after a random time period and seems to require a restart of wineserver to resolve. I'll make another bug entry for that, of course.
https://bugs.winehq.org/show_bug.cgi?id=57524
--- Comment #5 from Rémi Bernon rbernon@codeweavers.com --- Hmm, hard to say for sure. We usually rely on traces but for long runs it can become a bit unwieldy. Something like WINEDEBUG=+hid,+plugplay,+dinput,+rawinput maybe could tell. You can add +server if you want to trace wineserver requests, this will be absolutely massive though.
https://bugs.winehq.org/show_bug.cgi?id=57524
--- Comment #6 from T E Dixon dixonte+winehq@stc-networks.com --- (In reply to Rémi Bernon from comment #5)
Hmm, hard to say for sure. We usually rely on traces but for long runs it can become a bit unwieldy. Something like WINEDEBUG=+hid,+plugplay,+dinput,+rawinput maybe could tell. You can add +server if you want to trace wineserver requests, this will be absolutely massive though.
Maybe I'll get lucky and be able to reproduce it without a game running. Thanks, I'll see what I can do with that, but it'll likely take me some time.
https://bugs.winehq.org/show_bug.cgi?id=57524
Rémi Bernon rbernon@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |a70ac0960de3645bb12ea4ca24c | |cdf4d99d6867e Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #7 from Rémi Bernon rbernon@codeweavers.com --- Should be fixed with a70ac0960de3645bb12ea4ca24ccdf4d99d6867e.
https://bugs.winehq.org/show_bug.cgi?id=57524
--- Comment #8 from T E Dixon dixonte+winehq@stc-networks.com --- (In reply to Rémi Bernon from comment #7)
Should be fixed with a70ac0960de3645bb12ea4ca24ccdf4d99d6867e.
A brief test on my end suggests this is the case.
https://bugs.winehq.org/show_bug.cgi?id=57524
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 10.0-rc2.