[Bug 54836] New: GrandMA3 onPC Version 1.9.2.2 page fault on startup (1.8.8.2 worked fine)
https://bugs.winehq.org/show_bug.cgi?id=54836 Bug ID: 54836 Summary: GrandMA3 onPC Version 1.9.2.2 page fault on startup (1.8.8.2 worked fine) Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wintrust Assignee: wine-bugs(a)winehq.org Reporter: nikolaus.einhauser(a)web.de Distribution: --- So MALighting just released their new "major" update (new features, breaking old ones, etc) to their software which broke compatability with wine. Their previous version worked fine. The issue can easily be reproduced by installing the software and then starting `app_gma3.exe`. It will crash on startup. Judging by `wine: Unhandled page fault on execute access to 000000000000000F at address 000000000000000F (thread 010c)`, the problem seems to be in the application. By inspecting the `+relay` log a little closer the page fault only looks like a symptom of missing error handling. From what I can tell, the issue lies in wintrust.WinVerifyTrust but feel free to look trough the attached debug log yourself. I'd very glad to provide more in-depth debug info or help otherwise to aid in fixing this. Suggestions for workarounds are also appreciated. Thank you. PS. There is a contest currently ongoing that mandates the use of version 1.9 or higher. So staying on an older previously working version is not an option for me. -- 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=54836 --- Comment #1 from nikolaus.einhauser(a)web.de --- Created attachment 74338 --> https://bugs.winehq.org/attachment.cgi?id=74338 stacktrace / threads / registers from the debugger window -- 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=54836 --- Comment #2 from nikolaus.einhauser(a)web.de --- Created attachment 74339 --> https://bugs.winehq.org/attachment.cgi?id=74339 Trimmed (because of upload filesize limit) WINEDEBUG="+relay" trace -- 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=54836 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal -- 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=54836 --- Comment #3 from nikolaus.einhauser(a)web.de --- Created attachment 74352 --> https://bugs.winehq.org/attachment.cgi?id=74352 WINEDEBUG=+wintrust wine app_gma3.exe -- 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=54836 Swiftb0y <nikolaus.einhauser(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG --- Comment #4 from Swiftb0y <nikolaus.einhauser(a)web.de> --- A couple fine folks on the winehq IRC helped me get to the bottom of this. It seems that the software has started verifying the signature of system libraries (WS2_32.dll to be exact). Since wine doesn't (and from what I understand can't) sign the library implementations, there is no easy fix. I have managed to get the software running by compiling wine myself and patching `wintrust.WinVerifyTrust` to always succeed, though that could break in future versions as well. Closing for now, though it would be nice if there was a less technically challenging solution in the future that would not require compiling wine yourself. -- 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=54836 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|NOTOURBUG |--- Status|RESOLVED |UNCONFIRMED CC| |z.figura12(a)gmail.com --- Comment #5 from Zeb Figura <z.figura12(a)gmail.com> --- I don't know that it's clear yet this is a wontfix; it may deserve some discussion 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=54836 --- Comment #6 from Swiftb0y <nikolaus.einhauser(a)web.de> --- Sure, what do you propose? -- 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=54836 --- Comment #7 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Swiftb0y from comment #6)
Sure, what do you propose?
It may be reasonable to treat any builtin DLL as signed. It may also be reasonable to distribute packages with builtin DLLs signed by a signature that Wine treats as trustworthy. -- 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=54836 --- Comment #8 from Swiftb0y <nikolaus.einhauser(a)web.de> --- Both of those sound quite reasonable. -- 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=54836 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish(a)gmail.com URL| |https://www.malighting.com/ | |downloads/products/grandma3 | |/ Keywords| |download -- 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=54836 --- Comment #9 from Hans Leidekker <hans@meelstraat.net> --- (In reply to Zeb Figura from comment #7)
(In reply to Swiftb0y from comment #6)
Sure, what do you propose?
It may be reasonable to treat any builtin DLL as signed. It may also be reasonable to distribute packages with builtin DLLs signed by a signature that Wine treats as trustworthy.
Treating builtin dlls as signed introduces discrepancies such as missing security dll section and missing catalog hash. Wine distributors that make use of dll signing would need to override it. Wine already treats builtin dll signatures as trustworthy if the certificate chain leads to a trusted root CA but these signing certificates cost money and it seems unlikely that Linux distributions would take on this task. An alternative might be to include a script that generates a self-signed signing certificate when Wine is installed, signs Wine dlls with it and adds the corresponding CA to the local trust database. -- 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 (2)
-
WineHQ Bugzilla -
WineHQ Bugzilla