[Bug 35189] New: regression: Battle.net App fails to start after commit "msvcp100: Share the source code with msvcp90"
https://bugs.winehq.org/show_bug.cgi?id=35189 Bug ID: 35189 Summary: regression: Battle.net App fails to start after commit "msvcp100: Share the source code with msvcp90" Product: Wine Version: 1.7.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wine(a)JonnyJD.net CC: julliard(a)winehq.org Classification: Unclassified Regression SHA1: 6d30d6be78a49e1add6d8c7886484a2ceb950c71 Created attachment 46941 --> https://bugs.winehq.org/attachment.cgi?id=46941 stderr output when starting battle.net app Battle.net App started with 1.7.8 and later commits (failed after 15 seconds, but that is a differnt bug), but broke completely with http://source.winehq.org/git/wine.git/commitdiff/6d30d6be78a49e1add6d8c78864... Breaking means the exe starts, but no Window opens. The exe keeps running. I am running git version of wine in Arch Linux 64 bit with this package: https://aur.archlinux.org/packages/wine-git/ (added --disable-tests and specific commits added for bisection). The prominent error (that didn't appear otherwise) seems to be: err:ntdll:RtlpWaitForCriticalSection section 0x7e7362e0 "?" wait timed out in thread 001e, blocked by 0000, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x7e7362e0 "?" wait timed out in thread 001e, blocked by 0000, retrying (60 sec) with several of these above: fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f76c 1 C) semi-stub I didn't try to revert the patch myself, since it is a more complex patch and there have been related changes around the commit. I am afk for the evening (europe), but I will be available on the weekend to test things. I also tested another program, Diablo 3 (stable), which doesn't seem to be affected. -- 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=35189 Johannes Dewender <wine(a)JonnyJD.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression -- 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=35189 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE Regression SHA1|6d30d6be78a49e1add6d8c78864 | |84a2ceb950c71 | --- Comment #1 from Alexandre Julliard <julliard(a)winehq.org> --- Probably duplicate. *** This bug has been marked as a duplicate of bug 35181 *** -- 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=35189 Johannes Dewender <wine(a)JonnyJD.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #46941|0 |1 is obsolete| | --- Comment #2 from Johannes Dewender <wine(a)JonnyJD.net> --- Created attachment 46942 --> https://bugs.winehq.org/attachment.cgi?id=46942 better stderr output somehow -- 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=35189 Jerome Leclanche <adys.wh(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #3 from Jerome Leclanche <adys.wh(a)gmail.com> --- Confirming the dupe. Reverting the commit fixed it for me. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=35189 --- Comment #4 from Johannes Dewender <wine(a)JonnyJD.net> --- I can confirm that this is fixed now (same as Bug 35181). Note that there is another problem with the current Battle.net Launcher (infinetely trying to update battle.net), but that is a different problem. -- 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