https://bugs.winehq.org/show_bug.cgi?id=45764
Bug ID: 45764 Summary: Unhandled exception in Battle.net Product: Wine Version: 3.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcp Assignee: wine-bugs@winehq.org Reporter: svavar@kjarrval.is Distribution: ---
Created attachment 62219 --> https://bugs.winehq.org/attachment.cgi?id=62219 The terminal output when trying to run the battle.net launcher
After updating from Wine 3.14 to 3.15 on Ubuntu, the Battle.net program doesn't start anymore. The battle.net process hangs but the usual agent.exe hasn't even started. It did work earlier today before the update so the Wine update is the most likely reason.
When the Battle.net launcher program is started from the terminal, the last error line is the following: wine: Unhandled exception 0x40000015 in thread 2b at address 0x494f73 (thread 002b), starting debugger...
Tried to retrieve Program Error Details but it's gets stuck on the loading message.
Did notice a fixme message where the loader redirects from L"wined3d.dll" to L"wined3d-csmt.dll" even though the CSMT option is disabled in the configuration.
https://bugs.winehq.org/show_bug.cgi?id=45764
svavar@kjarrval.is svavar@kjarrval.is changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |critical Hardware|x86 |x86-64 Distribution|--- |Ubuntu
https://bugs.winehq.org/show_bug.cgi?id=45764
Maciej Stanczew maciej.stanczew+b@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |maciej.stanczew+b@gmail.com
--- Comment #1 from Maciej Stanczew maciej.stanczew+b@gmail.com ---
Did notice a fixme message where the loader redirects from L"wined3d.dll" to L"wined3d-csmt.dll" even though the CSMT option is disabled in the configuration.
CSMT is now enabled by default in development Wine (since version 3.3). Also, I've tried launching Battle.net with CSMT disabled, and it succeeded, without the error logs that you are experiencing.
I suggest you try with default CSMT settings -- remove "HKEY_CURRENT_USER -> Software > Wine > Direct3D > csmt" registry key for this.
https://bugs.winehq.org/show_bug.cgi?id=45764
--- Comment #2 from svavar@kjarrval.is svavar@kjarrval.is --- (In reply to Maciej Stanczew from comment #1)
Did notice a fixme message where the loader redirects from L"wined3d.dll" to L"wined3d-csmt.dll" even though the CSMT option is disabled in the configuration.
CSMT is now enabled by default in development Wine (since version 3.3). Also, I've tried launching Battle.net with CSMT disabled, and it succeeded, without the error logs that you are experiencing.
I suggest you try with default CSMT settings -- remove "HKEY_CURRENT_USER -> Software > Wine > Direct3D > csmt" registry key for this.
Removing that registry key had no effect since the same unhandled exception occurred after doing so.
https://bugs.winehq.org/show_bug.cgi?id=45764
svavar@kjarrval.is svavar@kjarrval.is changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME
--- Comment #3 from svavar@kjarrval.is svavar@kjarrval.is --- The launcher did start when I ran a relay and msgbox trace. Then I ran the launcher without a debug env variable, it started like it should have.
"WINEDEBUG=+relay,+msgbox wine Battle.net\ Launcher.exe &> winedebug.log"
Marking the bug as resolved for now.
https://bugs.winehq.org/show_bug.cgi?id=45764
anton.sudak@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |anton.sudak@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=45764
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal Component|msvcp |-unknown CC| |focht@gmx.net
https://bugs.winehq.org/show_bug.cgi?id=45764
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #4 from Austin English austinenglish@gmail.com --- Closing.