https://bugs.winehq.org/show_bug.cgi?id=47513
Bug ID: 47513 Summary: mailing-list-patches breaks gamepad input Product: Wine-staging Version: 4.12.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: sashok.olen@gmail.com CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: ---
Created attachment 64902 --> https://bugs.winehq.org/attachment.cgi?id=64902 +tid,+pid,+plugplay,+hid,+hid_report,+hidp,+xinput,+dinput,+rawinput
With mailing-list-patches patchset, all of my games are unable to detect a gamepad and receive no input from it. If I build staging with it reverted, the issues disappears. Attaching log with +tid,+pid,+plugplay,+hid,+hid_report,+hidp,+xinput,+dinput,+rawinput debug channels.
https://bugs.winehq.org/show_bug.cgi?id=47513
--- Comment #1 from Alexandr Oleynikov sashok.olen@gmail.com --- Specifically, the breakage happened after this was commited: https://github.com/wine-staging/wine-staging/commit/5ed9211eabf3bac7f466cb5c...
https://bugs.winehq.org/show_bug.cgi?id=47513
--- Comment #2 from Zebediah Figura z.figura12@gmail.com --- Is it still broken if you run `wine wineboot -u` in the affected prefix? If so, can you please attach a log with the same channels plus +ntoskrnl?
https://bugs.winehq.org/show_bug.cgi?id=47513
Alexandr Oleynikov sashok.olen@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #64902|0 |1 is obsolete| |
--- Comment #3 from Alexandr Oleynikov sashok.olen@gmail.com --- Created attachment 64906 --> https://bugs.winehq.org/attachment.cgi?id=64906 +tid,+pid,+plugplay,+hid,+hid_report,+hidp,+xinput,+dinput,+rawinput,+ntoskrnl
wine wineboot -u did not fix it. I did however notice this in the output when running it: 0026:err:setupapi:SetupDefaultQueueCallbackW copy error 2 L"\\?\Z:\usr\share\wine\winebus.inf" -> L"C:\windows\inf\winebus.inf" Attaching log with +tid,+pid,+plugplay,+hid,+hid_report,+hidp,+xinput,+dinput,+rawinput,+ntoskrnl debug channels.
https://bugs.winehq.org/show_bug.cgi?id=47513
--- Comment #4 from Zebediah Figura z.figura12@gmail.com --- So there is not a winebus.inf present in your C:/windows/inf/ directory? That message implies it's trying to copy it from a packaged installation. How did you install Staging?
https://bugs.winehq.org/show_bug.cgi?id=47513
--- Comment #5 from Alexandr Oleynikov sashok.olen@gmail.com --- Nope, there is no such file there. And in the directory it tries to copy that file from the only files that have .inf extension are wine.inf and winehid.inf. I built and installed staging using TKG PKGBUILDS for Arch Linux. It should be pretty much identical to regular staging though as I disabled all the additional patches that it adds when testing this.
https://bugs.winehq.org/show_bug.cgi?id=47513
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED
--- Comment #6 from Zebediah Figura z.figura12@gmail.com --- If the package isn't installing winebus.inf, that sounds like a problem with the package. Inasmuch as there isn't an official Staging release with those patches, you might have to manually add it to the package script yourself.
https://bugs.winehq.org/show_bug.cgi?id=47513
--- Comment #7 from Alexandr Oleynikov sashok.olen@gmail.com --- I will report that to the package maintainer. However, this might not actually be the cause of the breakage. I've just created the /usr/share/wine/winebus.inf file myself (with these contents taken from the patch that adds it https://paste.ubuntu.com/p/rqwg2MDGSw/) and I still have no gamepad input. In that case, can this bug be reopened?
https://bugs.winehq.org/show_bug.cgi?id=47513
--- Comment #8 from Zebediah Figura z.figura12@gmail.com --- (In reply to Alexandr Oleynikov from comment #7)
I will report that to the package maintainer. However, this might not actually be the cause of the breakage. I've just created the /usr/share/wine/winebus.inf file myself (with these contents taken from the patch that adds it https://paste.ubuntu.com/p/rqwg2MDGSw/) and I still have no gamepad input. In that case, can this bug be reopened?
If that's still the case after rerunning wineboot, then yes. I'll have to see a new log in that case, though.
https://bugs.winehq.org/show_bug.cgi?id=47513
Alexandr Oleynikov sashok.olen@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #64906|0 |1 is obsolete| |
--- Comment #9 from Alexandr Oleynikov sashok.olen@gmail.com --- Created attachment 64907 --> https://bugs.winehq.org/attachment.cgi?id=64907 +tid,+pid,+plugplay,+hid,+hid_report,+hidp,+xinput,+dinput,+rawinput,+ntoskrnl
Here's a new log (after running wine wineboot -u)
https://bugs.winehq.org/show_bug.cgi?id=47513
--- Comment #10 from Zebediah Figura z.figura12@gmail.com --- It's not picking up the device in the registry, which suggests the prefix update didn't actually work. In a successful run one should see a key labeled (I think) HKLM/System/CurrentControlSet/Enum/ROOT/WINE/WINEBUS.
Can you please attach a log of running wineboot -u itself, with WINEDEBUG=+pid,+wineboot,+plugplay,+setupapi,+reg?
https://bugs.winehq.org/show_bug.cgi?id=47513
--- Comment #11 from Alexandr Oleynikov sashok.olen@gmail.com --- Created attachment 64908 --> https://bugs.winehq.org/attachment.cgi?id=64908 registry screenshot
I do actually have a key like that in the registry (see attached screenshot). Will attach wineboot log in the next message.
https://bugs.winehq.org/show_bug.cgi?id=47513
--- Comment #12 from Alexandr Oleynikov sashok.olen@gmail.com --- Created attachment 64909 --> https://bugs.winehq.org/attachment.cgi?id=64909 +pid,+wineboot,+plugplay,+setupapi,+reg
Log WINEDEBUG=+pid,+wineboot,+plugplay,+setupapi,+reg when running wine wineboot -u
https://bugs.winehq.org/show_bug.cgi?id=47513
--- Comment #13 from Alexandr Oleynikov sashok.olen@gmail.com --- Removing that key in the registry and then rerunning wineboot -u again actually seemed to have fixed that? What a weird bug.
https://bugs.winehq.org/show_bug.cgi?id=47513
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|NOTOURBUG |INVALID
--- Comment #14 from Zebediah Figura z.figura12@gmail.com --- (In reply to Alexandr Oleynikov from comment #13)
Removing that key in the registry and then rerunning wineboot -u again actually seemed to have fixed that? What a weird bug.
That is indeed quite strange, but I guess we'll call this fixed for now.
https://bugs.winehq.org/show_bug.cgi?id=47513
Tk ti3nou@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ti3nou@gmail.com
--- Comment #15 from Tk ti3nou@gmail.com --- Created attachment 64910 --> https://bugs.winehq.org/attachment.cgi?id=64910 Add winebus.sys to configure
It's not fixed, if I may say. The issue is that loader/winebus.inf is missing from configure, and as a result doesn't get installed.
https://bugs.winehq.org/show_bug.cgi?id=47513
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |FIXED
--- Comment #16 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- (In reply to Tk from comment #15)
Created attachment 64910 [details] Add winebus.sys to configure
It's not fixed, if I may say. The issue is that loader/winebus.inf is missing from configure, and as a result doesn't get installed.
Thanks for the update. Change committed.
https://bugs.winehq.org/show_bug.cgi?id=47513
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #17 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- Closing Fixed wine-staging.