[Bug 37171] New: Battle.net app: can't start games, timeout related to a critical section.
https://bugs.winehq.org/show_bug.cgi?id=37171 Bug ID: 37171 Summary: Battle.net app: can't start games, timeout related to a critical section. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tipecaml(a)gmail.com After re-starting the Battle.net App (which may have caused it to perform an update, not sure about that), I cannot launch any of my games. This happened with wine-1.7.15; I upgraded to wine-1.7.24, and later to the git version, that I'll use for the rest of this bug report: $ wine --version wine-1.7.24-161-g276af27 I'm running Debian Sid. Let's say I try to run Starcraft 2: $ wine ".wine/drive_c/Program Files/StarCraft II/StarCraft II.exe" > log_running_sc2 2>&1 This runs the Battle.net App. It looks fine, except for the announcements (upcoming games, current tournaments...) that are usually displayed in the main part of the window: they are completely missing. I then click the huge "Play" button in the bottom, which turns into a greyed out "Launching..." button, as usual, but the game is never launched. After a while, the command returns. The whole log can be found as an attachment (log_running_sc2). I'm especially worried about this line: err:ntdll:RtlpWaitForCriticalSection section 0x7bcc8260 "directory.c: dir_section" wait timed out in thread 000d, blocked by 004f, retrying (60 sec) I've also tried to wipe out my .wine directory and install the Battle.net client from scratch: $ wine Downloads/Battle.net-Setup-enGB.exe > log_clean_wine_prefix 2>&1 The installation seems stalled at 82%, when the log reads: fixme:winsock:WS_getsockopt WS_SO_CONNECT_TIME - faking results After a while, I just clicked "Cancel" and witnessed the same issue with the "dir_section" thing. I've attached the log as "log_clean_wine_prefix". This might be an issue with a recent version of the Battle.net application, or with some libraries on my PC, though I do not remember upgrading anything prior to this incident. I'm marking this bug as "Major" because it basically prevents users from running any Blizzard game managed through the Battle.net application: the same thing also happens with Hearthstone, and I would not be surprised if this happened with World of Warcraft and Diablo III as well. -- 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=37171 --- Comment #1 from Cyril Roelandt <tipecaml(a)gmail.com> --- Created attachment 49410 --> https://bugs.winehq.org/attachment.cgi?id=49410 Log when running Starcraft 2. -- 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=37171 --- Comment #2 from Cyril Roelandt <tipecaml(a)gmail.com> --- Created attachment 49411 --> https://bugs.winehq.org/attachment.cgi?id=49411 Log: installing the Battle.net app with a clean $HOME/.wine directory. -- 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=37171 Cyril Roelandt <tipecaml(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #49410|0 |1 is obsolete| | --- Comment #3 from Cyril Roelandt <tipecaml(a)gmail.com> --- Created attachment 49412 --> https://bugs.winehq.org/attachment.cgi?id=49412 Log: running Starcraft 2 -- 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=37171 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |https://us.battle.net/accou | |nt/download/ CC| |focht(a)gmx.net Version|unspecified |1.7.24 Summary|Battle.net app: can't start |Battle.net app: can't start |games, timeout related to a |games, network timeout |critical section. | Severity|major |normal --- Comment #4 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, I can't confirm, works fine here (fresh install, news, SC2). You might have been affected with the DDoS that hit several game infrastructure -> http://www.cnet.com/news/playstation-network-battle-net-go-down-under-ddos/ Also not 'MAJOR' - just because it affects a few apps/games it doesn't mean it's that all important - regardless how many million addicts^H^H^H^H^H^H^Hpeople are using it. If a wide range of Windows apps doesn't work anymore then this severity is applicable. The bug is likely invalid. Regards -- 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=37171 --- Comment #5 from Cyril Roelandt <tipecaml(a)gmail.com> --- It seems like this DDOS started yesterday (Sunday the 24th), if I'm reading the news correctly, and I've had this issue since Friday the 22nd. Also, I would find it weird to run into something like this: err:ntdll:RtlpWaitForCriticalSection section 0x7bcc8260 "directory.c: dir_section" wait timed out in thread 0041, blocked by 004e, retrying (60 sec) If the latest version of the Battle.net app works, then it might be an issue with some of the libs in Debian Sid; this might be worth debugging, since they will eventually end up in Debian testing/stable and in all Debian-based distributions. WDYT ? -- 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=37171 Cyril Roelandt <tipecaml(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #6 from Cyril Roelandt <tipecaml(a)gmail.com> --- So, I still do not think it was related to the DDOS, but after re-installing some of the dependencies and re-compiling a recent version of Wine, I cannot reproduce this bug again, so I'll just close it. -- 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=37171 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)
-
wine-bugs＠winehq.org