https://bugs.winehq.org/show_bug.cgi?id=58078
Bug ID: 58078 Summary: StarCraft Remastered: game is not started with wine-10.5 Product: Wine-staging Version: 10.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: dimich.dmb@gmail.com CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: ---
The game is not started with wine-10.5
StarCraft.exe process is running and consuming 100% of one CPU core. No video mode changed, no game window created. Battle.net launcher is displaying StartCraft as "Playing Now".
After downgrading wine to 10.4 the game starts and works fine.
StartCraft: v1.23.10.13515 OS: Arch Linux Kernel v6.14.1 GPU: Nvidia, proprietary driver v570.133.07
https://bugs.winehq.org/show_bug.cgi?id=58078
Dmytro Bagrii dimich.dmb@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dimich.dmb@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=58078
Béla Gyebrószki gyebro69@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gyebro69@gmail.com
--- Comment #1 from Béla Gyebrószki gyebro69@gmail.com --- Does the problem happen in vanilla Wine (non-Staging) too?
Could you please run a regression test to find which commit caused the issue? https://gitlab.winehq.org/wine/wine/-/wikis/Regression-Testing
I wonder if this is the same as bug #58064 because I'm also using Nvidia drivers 570.133.07.
http://bugs.winehq.org/show_bug.cgi?id=58078
--- Comment #2 from Dmytro Bagrii dimich.dmb@gmail.com --- (In reply to Béla Gyebrószki from comment #1)
Does the problem happen in vanilla Wine (non-Staging) too?
Non-staging wine can't even start Battle.net Launcher. It crashes with "Program Error: The program Battle.net.exe has encountered a serious problem and needs to close. We are sorry for inconvenience".
Some time ago I had to apply "chromium write-copy patch" to non-staging wine to get it working. Since the patch seems to be already included into wine-staging, I stopped to patch non-staging wine and switched to staging.
Could you please run a regression test to find which commit caused the issue?
Hopefully I can try to bisect wine-staging between 10.4 and 10.5 this week.
http://bugs.winehq.org/show_bug.cgi?id=58078
--- Comment #3 from Dmytro Bagrii dimich.dmb@gmail.com --- Well, I tried to bisect wine-staging repo first but couldn't do it because of failures to apply patches. So I patched vanilla wine to fix Battle.net Launcher issue and tested vanilla wine repository instead.
Vanilla wine bisection of vanilla wine showed that the issue is introduced by this commit: https://gitlab.winehq.org/wine/wine/-/commit/ab2b7ebfcd78f6a74068a5a79d90ee6...
So the ticket is possible duplicate of https://bugs.winehq.org/show_bug.cgi?id=58064
http://bugs.winehq.org/show_bug.cgi?id=58078
Dmytro Bagrii dimich.dmb@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |-unknown Product|Wine-staging |Wine
http://bugs.winehq.org/show_bug.cgi?id=58078
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #4 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
Please explain this contradiction:
(In reply to Dmytro Bagrii from comment #2)
Since the patch seems to be already included into wine-staging, I stopped to patch non-staging wine and switched to staging.
(In reply to Dmytro Bagrii from comment #3)
Well, I tried to bisect wine-staging repo first but couldn't do it because of failures to apply patches.
If you switched to staging and didn't have to patch it, then why are you trying to patch it when bisecting?
Regards.
http://bugs.winehq.org/show_bug.cgi?id=58078
--- Comment #5 from Dmytro Bagrii dimich.dmb@gmail.com --- (In reply to Olivier F. R. Dierick from comment #4)
Please explain this contradiction:
(In reply to Dmytro Bagrii from comment #2)
Since the patch seems to be already included into wine-staging, I stopped to patch non-staging wine and switched to staging.
(In reply to Dmytro Bagrii from comment #3)
Well, I tried to bisect wine-staging repo first but couldn't do it because of failures to apply patches.
If you switched to staging and didn't have to patch it, then why are you trying to patch it when bisecting?
Because vanilla wine without "chomium write-copy patch" can't even start Battle.net Loader, so without applying that patch I can't run and test StartCraft. That patch is not related to the issue described in this ticket, it is just to run Battle.net Launcher with vanilla wine. Wine-staging doesn't require that patch to run Battle.net Launcher.
In comment #3 I mean that I can't test wine-staging because patches from staging repo fail to apply to intermediate states between `wine-10.4` and `wine-10.5`.
http://bugs.winehq.org/show_bug.cgi?id=58078
Dmytro Bagrii dimich.dmb@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #6 from Dmytro Bagrii dimich.dmb@gmail.com --- Fixed by https://gitlab.winehq.org/wine/wine/-/commit/260346a9160568004b9cb123608fb98...
http://bugs.winehq.org/show_bug.cgi?id=58078
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |260346a9160568004b9cb123608 | |fb988c30623f1
http://bugs.winehq.org/show_bug.cgi?id=58078
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 10.10.
-
WineHQ Bugzilla