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.