https://bugs.winehq.org/show_bug.cgi?id=58012
Bug ID: 58012 Summary: DOOM + DOOM II: rsaenh regression Product: Wine Version: 10.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: rsaenh Assignee: wine-bugs@winehq.org Reporter: joelh@disroot.org Distribution: ---
Created attachment 78271 --> https://bugs.winehq.org/attachment.cgi?id=78271 backtrace of doom_gog.exe
DOOM + DOOM II by Nightdive Studios released in 2024. I am using the GOG.com version.
The game will get past the opening screens, then crash on the main menu. It worked okay in Wine 10.2.
I have tracked down the problematic commit to: fd539487b7860ff0a53474aa6fbcbe229f3f42c1 rsaenh: Use the bundled tomcrypt to replace the local copy.
https://bugs.winehq.org/show_bug.cgi?id=58012
Joel H. joelh@disroot.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |fd539487b7860ff0a53474aa6fb | |cbe229f3f42c1
https://bugs.winehq.org/show_bug.cgi?id=58012
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
http://bugs.winehq.org/show_bug.cgi?id=58012
Paul Gofman gofmanp@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gofmanp@gmail.com
--- Comment #1 from Paul Gofman gofmanp@gmail.com --- I tried to look at it but could not immediately reproduce (tried with Steam version and with GoG version as well), those 2-3 variants of the bundled games I tried got just fine to the menu. Could you please provide the following info if possible:
1. Exact reproduction step (starting from install on clean prefix). Is it standalone install or GOG Galaxy is used? If the latter, how exactly do you install and run it (that crashes in CEF renderer with upstream Wine right now and if that was used probably something on top of upstream Wine was used or some config options applied). Which game exactly is started? I. e., full step by step reproduction steps.
2. Full complete (archived) log output from run with WINEDEBUG=pid,+timestamp,+process,+loaddll,+seh,+unwind,+crypt,+bcrypt,+advapi,+handle env var set.