[Bug 50483] New: Starcraft Remastered: Unable to connect to Battle.net servers or create LAN game
https://bugs.winehq.org/show_bug.cgi?id=50483 Bug ID: 50483 Summary: Starcraft Remastered: Unable to connect to Battle.net servers or create LAN game Product: Wine-staging Version: 5.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zculek(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- With wine-staging versions >5.18 (higher than 5.18) I am no longer able to connect to Battle.net servers eaither at all (just hangs on "Connectiong..."; screenshot attached) or randomly to some specific server (most often Europe doesn't work, but sometimes others as well), no error being given. Sometimes connecting to Battle.net servers passes (mostly if I first go to create a LAN game, then return from that menu to selecting between Battle.net and LAN menu), but I am not able to create a game (error: "Failed to advertise the game. Connection lost while trying to advertise the game. (Error 5:9)"; screenshot attached) nor join any of the games (error: "Unable to join game"; screenshot attached). Creating a LAN game doesn't work either, it just hangs on "Creating game..." (screenshot attached). All of this works properly with wine-staging 5.18. The versions >5.18 that I tested - 5.19, 5.20, 5.21, 6.0-rc1 - all of them have the same problematic behavior, so I guess it must be something 5.18 > 5.19. I can confirm that this is not the issue with Battle.net availability or IP/account being temp blocked or anything similar, as everything works properly with 5.18 (also with wine-staging 5.7) and when using the same Battle.net account and connecting from the same IP/network using a Windows machine. I have also seen other users reporting the same issue elsewhere on the Internet, so this is not an isolated case/issue with my machine/setup, e.g. https://lutris.net/games/starcraft-remastered/ Let me know if any additional details are needed. I was checking the logs and console output, but I'm not sure any of it would be helpful. System: OS: Linux Mint 20 Ulyana Kernel: 5.4.0-60-generic x86_64 Working wine-staging versions: 5.18, 5.7 Non-working wine-staging versions: 5.19, 5.20, 5.21, 6.0-rc3 Screenshots: <a href="https://ibb.co/r57nHTZ"><img src="https://i.ibb.co/r57nHTZ/2020-01-11-SCR-01-LAN-hang-create-game.png" alt="2020-01-11-SCR-01-LAN-hang-create-game" border="0"></a> <a href="https://ibb.co/g6BHLZ9"><img src="https://i.ibb.co/g6BHLZ9/2020-01-11-SCR-02-Battlenet-hang-create-game.png" alt="2020-01-11-SCR-02-Battlenet-hang-create-game" border="0"></a> <a href="https://ibb.co/8sxV0Cy"><img src="https://i.ibb.co/8sxV0Cy/2020-01-11-SCR-03-Battlenet-error-create-game.png" alt="2020-01-11-SCR-03-Battlenet-error-create-game" border="0"></a> <a href="https://ibb.co/BBk2Yq8"><img src="https://i.ibb.co/BBk2Yq8/2020-01-11-SCR-04-Battlenet-error-join-game.png" alt="2020-01-11-SCR-04-Battlenet-error-join-game" border="0"></a> <a href="https://ibb.co/L5FcnzC"><img src="https://i.ibb.co/L5FcnzC/2020-01-11-SCR-05-Battlenet-hang-connecting.png" alt="2020-01-11-SCR-05-Battlenet-hang-connecting" border="0"></a> -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50483 --- Comment #1 from Zel Uneec <zculek(a)gmail.com> --- Sorry, didn't know how screenshot links will be displayed, so here are the screenshots once again, plain view: https://ibb.co/r57nHTZ https://ibb.co/g6BHLZ9 https://ibb.co/8sxV0Cy https://ibb.co/BBk2Yq8 https://ibb.co/L5FcnzC -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50483 Paul Gofman <pgofman(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pgofman(a)codeweavers.com --- Comment #2 from Paul Gofman <pgofman(a)codeweavers.com> --- Is the issue present with upstream (non Staging) Wine? Could you please also: - name specific game(s) which fails to connect (is it Starcraft I?) and exact instructions how to reproduce the issue? - attach a plain terminal output (see https://wiki.winehq.org/Bugs#How_to_report) from the failing run. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50483 --- Comment #3 from Zel Uneec <zculek(a)gmail.com> ---
Is the issue present with upstream (non Staging) Wine?
I haven't used upstream Wine for Starcraft Remasterd for quite some time, since there were multiple issues, and wine-staging worked wine, so I didn't know when I reported the bug. I just tested upstream Wine 5.18 and 5.19 - wiht 5.18 everything works as expected, the same as wine-staging 5.18, while the issue is present in upstream Wine 5.19 as well, just as in wine-staging 5.19. I haven't tested >5.19 versions (6.0-rc included). Should this be moved to upstream instead of wine-staging then?
Could you please also: - name specific game(s) which fails to connect (is it Starcraft I?)
I named the game in subject, as per guidelines - "Starcraft Remastered" - which is a remastered version of Starcraft Brood War (or Stacraft I if you want it that way), but the game is also named "Starcraft Remastered" in AppDB - https://appdb.winehq.org/objectManager.php?sClass=version&iId=35645
and exact instructions how to reproduce the issue?
Sure, sorry on that... Steps to reproduce are: 1. Install wine-staging 5.19 2. Install Battle.net desktop app - https://www.blizzard.com/download/confirmation?product=bnetdesk 4. Start Battle.net desktop app, login. 5. Install Starcraft Remastered (/Anthology) through Battle.net desktop app. 6. Start Starcraft, go to Multiplayer, select "Starcraft Brood War - Expansion", (on first run click OK to install and use Bonjour for LAN and) then: 6.a)I. Choose "Battle.net" - this hangs on "Connecting..." 6.a)II. If you manage to connect to Battle.net server (first go to create a LAN game, then return from that menu to selecting between Battle.net and LAN menu - magically works, but only once), try to join random game - fails with "Unable to join game" - or try to create a game (standard setting are OK, it doesn't matter really) - it fails with "Failed to advertise the game. Connection lost while trying to advertise the game. (Error 5:9)" 6.b) Choose "Local Area Network", create and ID or use an existing one, click "Create Game", choose any Game Type and map and click on OK - this hangs on "Creating game..."
- attach a plain terminal output (see https://wiki.winehq.org/Bugs#How_to_report) from the failing run.
Will try to get it today. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50483 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #4 from Zebediah Figura <z.figura12(a)gmail.com> --- I think this is already bug 50366. Please try the attached patch there if possible. *** This bug has been marked as a duplicate of bug 50366 *** -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50483 --- Comment #5 from Paul Gofman <pgofman(a)codeweavers.com> --- Sorry, missed the name of the game in the subject initially. I think I am reproducing the issue, it is starting from commit: commit 02a764e702094572186e079f6d48946627336d03 Author: Zebediah Figura <z.figura12(a)gmail.com> Date: Mon Sep 28 22:35:03 2020 -0500 ws2_32: Look for supported socket parameters if any parameters to WSASocket() are zero. I am debugging this, it is not clear yet though what it going wrong, looks like (as it already happened with the same commit in the past) it is not wrong per se but triggers different application behaviour now when getsockopt() returns something for the sockets created without specifying protocol. And no, implementing SIO_BASE_HANDLE does not help (at least alone). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50483 --- Comment #6 from Austin English <austinenglish(a)gmail.com> --- Closing. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50483 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #7 from Austin English <austinenglish(a)gmail.com> --- Closing. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla