https://bugs.winehq.org/show_bug.cgi?id=48322 --- Comment #18 from Sveinar Søpler <cybermax(a)dexter.no> --- (In reply to Luca Boccassi from comment #17)
Rather than bisecting the patchsets, I'm thinking it might be easier to bisect the staging git tree itself, with 4.17 being "good" and 4.18 being "bad"? In _theory_, unless intermittent breakages were added and then removed, it should be doable as both versions work with WoW.
I am not sure it is "as easy as that", but there was some strangeness that started happening with 4.16 for some games aswell. I am sure this is not ONLY WoW with this problem tho. This is a bug posted, now marked as solved: https://bugs.winehq.org/show_bug.cgi?id=47834 This is what i gather as something that caused problems aswell: https://github.com/wine-staging/wine-staging/commit/0c7512f5f53deb168d3508bd... And it was disabled pre 4.18 launch: https://github.com/wine-staging/wine-staging/commit/5b066d6aed7fd90c0be0a2a1... But i see no tests mentioning WoW in this particular context. Maybe do some comparison of staging-4.17 vs. 4.17 with these patches enabled/disabled? I think there was changes to the wine tree between 4.17 and 4.18 that prompted the need to update this user32-rawinput patchset tho, but it is way beyond me to figure out the ins and outs of this. We are playing the "blame-game" here: Is it wine, or is it staging :) -- 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.