[Bug 47332] New: supposedly 0003-ntdll-Fill-process-kernel-and-user-time.patch makes certain Blizzard games crash
https://bugs.winehq.org/show_bug.cgi?id=47332 Bug ID: 47332 Summary: supposedly 0003-ntdll-Fill-process-kernel-and-user-time.patch makes certain Blizzard games crash Product: Wine-staging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tempel.julian(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Report spin-off from here: https://bugs.winehq.org/show_bug.cgi?id=47265#c45 Commit 071fe01910b1360b8ea0e0ac9501b52baea2b720 is confirmed to make at least Heroes of the Storm and Starcraft 2 crash on launch. https://github.com/wine-staging/wine-staging/commit/071fe01910b1360b8ea0e0ac... I currently don't have a compiled build of this commit at hand, so anybody may feel free to provide logs. -- 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=47332 pattietreutel <katyaberezyaka(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katyaberezyaka(a)gmail.com -- 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=47332 --- Comment #1 from Zebediah Figura <z.figura12(a)gmail.com> --- Okay, let's try to clear this up somewhat. It would be nice to know what is meant by "071fe0191 makes games crash". It doesn't make sense to revert that directly, so I suspect what is meant is "071fe0191 on top of upstream 07e249e43 works, and 1b7ebd3bb on top of upstream 042e06256 doesn't." That can mean an error in rebasing, or it can mean a regression in upstream Wine. Bug 47265 was about the latter, which was pinpointed to 3e927c4ae by Andrew Wesie. That was effectively reverted by 13e11d3fc, which seems to have fixed the game for some people, but not for others. I would suggest, for anyone still having the issue after 13e11d3fc, to first try running `wine wineboot -u` in the affected prefix. If the bug still occurs after that, please reply here. -- 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=47332 --- Comment #2 from tempel.julian(a)gmail.com --- I might be mistaken, but I think the wine-tkg PKGBUILD which I use always pulls the latest commits of both wine and the -staging patchset. When I clamp it to -staging commit 071fe01910b1360b8ea0e0ac9501b52baea2b720, it doesn't crash. So I suppose this is a sign for a regression in -staging patchset, and not wine itself? Here is a log file. Clean prefix (HotS requires native d3dx11_42 and d3dcompiler_47) and turning off esync don't help. -- 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=47332 --- Comment #3 from tempel.julian(a)gmail.com --- Created attachment 64673 --> https://bugs.winehq.org/attachment.cgi?id=64673 wine log -- 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=47332 --- Comment #4 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to tempel.julian from comment #2)
I might be mistaken, but I think the wine-tkg PKGBUILD which I use always pulls the latest commits of both wine and the -staging patchset. When I clamp it to -staging commit 071fe01910b1360b8ea0e0ac9501b52baea2b720, it doesn't crash. So I suppose this is a sign for a regression in -staging patchset, and not wine itself?
Here is a log file. Clean prefix (HotS requires native d3dx11_42 and d3dcompiler_47) and turning off esync don't help.
What is it applying 071fe0191 on top of? Upstream 07e249e43 or upstream master? -- 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=47332 --- Comment #5 from tempel.julian(a)gmail.com --- In last_build_config.log, it says Wine (plain) version: 4.9.r378.g48a74277f5 Using wine-staging patchset (version 4.9.r15.g5681cd54) So, "riddle" solved, I guess. -- 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=47332 --- Comment #6 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to tempel.julian from comment #5)
In last_build_config.log, it says Wine (plain) version: 4.9.r378.g48a74277f5 Using wine-staging patchset (version 4.9.r15.g5681cd54)
So, "riddle" solved, I guess.
This is a working build or a non-working build? -- 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=47332 --- Comment #7 from tempel.julian(a)gmail.com --- (In reply to Zebediah Figura from comment #6)
This is a working build or a non-working build? Crashing build. I'm going to recompile with -staging clamped to 071fe01910b1360b8ea0e0ac9501b52baea2b720 (which doesn't crash) and inform you if it's based on wine git-master as well.
-- 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=47332 --- Comment #8 from tempel.julian(a)gmail.com --- With that clamp, it's based on 4.8.r163.g07e249e431, so not wine git-master. As described in the previous bug ticket, applying this patch helped to make -staging work again, but it seems it needs rebasing for recent commits to be applicable again? https://bugs.winehq.org/attachment.cgi?id=64567 -- 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=47332 --- Comment #9 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to tempel.julian from comment #8)
With that clamp, it's based on 4.8.r163.g07e249e431, so not wine git-master.
As described in the previous bug ticket, applying this patch helped to make -staging work again, but it seems it needs rebasing for recent commits to be applicable again? https://bugs.winehq.org/attachment.cgi?id=64567
The problem is that 13e11d3fc should do effectively the same thing. The only difference is that now kernel32 doesn't call into ntdll. I'd guess that the anticheat engine is trying to validate that kernel32 does call into ntdll, but it's still confusing that it works for some people and not others. I'd really like to see the condition narrowed down first. -- 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=47332 --- Comment #10 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- Wine-TKG was carrying a patch[1] that was causing broken behaviour in WoW at least. TKG has updated his package, so you might want to try again. Also, custom wine versions aren't accepted when reporting bugs, so always test with official packages before filing a bug. [1]https://github.com/Tk-Glitch/PKGBUILDS/blob/master/wine-tkg-git/wine-tkg-pat... -- 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=47332 --- Comment #11 from tempel.julian(a)gmail.com --- Thanks, but of course I already turned off applying that custom patch (and any other) before. -- 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=47332 tempel.julian(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #12 from tempel.julian(a)gmail.com --- But only the first time I was trying to bisect, and not the subsequent ones (meaning not with newer commits in master). It's fixed with 4.10 without tkg's use_clock_monotonic.patch, thanks for your help and sorry for the inconvenience. -- 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=47332 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED Resolution|FIXED |INVALID --- Comment #13 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- Closing as INVALID instead. -- 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)
-
wine-bugs＠winehq.org