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.