https://bugs.winehq.org/show_bug.cgi?id=53720
Bug ID: 53720 Summary: Starcraft Remastered: Product: Wine-staging Version: 7.18 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: ---
Created attachment 73151 --> https://bugs.winehq.org/attachment.cgi?id=73151 Wine running Starcraft log
Selecting "Local Area Network" in "Select Connection" causes following message: "Bonjour is required to search for available LAN".
After selecting "Ok" following message appears: "Failed to activate the Bonjour service."
Only once i got no messages/errors with wine-staging-7.18 in 10-15 attempts.
Downgrade wine-staging to v7.17 solves the problem. Looks like regression of https://bugs.winehq.org/show_bug.cgi?id=52335
Starcraft Remastered v1.23.10.11109
Arch Linux, x86_64, kernel 5.19.10-arch1-1
https://bugs.winehq.org/show_bug.cgi?id=53720
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be Keywords| |regression Summary|Starcraft Remastered: |Starcraft Remastered LAN | |play complains about | |Bonjour service
--- Comment #1 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
Does the issue happen with upstream (=not staging) wine?
Bisecting between 7.17 & 7.18 may speed-up the fixing. The instructions for regression testing can be found there: https://wiki.winehq.org/Regression_Testing
Regards.
https://bugs.winehq.org/show_bug.cgi?id=53720
--- Comment #2 from Dmytro Bagrii dimich.dmb@gmail.com --- (In reply to Olivier F. R. Dierick from comment #1)
Does the issue happen with upstream (=not staging) wine?
No, it doesn't, upstream wine-7.18 works fine. I use wine-staging because some time ago (a year?) upstream wine failed to run Starcraft Remastered at all. Now i can see it does run.
Bisecting between 7.17 & 7.18 may speed-up the fixing.
Do you mean to bisect upstream wine if it doesn't work too? But it works. As i understand, for wine-staging i should bisect https://github.com/wine-staging/wine-staging, not https://source.winehq.org/git/wine.git, right?
https://bugs.winehq.org/show_bug.cgi?id=53720
--- Comment #3 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to Dmytro Bagrii from comment #2)
Do you mean to bisect upstream wine if it doesn't work too? But it works. As i understand, for wine-staging i should bisect https://github.com/wine-staging/wine-staging, not https://source.winehq.org/git/wine.git, right?
Hello,
If it works with upstream Wine then, yes, it is different.
Wine-staging is only a set of patches applied on the upstream wine source. You'll need to be able to compile wine from source (https://wiki.winehq.org/Building_Wine).
It is easier to bisect wine-staging by hand (See https://wiki.winehq.org/Wine-Staging#Building_from_source and https://wiki.winehq.org/Wine-Staging#Regressions_between_Staging_versions)
There is two way to do the regression test: - Set wine and wine-staging to 7.18 and disable wine-staging patchset one at a time between each rebuild, until you find the patchset(s) that breaks the game. - Rebuild wine and wine-staging to each of the respective commit numbers from the rebase history (https://github.com/wine-staging/wine-staging/commits/master) until you find the first commit that breaks the game.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=53720
--- Comment #4 from Zeb Figura z.figura12@gmail.com --- It's probably much less time-consuming to bisect wine against wine-staging by applying the patches as commits. There's instructions on the same page.
https://bugs.winehq.org/show_bug.cgi?id=53720
--- Comment #5 from Dmytro Bagrii dimich.dmb@gmail.com --- Created attachment 73160 --> https://bugs.winehq.org/attachment.cgi?id=73160 mdnsResponder.exe window
https://bugs.winehq.org/show_bug.cgi?id=53720
--- Comment #6 from Dmytro Bagrii dimich.dmb@gmail.com --- (In reply to Zeb Figura from comment #4)
It's probably much less time-consuming to bisect wine against wine-staging by applying the patches as commits. There's instructions on the same page.
As i understand, i can't bisect https://github.com/wine-staging/wine-staging because patchsets must be applied in a strict order and it differs from commits order. I tried to checkout wine-staging in a middle between v7.17 and 7.18 but build obviously failed with
error: patch failed: configure:20910 error: configure: patch does not apply error: patch failed: configure.ac:2361 error: configure.ac: patch does not apply ERROR: Failed to apply patch, aborting!
Clean build takes about 20 minutes on my system, and bisecting 178 patchsets will take up to 7 iterations if i'm not lucky. So findning exact patchset will be not easy.
Also the bug seems floating: after one successfull run with upstream or staging 7.17 i can't reproduce it with 7.18 until reboot. Of course, i wait until `wineserver` and other subprocesses terminated. So i have to reboot every time to reproduce it.
Also sometimes "Bonjour is required to search for available LAN" appears not immediately after i select "Local Area Network" but several seconds later when i already entered to menu.
Additinal observation: before "Failed to activate Bonjour service" message appear i see shortly appearing window. I managed to iconify Starcraft and catch it on screenshot: https://bugs.winehq.org/attachment.cgi?id=73160.
https://bugs.winehq.org/show_bug.cgi?id=53720
--- Comment #7 from Dmytro Bagrii dimich.dmb@gmail.com ---
bisecting 178 patchsets will take up to 7 iterations
Ah, i can't just comment out some number of last patchsets in patchinstall.sh, it also breaks build.
Could you please point me to exact instruction how to build intermediate version of staging between v7.17 and v7.18? Can't find at the page on wiki.
-
WineHQ Bugzilla