https://bugs.winehq.org/show_bug.cgi?id=48811
Bug ID: 48811 Summary: StarCraft II fails to load in staging, crashes after trying to start a game in stable Product: Wine Version: 5.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dbghelp Assignee: wine-bugs@winehq.org Reporter: wschmrdr@gmail.com Distribution: ---
Created attachment 66725 --> https://bugs.winehq.org/attachment.cgi?id=66725 Output occurring when the application crashes.
Ever since upgrading from 5.3 to 5.4, StarCraft II has ceased working. On staging, this occurs during the loading screen. I am able to get through the Battle.net app OK, but cannot get to my login authenticating. I have tried switching to stable, but when trying to load up a game, I see the same output issue. Selected the dbghelp component because that's the line that comes up in the output at the time of the crash.
https://bugs.winehq.org/show_bug.cgi?id=48811
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|StarCraft II fails to load |StarCraft II fails to load |in staging, crashes after |in staging |trying to start a game in | |stable | CC| |dark.shadow4@web.de
--- Comment #1 from Fabian Maurer dark.shadow4@web.de --- Probably not dbghelp that's at fault here.
Just to make this clear, what versions did you try? wine-5.4 and wine-staging-5.4? Because there is no wine-stable 5.4.
Also, for two different bugs, please open two separate bug reports. Let's make this one about the wine-staging error. When downgrading wine-staging to 5.3, it works again?
https://bugs.winehq.org/show_bug.cgi?id=48811
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|dbghelp |-unknown
https://bugs.winehq.org/show_bug.cgi?id=48811
--- Comment #2 from wschmrdr@gmail.com --- (In reply to Fabian Maurer from comment #1)
Probably not dbghelp that's at fault here.
Just to make this clear, what versions did you try? wine-5.4 and wine-staging-5.4? Because there is no wine-stable 5.4.
Also, for two different bugs, please open two separate bug reports. Let's make this one about the wine-staging error. When downgrading wine-staging to 5.3, it works again?
I agree about dbghelp; didn't see an unknown there, so thank you for fixing.
Staging was 5.4, Stable was 5.0.0. I tried forcing the version of 5.3 and my package manager was not permitting me to downgrade. I can try again tomorrow morning; I agree the focus is 5.4, given I've had success with some of the 5.x versions.
https://bugs.winehq.org/show_bug.cgi?id=48811
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
https://bugs.winehq.org/show_bug.cgi?id=48811
--- Comment #3 from wschmrdr@gmail.com --- Downgraded manually to 5.3, and Starcraft II works at a level I believe to be satisfactory.
https://bugs.winehq.org/show_bug.cgi?id=48811
aersaud@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |aersaud@gmail.com
--- Comment #4 from aersaud@gmail.com --- I am experiencing the same issue. Compiling and installing wine-staging v5.3 works. Anything after v5.3 does not working from my testing in regards to this game.
https://bugs.winehq.org/show_bug.cgi?id=48811
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC| |z.figura12@gmail.com
--- Comment #5 from Zebediah Figura z.figura12@gmail.com --- Can you please retest with current upstream wine (6.0-rc3)?
I'm not sure what this bug ever was (what could have broken things in 5.4 specifically? There's not a lot related to its anticheat there...) but I'm happy to mark it as FIXED if nothing's broken anymore...
https://bugs.winehq.org/show_bug.cgi?id=48811
Berillions berillions@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |berillions@gmail.com
--- Comment #6 from Berillions berillions@gmail.com --- (In reply to Zebediah Figura from comment #5)
Can you please retest with current upstream wine (6.0-rc3)?
I'm not sure what this bug ever was (what could have broken things in 5.4 specifically? There's not a lot related to its anticheat there...) but I'm happy to mark it as FIXED if nothing's broken anymore...
Hi Zebediah,
I don't know if it's related but i tried SC2 with all wine-6.0 rc version and i found a strange issue.
If you create a 64bits prefix, you succeed to launch the game once (generally the 1st time). For the next launch, the game load, all SC2 processes exist but there is no game's window. This issue exists if you use 32 or 64bits version of the game (you change the version in the game's properties)
But if you create a 32 prefix only, the game works correctly without problem. Each time you launch the game, the game's window appears.
I'm not sure to be clear but like the 1st episode is free, i think you can reproduce this easily.
Maxime
https://bugs.winehq.org/show_bug.cgi?id=48811
--- Comment #7 from Berillions berillions@gmail.com --- New infos : The game works in a 64bits prefix if you launch it with 32bits version. If you have launched the game with 64bits version, you need to kill SC2_x64.exe and SC2Switcher_x64.exe before.
When i launch the 64bits version, i have this error version in my output console : 0570:err:virtual:virtual_setup_exception stack overflow 1808 bytes in thread 0570 addr 0x7fd9fb523552 stack 0x9b008f0 (0x9b00000-0x9b01000-0xa300000)
https://bugs.winehq.org/show_bug.cgi?id=48811
Linards linards.liepins@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |linards.liepins@gmail.com
--- Comment #8 from Linards linards.liepins@gmail.com --- (In reply to Berillions from comment #7)
New infos : The game works in a 64bits prefix if you launch it with 32bits version. If you have launched the game with 64bits version, you need to kill SC2_x64.exe and SC2Switcher_x64.exe before.
When i launch the 64bits version, i have this error version in my output console : 0570:err:virtual:virtual_setup_exception stack overflow 1808 bytes in thread 0570 addr 0x7fd9fb523552 stack 0x9b008f0 (0x9b00000-0x9b01000-0xa300000)
Dupe of https://bugs.winehq.org/show_bug.cgi?id=51273 , no?
https://bugs.winehq.org/show_bug.cgi?id=48811
--- Comment #9 from Zebediah Figura z.figura12@gmail.com --- (In reply to Linards from comment #8)
(In reply to Berillions from comment #7)
New infos : The game works in a 64bits prefix if you launch it with 32bits version. If you have launched the game with 64bits version, you need to kill SC2_x64.exe and SC2Switcher_x64.exe before.
When i launch the 64bits version, i have this error version in my output console : 0570:err:virtual:virtual_setup_exception stack overflow 1808 bytes in thread 0570 addr 0x7fd9fb523552 stack 0x9b008f0 (0x9b00000-0x9b01000-0xa300000)
Dupe of https://bugs.winehq.org/show_bug.cgi?id=51273 , no?
That comment predates the regression commit by several months.
https://bugs.winehq.org/show_bug.cgi?id=48811
--- Comment #10 from Fabian Maurer dark.shadow4@web.de --- Any news on this?
https://bugs.winehq.org/show_bug.cgi?id=48811
--- Comment #11 from wschmrdr@gmail.com --- OBE; this may be closed. Apologies for the delay in response, as I could not access the game for a long period of time.
https://bugs.winehq.org/show_bug.cgi?id=48811
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution|--- |FIXED
--- Comment #12 from Fabian Maurer dark.shadow4@web.de --- Thank you, marking FIXED then.
https://bugs.winehq.org/show_bug.cgi?id=48811
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #13 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 8.11.