[Bug 60094] New: Proton crashes on game launch, error refers to wintrust.dll
http://bugs.winehq.org/show_bug.cgi?id=60094 Bug ID: 60094 Summary: Proton crashes on game launch, error refers to wintrust.dll Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wintrust Assignee: wine-bugs@list.winehq.org Reporter: thegeekno72@gmail.com Target Milestone: --- Distribution: --- Hello everyone, I am but a user, rather fresh to Linux, even more so to WINE and subsequent projects based on it; I just want my game to work but according to the person who parsed through my proton logs for me, `wintrust.dll` was in disagreement with that today. With much respect to your work, I don't understand any of it though I do know I'd like to see it fixed whenever someone will be available to work on this issue; if you need further logs or testing done on my end, I know how to follow instructions, which is how we eventually got the game working with a tweaked wintrust -see link at the bottom- and would like to see this work natively without tweaks. Best regards, Geek https://github.com/Etaash-mathamsetty/wine-valve/compare/8316bc546bd6f82f2b1... -- 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.
http://bugs.winehq.org/show_bug.cgi?id=60094 --- Comment #1 from TheGeekn°72 <thegeekno72@gmail.com> --- Created attachment 81628 --> http://bugs.winehq.org/attachment.cgi?id=81628 Proton logs relevant mention : `WTHelperGetProvCertFromChain (0000000000000000 0)` -- 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.
http://bugs.winehq.org/show_bug.cgi?id=60094 --- Comment #2 from TheGeekn°72 <thegeekno72@gmail.com> --- Comment on attachment 81628 --> http://bugs.winehq.org/attachment.cgi?id=81628 Proton logs relevant mention : `WTHelperGetProvCertFromChain (0000000000000000 0)` -- 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.
http://bugs.winehq.org/show_bug.cgi?id=60094 Stian Low <wineryyyyy@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wineryyyyy@gmail.com --- Comment #3 from Stian Low <wineryyyyy@gmail.com> --- (In reply to TheGeekn°72 from comment #0)
Hello everyone, I am but a user, rather fresh to Linux, even more so to WINE
Welcome to Wine and Linux and liberation.
I just want my game to work but according to the person who parsed through my proton logs for me, `wintrust.dll` was in disagreement with that today.
Wine has a staging repo that seems to have already worked around this bug many years ago: - https://gitlab.winehq.org/wine/wine-staging/-/blob/master/patches/wintrust-W... Staging patches are usually considered hacks as workarounds until more difficult fixes are solved: - https://gitlab.winehq.org/wine/wine-staging ge-proton includes staging for builds to worksaround bugs for plain proton: - https://github.com/GloriousEggroll/proton-ge-custom WineHQ also offers staging builds for various distros: - https://dl.winehq.org/wine-builds For example, for my Debian machine I may pull from: - https://dl.winehq.org/wine-builds/debian/pool/main/
With much respect to your work, I don't understand any of it though
You may also build wine yourself to test latest changes not part of prebuilds yet: - https://gitlab.winehq.org/wine/wine/-/wikis/Building-Wine Wine-staging applies patches atop latest wine via patchinstall.py: - https://gitlab.winehq.org/wine/wine-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.
http://bugs.winehq.org/show_bug.cgi?id=60094 --- Comment #4 from Stian Low <wineryyyyy@gmail.com> --- (In reply to TheGeekn°72 from comment #0)
With much respect to your work, I don't understand any of it though
Example of bug specifically for wine-staging to fix/workaround Battle.net flickering: - https://gitlab.winehq.org/wine/wine/-/merge_requests/11398 Many gamers tend to use staging by default because it works around so many bugs. Example of my staging patch that helps workaround Battle.net flicker bug: - https://gitlab.winehq.org/wine/wine-staging/-/blob/master/patches/wined3d_un... Example of fix for my staging hack for comparison to highlight the level of difficulty difference of hacks vs fixes: - https://gitlab.winehq.org/wine/wine/-/merge_requests/10567/diffs Wine has tests for expected behavior that must pass for solutions to be considered fixes vs hacks so most of the patches in staging likely fail some of those tests despite otherwise fixing many apps thus they are kept in separate staging repo until fixes that pass tests are provided. Often staging provides a basis of understanding for what is bugged and guides for fixes. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=60094 --- Comment #5 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Stian Low from comment #4)
Example of bug specifically for wine-staging to fix/workaround Battle.net flickering: - https://gitlab.winehq.org/wine/wine/-/merge_requests/11398
Correction for Battle.net flicker bug URL: - https://bugs.winehq.org/show_bug.cgi?id=59631 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=60094 Zeb Figura <z.figura12@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com Summary|Proton crashes on game |Marathon crashes on launch |launch, error refers to | |wintrust.dll | --- Comment #6 from Zeb Figura <z.figura12@gmail.com> --- Let's please try to stay on topic. Proton is not supported in this bug tracker; please use upstream Wine or file bugs with Proton. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=60094 --- Comment #7 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Zeb Figura from comment #6)
Let's please try to stay on topic.
Proton is not supported in this bug tracker; please use upstream Wine or file bugs with Proton.
Topic: WTHelperGetProvCertFromChain bugged for wine (not just proton) Solution: test wine-staging (also not proton) via links provided wine-staging briefly explained in relation to proton for newcomer who may be less familiar. Apologies if that help is considered noise. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=60094 --- Comment #8 from Ken Sharp <imwellcushtymelike@gmail.com> --- So what version of Wine is this relevant to? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=60094 --- Comment #9 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Ken Sharp from comment #8)
So what version of Wine is this relevant to?
Seems 11.0 according to attached log: 28213.559:0028:002c:fixme:winediag:loader_init wine-cachyos 11.0 is a testing version containing experimental patches. wine-11.14-1012f3d9950 shows identical WTHelperGetProvCertFromChain as link prior to being patched. wine-staging link shows similar workaround since 2001 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=60094 --- Comment #10 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Stian Low from comment #9)
28213.559:0028:002c:fixme:winediag:loader_init wine-cachyos 11.0 is a testing version containing experimental patches.
experimental patches log typically indicates that staging is already used which contains the patch upstream so a bit confusing why it requires separate patching via github link. Maybe cachyos builds differently. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=60094 Ken Sharp <imwellcushtymelike@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |11.0 Component|wintrust |-unknown -- 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.
http://bugs.winehq.org/show_bug.cgi?id=60094 --- Comment #11 from TheGeekn°72 <thegeekno72@gmail.com> --- (In reply to Stian Low from comment #3)
(In reply to TheGeekn°72 from comment #0) Welcome to Wine and Linux and liberation. Haha thanks! Truthfully, I've been on CachyOS for just over 5 months now, I only touch windows at work for reasons beyond my control
Wine has a staging repo that seems to have already worked around this bug many years ago: Staging patches are usually considered hacks as workarounds until more difficult fixes are solved: - https://gitlab.winehq.org/wine/wine-staging You may also build wine yourself to test latest changes not part of prebuilds yet: - https://gitlab.winehq.org/wine/wine/-/wikis/Building-Wine I don't even know how to build a package yet, most of the operations I've been doing while testing how to get the game to work has been replacing precise files or trying a different proton fork, I'll mention that to my dev friends, see how we can leverage this, though my final objective was to see how we could get that fixed officially "upstream" (am I using this right within present context?) so that any "John Gamer" could play the games blocked by this issue, hopefully (as with every software project of course) there is a definite breakthrough leading to a valid fix to this issue
Wine-staging applies patches atop latest wine via patchinstall.py: - https://gitlab.winehq.org/wine/wine-staging Since my issue stems from a Proton build, I would guess this is not compatible to my situation? eh, I'll figure something out.
(In reply to Stian Low from comment #4)
(In reply to TheGeekn°72 from comment #0) Wine has tests for expected behavior that must pass for solutions to be considered fixes vs hacks so most of the patches in staging likely fail some of those tests despite otherwise fixing many apps thus they are kept in separate staging repo until fixes that pass tests are provided. Often staging provides a basis of understanding for what is bugged and guides for fixes. So, hacks that solve specific bug instances, not everything, but provides info on what exactly is to be fixed, like laboratory experiments, got it
(In reply to Stian Low from comment #10)
(In reply to Stian Low from comment #9) experimental patches log typically indicates that staging is already used which contains the patch upstream so a bit confusing why it requires separate patching via github link. Maybe cachyos builds differently. I set Steam to use proton-cachy-slr which I keep updated to latest whenever a new build releases, though we got the game to work using a different proton fork (Proton-EM 11, as per the link to the commit I shared) in which my dev friend tweaked the wintrust dll in order to skip something? jump past the part that caused the game to fail launching? I'll test by using that modded wintrust in prootn-cachy-slr to make sure it's only that halting the game launch and not moving to a different proton fork altogether (since it occurred to me I did not test to make definitively sure that was it)
(In reply to Zeb Figura from comment #6)
Let's please try to stay on topic.
Proton is not supported in this bug tracker; please use upstream Wine or file bugs with Proton. I'd just like to say that I'm here because my dev friend (who maintains Proton-EM) told me wintrust was originally a WINE component and to get that fixed, it would have to be done upstream and thus to open an issue in here since this is the source of the file and not Proton projects, sorry if there was a better place to submit this issue, I was not made aware of it.
-- 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.
http://bugs.winehq.org/show_bug.cgi?id=60094 --- Comment #12 from Stian Low <wineryyyyy@gmail.com> --- (In reply to TheGeekn°72 from comment #11)
Since my issue stems from a Proton build, I would guess this is not compatible to my situation? eh, I'll figure something out.
Wine powers much of proton so wine-staging may still apply to proton just as it does for wine but proton's version of wine may have changes that deviation from upstream which may break wine-staging patches from applying cleanly which may require proton/fork maintainers to handle them with more care to make them more compatible. I often use ge-proton as gold standard for testing if broken games have any known workarounds to save dev time and reduce redundant effort: - https://github.com/GloriousEggroll/proton-ge-custom/releases ge-proton is yet another fork like proton-cachy-sir and proton-em-11 and therefore similarly compatible to your situtation. Because ge-proton uses wine-staging unlike vanilla proton, it seems unlikely you would have encountered the WTHelperGetProvCertFromChain bug because ge-proton seems to use the workaround patch from wine-staging.
(In reply to Stian Low from comment #4) So, hacks that solve specific bug instances, not everything, but provides info on what exactly is to be fixed, like laboratory experiments, got it
Indeed but that lab that is wine-staging may be used as if a full-fledged solution like many gamers who only use wine without proton and like how of ge-proton seems to use it as an integral part that makes that fork unique from other forks without wine-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.
http://bugs.winehq.org/show_bug.cgi?id=60094 --- Comment #13 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Stian Low from comment #12)
Indeed but that lab that is wine-staging may be used as if a full-fledged solution like many gamers who only use wine without proton and like how of ge-proton seems to use it as an integral part that makes that fork unique from other forks without wine-staging.
Wallpaper Engine bug is a recent example which may further highlight how wine-staging helps workaround game/rendering bugs and why some gamers may use wine-staging by default: - https://bugs.winehq.org/show_bug.cgi?id=59506#c3 First 3 screenshots show wine-staging fixing missing fonts and layout bugs shown for last 2 screenshots for vanilla wine without wine-staging patches applied atop: - https://bugs.winehq.org/attachment.cgi?id=81611 In this case however, reporter indicates they used ge-proton which often indicates to me that no known workarounds/fixes exist yet and is worthy of pursuing wine dev effort as a brand new bug fix. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=60094 TheGeekn°72 <thegeekno72@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |wintrust Distribution|--- |ArchLinux -- 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.
http://bugs.winehq.org/show_bug.cgi?id=60094 Hans Leidekker <hans@meelstraat.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Fixed by SHA1| |2974626684216395a5059eb4b62 | |20683fc050b67 --- Comment #14 from Hans Leidekker <hans@meelstraat.net> --- Fixed by 2974626684216395a5059eb4b6220683fc050b67. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=60094 Alexandre Julliard <julliard@winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #15 from Alexandre Julliard <julliard@winehq.org> --- Closing bugs fixed in 11.17. -- 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)
-
WineHQ Bugzilla