[Bug 36216] New: Hearthstone fails to start, says the game timed out
https://bugs.winehq.org/show_bug.cgi?id=36216 Bug ID: 36216 Summary: Hearthstone fails to start, says the game timed out Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adys.wh(a)gmail.com (not related to bug 36178) The game is started from the Battle.net client, gets to the login screen. Then the game says: Closed Your game timed out as it was requesting data from the Hearthstone utility service. Please relaunch Hearthstone to reconnect. This error sometimes happened before, but now it's impossible to get into the game. Looking at some wireshark logs, theres a lot of crypted communication on port 1119 between hearthstone and the battle.net agent, then it stops for a few seconds and the game says it timed out. -- 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=36216 --- Comment #1 from Jerome Leclanche <adys.wh(a)gmail.com> --- Created attachment 48348 --> https://bugs.winehq.org/attachment.cgi?id=48348 WINEDEBUG=+winsock,+tid,-uniscribe wine Hearthstone\ Beta\ Launcher.exe Here is a winsock,tid log. Server killed immediately after timeout. (-uniscribe because of fixme:uniscribe:ScriptShapeOpenType Ranges not supported yet spam) -- 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=36216 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |madewokherd(a)gmail.com, | |matteo.mystral(a)gmail.com --- Comment #2 from Matteo Bruni <matteo.mystral(a)gmail.com> --- I ran a regression test and weirdly (for me at least) the culprit seems to be: commit 2005be6dc92c0943ede01525cecad88f8e83c9c7 Author: Vincent Povirk <vincent(a)codeweavers.com> Date: Wed Apr 16 15:50:37 2014 -0500 shell32: Use CREATE_NEW_CONSOLE when SEE_MASK_NOCONSOLE is omitted. Reverting it on top of wine 1.7.18 fixes the issue here. Jerome, can you confirm? I guess a +tid,+exec,+process trace might shed some light. -- 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=36216 --- Comment #3 from Jerome Leclanche <adys.wh(a)gmail.com> --- Interesting. I will give it a shot in a bit, I really didn't think it'd be a 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=36216 Vincent Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |https://us.battle.net/accou | |nt/download/?show=hearthsto | |ne&style=hearthstone --- Comment #4 from Vincent Povirk <madewokherd(a)gmail.com> --- I haven't had a chance to try reverting the patch, but I can reproduce the bug here. -- 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=36216 --- Comment #5 from Jerome Leclanche <adys.wh(a)gmail.com> --- (In reply to Vincent Povirk from comment #4) I'm currently unable to reproduce the bug, so I can't test reverting 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=36216 Vincent Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression Regression SHA1| |2005be6dc92c0943ede01525cec | |ad88f8e83c9c7 --- Comment #6 from Vincent Povirk <madewokherd(a)gmail.com> --- Reverting the patch helps here 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=36216 --- Comment #7 from Vincent Povirk <madewokherd(a)gmail.com> --- I think what's breaking this is the delay in starting Agent.exe (which is a console executable) when we also start wineconsole.exe. Using DETACHED_PROCESS doesn't break it like CREATE_NEW_CONSOLE does, so I don't think it matters what happens to the stdio handles. -- 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=36216 Jerome Leclanche <adys.wh(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |shell32 -- 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=36216 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |leslie_alistair(a)hotmail.com -- 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=36216 Xinkai <yeled.nova(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yeled.nova(a)gmail.com --- Comment #8 from Xinkai <yeled.nova(a)gmail.com> --- (In reply to Matteo Bruni from comment #2)
I ran a regression test and weirdly (for me at least) the culprit seems to be:
commit 2005be6dc92c0943ede01525cecad88f8e83c9c7 Author: Vincent Povirk <vincent(a)codeweavers.com> Date: Wed Apr 16 15:50:37 2014 -0500
shell32: Use CREATE_NEW_CONSOLE when SEE_MASK_NOCONSOLE is omitted.
Reverting it on top of wine 1.7.18 fixes the issue here. Jerome, can you confirm? I guess a +tid,+exec,+process trace might shed some light.
Thanks, reverting this works for me 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.
http://bugs.winehq.org/show_bug.cgi?id=36216 --- Comment #9 from Vincent Povirk <madewokherd(a)gmail.com> --- Well, I'm stumped. Agent.exe is started before Hearthstone, so I assume it's not related to startup timing, and I don't know what else it could be. -- 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=36216 Vijay Kamuju <infyquest(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |infyquest(a)gmail.com --- Comment #10 from Vijay Kamuju <infyquest(a)gmail.com> --- Can you send a patch to fix the spamming of FIXME's in usp10. -- 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=36216 Ozan Türkyılmaz <ozan.turkyilmaz(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ozan.turkyilmaz(a)gmail.com --- Comment #11 from Ozan Türkyılmaz <ozan.turkyilmaz(a)gmail.com> --- I reve(In reply to Matteo Bruni from comment #2)
I ran a regression test and weirdly (for me at least) the culprit seems to be:
commit 2005be6dc92c0943ede01525cecad88f8e83c9c7 Author: Vincent Povirk <vincent(a)codeweavers.com> Date: Wed Apr 16 15:50:37 2014 -0500
shell32: Use CREATE_NEW_CONSOLE when SEE_MASK_NOCONSOLE is omitted.
Reverting it on top of wine 1.7.18 fixes the issue here. Jerome, can you confirm? I guess a +tid,+exec,+process trace might shed some light.
I reverted and game connected just fine. -- 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=36216 Tony Murray <murraytony(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |murraytony(a)gmail.com -- 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=36216 gonzo <hplgonzo(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hplgonzo(a)gmx.net -- 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=36216 nE0sIghT <update.microsoft(a)mail.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |update.microsoft(a)mail.ru -- 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=36216 --- Comment #12 from nE0sIghT <update.microsoft(a)mail.ru> --- I confirm that reverting patch works 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.
http://bugs.winehq.org/show_bug.cgi?id=36216 rmlipman(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rmlipman(a)gmail.com -- 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=36216 lubosz <lubosz(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lubosz(a)gmail.com --- Comment #13 from lubosz <lubosz(a)gmail.com> --- I can confirm that the said patch causes a regression for Hearthstone. Reverting it makes Hearthstone playable again. Please revert it for the next release. Related battle.net forums post: http://us.battle.net/hearthstone/en/forum/topic/12673258426 -- 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=36216 Chris_9 <jukeller(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jukeller(a)gmx.de -- 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=36216 Peter <forreg(a)rinaldus.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |forreg(a)rinaldus.ru --- Comment #14 from Peter <forreg(a)rinaldus.ru> --- (In reply to Ozan Türkyılmaz from comment #11)
I reve(In reply to Matteo Bruni from comment #2)
I ran a regression test and weirdly (for me at least) the culprit seems to be:
commit 2005be6dc92c0943ede01525cecad88f8e83c9c7 Author: Vincent Povirk <vincent(a)codeweavers.com> Date: Wed Apr 16 15:50:37 2014 -0500
shell32: Use CREATE_NEW_CONSOLE when SEE_MASK_NOCONSOLE is omitted.
Reverting it on top of wine 1.7.18 fixes the issue here. Jerome, can you confirm? I guess a +tid,+exec,+process trace might shed some light.
I reverted and game connected just fine.
I didn't understand is this command or what? Where should I type 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.
http://bugs.winehq.org/show_bug.cgi?id=36216 Agustín Atahides <dorklotus(a)outlook.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dorklotus(a)outlook.com --- Comment #15 from Agustín Atahides <dorklotus(a)outlook.com> --- (In reply to lubosz from comment #13)
I can confirm that the said patch causes a regression for Hearthstone. Reverting it makes Hearthstone playable again.
Please revert it for the next release.
Related battle.net forums post: http://us.battle.net/hearthstone/en/forum/topic/12673258426
Sadly they didn't fix it, the problem is still present on wine 1.7.19, I hope they get it fixed for the next release... -- 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=36216 Johannes Dewender <wine(a)JonnyJD.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wine(a)JonnyJD.net -- 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=36216 Ker noa <blue-t(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blue-t(a)web.de -- 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=36216 --- Comment #16 from Ker noa <blue-t(a)web.de> --- Created attachment 48573 --> https://bugs.winehq.org/attachment.cgi?id=48573 1.7.19 trace of Hearthstone.exe -- 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=36216 --- Comment #17 from Johannes Dewender <wine(a)JonnyJD.net> --- Created attachment 48575 --> http://bugs.winehq.org/attachment.cgi?id=48575 patch reverting commit 2005be6dc92c0943ede01525cecad88f8e83c9c7 I can confirm the problem and the fix for current git (704d169; 1.7.19 + 47 commits). Without the patch I get that error message starting hearthstone (from battle.net app, login there works). Applying the patch (reverting commit 2005be6) lets me play hearthstone fine again. (played a full match) I attach the patch that can be applied to revert the "offending" commit. (For people not having/using a git checkout) -- 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=36216 Kyle <kyleki(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kyleki(a)gmail.com -- 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=36216 Meghan Pietila <pietila.meghan(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pietila.meghan(a)gmail.com -- 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=36216 Kirill <dhampik(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dhampik(a)gmail.com -- 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=36216 a.metaphysical.drama(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |a.metaphysical.drama(a)gmail. | |com -- 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=36216 maxpotter0(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maxpotter0(a)gmail.com --- Comment #18 from maxpotter0(a)gmail.com --- (In reply to Johannes Dewender from comment #17)
Created attachment 48575 [details] patch reverting commit 2005be6dc92c0943ede01525cecad88f8e83c9c7
I can confirm the problem and the fix for current git (704d169; 1.7.19 + 47 commits).
Without the patch I get that error message starting hearthstone (from battle.net app, login there works). Applying the patch (reverting commit 2005be6) lets me play hearthstone fine again. (played a full match)
I attach the patch that can be applied to revert the "offending" commit. (For people not having/using a git checkout)
How do I download and apply this patch? I've never had to do this before. Thanks for making the patch. -- 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=36216 --- Comment #19 from Johannes Dewender <wine(a)JonnyJD.net> --- Well, this is a bit out of scope for this ticket, but you need to build wine from source like explained a bit here: https://www.winehq.org/docs/wineusr-guide/installing-wine-source Depending on your Linux distribution there might be prepared source packages you can build (but that is really out of scope, you better ask in help channels for your distribution). If you are using Ubuntu, there is a dedicated wiki page for that: http://wiki.winehq.org/Ubuntu Anyways, before you run "make" you do "patch -p1 < shlexec.patch". Please use other help channels (like for your distribution) if you need more assistance with that. There are 21 CCs for this bug and most probably don't want a dozen messages on how to patch and build wine in one specific distribution. -- 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=36216 Jarrod Meyer <jarrodmeyer+winehq(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jarrodmeyer+winehq(a)gmail.co | |m --- Comment #20 from Jarrod Meyer <jarrodmeyer+winehq(a)gmail.com> --- Johannes Dewender wrote:
I can confirm the problem and the fix for current git (704d169; 1.7.19 + 47 commits).
I've installed wine-1.7.20 in fedora 20 from the updates-testing repo, and I can confirm I am still seeing the problem. Is this not supposed to be fixed before 1.7.20? Maybe I'm missing something. -- 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=36216 Ryan Davis <iconoclasmandheresy(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iconoclasmandheresy(a)gmail.c | |om --- Comment #21 from Ryan Davis <iconoclasmandheresy(a)gmail.com> --- Confirm, still present in 1.7.20 packages from Ubuntu 14.04 PPA. I havn't had a chance to set up a proper build environment yet so testing the reversion patch isn't simple 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.
https://bugs.winehq.org/show_bug.cgi?id=36216 --- Comment #22 from Jerome Leclanche <adys.wh(a)gmail.com> --- Guys, you don't need to confirm this. The bug is known, the cause is known and reverting 2005be6dc92c0943ede01525cecad88f8e83c9c7 fixes it. A proper fix is needed to land upstream as it doesn't look like the patch will be reverted (something which could be argued but probably not worth doing so). If you don't know how git works or how to compile Wine, then please, just stick to Wine 1.7.16 and you won't have this issue. -- 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=36216 joe(a)nahmias.net <joe(a)nahmias.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joe(a)nahmias.net -- 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=36216 --- Comment #23 from Jarrod Meyer <jarrodmeyer+winehq(a)gmail.com> --- Jerome Leclanche wrote:
Guys, you don't need to confirm this. The bug is known, the cause is known and reverting 2005be6dc92c0943ede01525cecad88f8e83c9c7 fixes it.
Sorry, I thought the comment about it being fixed meant 1.7.20 was unaffected, so I wanted to share the info. -- 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=36216 --- Comment #24 from gonzo <hplgonzo(a)gmx.net> --- I can confirm, that building the latest git-version of wine (in my case 1.7.20.r158.g8762842-1) and including your patch works fine. Thank you Johannes Dewender and all the other guys, who keep track of that meanwhile more or less "solved 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.
http://bugs.winehq.org/show_bug.cgi?id=36216 --- Comment #25 from Ryan Davis <iconoclasmandheresy(a)gmail.com> --- I'm sure it does work with the patch. Reverting the regression doesn't really solve the problem since the regression was introduced by some code designed to fix a different problem. So... what we have are two different source programs, each of which has different problems. The folks working on the code are (we are told) trying to come up with something that includes the new feature and lacks the bug. That patch will then be included in a future mainline release. At that point the problem will be solved. We do have a workaround providing you are willing/able to build from source. -- 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=36216 yarglesnargle7(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yarglesnargle7(a)gmail.com --- Comment #26 from yarglesnargle7(a)gmail.com --- Created attachment 48972 --> http://bugs.winehq.org/attachment.cgi?id=48972 revert commit shell32 -- 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=36216 mathieu(a)rochette.cc changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mathieu(a)rochette.cc -- 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=36216 sveinelo <sveinelo(a)getmail.no> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sveinelo(a)getmail.no -- 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=36216 sveinelo <sveinelo(a)getmail.no> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|sveinelo(a)getmail.no | -- 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=36216 sveinelo <erik.lovland(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |erik.lovland(a)gmail.com -- 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=36216 --- Comment #27 from Kyle <kyleki(a)gmail.com> --- FWIW, the latest wine update for Fedora 20 (1.7.22-1) is still broken. -- 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=36216 babist1st(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |babist1st(a)gmail.com -- 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=36216 paulemile.purnelle(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |paulemile.purnelle(a)gmail.co | |m -- 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=36216 paulemile.purnelle(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC|paulemile.purnelle(a)gmail.co | |m | -- 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=36216 paulemile.purnelle(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |paulemile.purnelle(a)gmail.co | |m -- 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=36216 Andreas Källberg <anka.213.bacn(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anka.213.bacn(a)gmail.com -- 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=36216 Erich Hoover <erich.e.hoover(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |erich.e.hoover(a)gmail.com --- Comment #28 from Erich Hoover <erich.e.hoover(a)gmail.com> --- Could someone provide a WINEDEBUG="+exec" log? It'd be interesting to see what kind of SHELLEXECUTEINFO the application is passing. -- 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=36216 --- Comment #29 from Ker noa <blue-t(a)web.de> --- Created attachment 49282 --> https://bugs.winehq.org/attachment.cgi?id=49282 winedebug log with +exec -- 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=36216 --- Comment #30 from Ker noa <blue-t(a)web.de> --- Created attachment 49283 --> https://bugs.winehq.org/attachment.cgi?id=49283 winedebug log with +exec when started from the launcher there you go, debug log with +exec trace , game was started from the launcher. and on the other attachment run directly from the gamedir with wine -- 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=36216 ghallberg(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ghallberg(a)gmail.com -- 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=36216 lingepumpe(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lingepumpe(a)gmail.com --- Comment #31 from lingepumpe(a)gmail.com --- Any information on a proper fix that will be added to wine? Situation is rather sad with this forced downgrade or manual wine compilation... -- 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=36216 willismonroe(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |willismonroe(a)gmail.com -- 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=36216 cirilloblu(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cirilloblu(a)gmail.com -- 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=36216 czesiekbis(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |czesiekbis(a)gmail.com -- 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=36216 Cyril Roelandt <tipecaml(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tipecaml(a)gmail.com --- Comment #32 from Cyril Roelandt <tipecaml(a)gmail.com> --- I can also confirm that reverting the specified commit fixes the issue. -- 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=36216 Ing. Jan Kaláb <pitlicek(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pitlicek(a)gmail.com -- 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=36216 Stephen Mollett <molletts(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |molletts(a)yahoo.com -- 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=36216 noryb009(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |noryb009(a)gmail.com -- 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=36216 --- Comment #33 from Meghan Pietila <pietila.meghan(a)gmail.com> --- With wine 1.7.30, the attached patch fails with "Aborting due to unexpected upstream changes". I don't have the knowledge to create a patch file myself, is there anyone out there who can attach a patch that works with the more recent wine? (Hearthstone still fails to connect with 1.7.30.) -- 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=36216 roger(a)mailinator.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roger(a)mailinator.com --- Comment #34 from roger(a)mailinator.com --- What's the cause of this problem? Is it upstream (the game) issue, or something to be fixed in wine? -- 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=36216 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian(a)fds-team.de -- 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=36216 --- Comment #35 from Ryan Davis <iconoclasmandheresy(a)gmail.com> --- There is, I have gathered, a timing or order of operations issue. It is in WINE to the extent that some difference of the behavior under native Windows exposes an assumption made by the Hearthstone software that other programs do not make. It may be a case of Blizzard using undocumented behavior or exploiting documented behavior in a way that is atypical. The fact that the patch fails to apply indicates someone has done some work in the neighborhood and that a solution is perhaps forthcoming. -- 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=36216 --- Comment #36 from a.metaphysical.drama(a)gmail.com --- Patching works fine for me, i'm using the patch from the comment 26: https://bugs.winehq.org/attachment.cgi?id=48972&action=diff&context=patch&co... -- 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=36216 --- Comment #37 from Meghan Pietila <pietila.meghan(a)gmail.com> --- (In reply to Meghan Pietila from comment #33)
With wine 1.7.30, the attached patch fails with "Aborting due to unexpected upstream changes". I don't have the knowledge to create a patch file myself, is there anyone out there who can attach a patch that works with the more recent wine? (Hearthstone still fails to connect with 1.7.30.)
Tried patching again using the git sources instead of the winehq repository sources and ran successfully; was able to launch and run Battle.net and Hearthstone with no issues on Oct 10. (New problem appeared on Oct 11, but out of scope of this ticket.) Followed these directions, in case this helps any other users: http://wiki.winehq.org/Patching -- 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=36216 Jo-Herman Haugholt <johannes(a)huyderman.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |johannes(a)huyderman.com -- 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=36216 Michael Müller <michael(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michael(a)fds-team.de -- 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=36216 --- Comment #38 from Ker noa <blue-t(a)web.de> --- https://github.com/wine-compholio/wine-staging/blob/ad5dcc97522c2087727075ec... seems to be the better approach to fix this. -- 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=36216 --- Comment #39 from Sebastian Lackner <sebastian(a)fds-team.de> --- (In reply to Ker noa from comment #38)
https://github.com/wine-compholio/wine-staging/blob/ ad5dcc97522c2087727075ecfb323de1567486a6/patches/kernel32-Console_Handles/ 0001-kernel32-Invalid-console-handles-for-new-processes-a.patch
seems to be the better approach to fix this.
The patch was added just recently and still needs a bit more testing and probably also some more wine tests. But please give it a try and report back if it works. Especially report if you notice that any app breaks with the patch applied. -- 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=36216 --- Comment #40 from Johannes Dewender <wine(a)JonnyJD.net> --- (In reply to Ker noa from comment #38)
https://github.com/wine-compholio/wine-staging/blob/ ad5dcc97522c2087727075ecfb323de1567486a6/patches/kernel32-Console_Handles/ 0001-kernel32-Invalid-console-handles-for-new-processes-a.patch
I rebuilt my wine from current git (1.7.34.r74.gcf92569). With vanilla wine the error message changed since my last report. I don't get the "timed out" message anymore, but after starting Hearthstone from the launcher I get the same message already mentioned in the Hearthstone comments: The game crashed. The crash report folder named "2014-12-28_131400" next to game executable. (well, with the date of today obviously and another pid/time or what that is) With (only) the above mentioned patch added everything works fine. I can start Hearthstone and played a game till the end. Diablo 3 also doesn't break with the patch. Didn't try other programs. So the patch seems to work fine. PS: I previously used an older wine build with the patch reverting 2005be6dc92. I don't know when the error message changed, but I do guess this is because Hearthstone itself changed. -- 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=36216 --- Comment #41 from lubosz <lubosz(a)gmail.com> --- I can confirm that "kernel32: Invalid console handles for new processes are 0, not INVALID_HANDLE_VALUE." fixes the timeout issue. I hope that this will get merged soon and Hearthstone gains upstream Wine support after 9 months again. -- 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=36216 Saulius K. <saulius2(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |saulius2(a)gmail.com -- 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=36216 Johannes Dewender <wine(a)JonnyJD.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #48575|0 |1 is obsolete| | --- Comment #42 from Johannes Dewender <wine(a)JonnyJD.net> --- Created attachment 50881 --> https://bugs.winehq.org/attachment.cgi?id=50881 patch taken from wine-staging/compholio by Erich E. Hoover I added the best currently known patch to the attachments to make finding it easier. I obsoleted the patch that only reverted 2005be6dc92, since that commit was made to fix other things. What is the current status? Was the patch submitted? It is not applied in wine (git) and I also can't find it in https://source.winehq.org/patches/ -- 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=36216 --- Comment #43 from Johannes Dewender <wine(a)JonnyJD.net> --- The patch was sent to wine, but there was no reaction. Possibly because it isn't/wasn't known that this fixes a bug: https://www.winehq.org/pipermail/wine-patches/2015-January/136652.html I got the info from https://github.com/wine-compholio/wine-staging/commit/ad5dcc97522c2087727075... (where the patch was added to wine-staging) -- 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=36216 --- Comment #44 from Sebastian Lackner <sebastian(a)fds-team.de> --- (In reply to Johannes Dewender from comment #43)
Possibly because it isn't/wasn't known that this fixes a bug:
"""Several applications rely on the TEB value for fresh invalid console handles to be zero instead of INVALID_HANDLE_VALUE (fixes Bug #36216 and Bug #37914).""" What was unclear about that? ;) Erich E. Hoover is planning to resubmit the patch soon, they only stay in the patches list for about one month. -- 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=36216 --- Comment #45 from Erich E. Hoover <erich.e.hoover(a)wine-staging.com> --- (In reply to Sebastian Lackner from comment #44)
... What was unclear about that? ;) Erich E. Hoover is planning to resubmit the patch soon, they only stay in the patches list for about one month.
Yeah, it only just dropped off the list (allowing me to resend it). I'm going to resend it along with a couple other small patches as soon as I can. -- 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=36216 --- Comment #46 from Jerome Leclanche <adys.wh(a)gmail.com> --- (In reply to Erich E. Hoover from comment #45) Any update Erich? -- 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=36216 --- Comment #47 from Erich E. Hoover <erich.e.hoover(a)wine-staging.com> --- (In reply to Jerome Leclanche from comment #46)
(In reply to Erich E. Hoover from comment #45) Any update Erich?
Yup, made some fixes for some 64-bit warnings in the tests. I was planning on submitting Friday but some things came up, I'll likely get to submitting it and a couple other patches today or tomorrow. -- 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=36216 Frédéric Delanoy <frederic.delanoy(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |frederic.delanoy(a)gmail.com Resolution|--- |FIXED --- Comment #48 from Frédéric Delanoy <frederic.delanoy(a)gmail.com> --- Works in wine 1.7.40 -- 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=36216 --- Comment #49 from Sebastian Lackner <sebastian(a)fds-team.de> --- (In reply to Frédéric Delanoy from comment #48)
Works in wine 1.7.40
Are you sure that its fixed? The patch by Erich was not accepted yet, so it must be related to an update of the game itself (or you are using a distro which ships Wine-Staging by default, but then you shouldn't use it for bug reporting). -- 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=36216 Frédéric Delanoy <frederic.delanoy(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #50 from Frédéric Delanoy <frederic.delanoy(a)gmail.com> --- (In reply to Sebastian Lackner from comment #49)
(In reply to Frédéric Delanoy from comment #48)
Works in wine 1.7.40
Are you sure that its fixed? The patch by Erich was not accepted yet, so it must be related to an update of the game itself (or you are using a distro which ships Wine-Staging by default, but then you shouldn't use it for bug reporting).
I used plain compiled wine to test. I retested using 2005be6dc92c0943ede01525cecad88f8e83c9c7^ and 2005be6dc92c0943ede01525cecad88f8e83c9c7 and couldn't reproduce the original issue either. The bug probably doesn't trigger anymore due to game update itself. I'll reopen, and hopefully Jerome can retry himself. -- 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=36216 --- Comment #51 from Jerome Leclanche <adys.wh(a)gmail.com> --- I'm using a patched wine version to play the game. But there was a major game update a couple of days ago, it's likely it was fixed by that. I'd say keep the bug open until the patch lands. -- 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=36216 --- Comment #52 from Frédéric Delanoy <frederic.delanoy(a)gmail.com> --- (In reply to Jerome Leclanche from comment #51)
I'm using a patched wine version to play the game. But there was a major game update a couple of days ago, it's likely it was fixed by that.
I'd say keep the bug open until the patch lands.
Problem is, you can't test whether the proposed patch fixes the bug (since *this* bug doesn't appear anymore due to changes in the Hearthstone), so you wouldn't also be able to test later for regression testing. It would probably be better to close this bug, and create a new bug report with a simpler app showing the issue, so we can test if the proposed fix works. Erich E. Hoover would probably be most "appropriate" for this since he found the fix and wrote a patch. -- 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=36216 ghallberg(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC|ghallberg(a)gmail.com | -- 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=36216 --- Comment #53 from Erich E. Hoover <erich.e.hoover(a)wine-staging.com> --- (In reply to Frédéric Delanoy from comment #52)
... It would probably be better to close this bug, and create a new bug report with a simpler app showing the issue, so we can test if the proposed fix works.
Erich E. Hoover would probably be most "appropriate" for this since he found the fix and wrote a patch.
I'm fine with it either way, since we have no idea what other programs are affected it's really a matter of testing. I do have some tests attached to the patch that demonstrate the behavior, I'll double check things and try to get the patches submitted during my lunch break today. I've just been way to busy lately to devote any time to Wine :/ -- 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=36216 Tony Murray <murraytony(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|murraytony(a)gmail.com | -- 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=36216 Erich E. Hoover <erich.e.hoover(a)wine-staging.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |4b559f02dd6ad61287fb79547c9 | |3105aaa2f7525 Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #54 from Erich E. Hoover <erich.e.hoover(a)wine-staging.com> --- Should this affect any other apps, the problem is now fixed by commit 4b559f02dd6ad61287fb79547c93105aaa2f7525. -- 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=36216 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #55 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 1.7.42. -- 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