[Bug 35181] New: Path of Exile doesn't start correctly, stalls
http://bugs.winehq.org/show_bug.cgi?id=35181 Bug ID: 35181 Summary: Path of Exile doesn't start correctly, stalls Product: Wine Version: 1.7.8 Hardware: x86 URL: http://webcdn.pathofexile.com/downloads/PathOfExileIns taller.msi OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: frederic.delanoy(a)gmail.com Classification: Unclassified Regression SHA1: 6d30d6be78a49e1add6d8c7886484a2ceb950c71 Created attachment 46927 --> http://bugs.winehq.org/attachment.cgi?id=46927 Terminal log wine-1.7.8-127-g6d30d6b After 6d30d6be78a49e1add6d8c7886484a2ceb950c71 is the first bad commit commit 6d30d6be78a49e1add6d8c7886484a2ceb950c71 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Thu Dec 19 17:02:11 2013 +0100 msvcp100: Share the source code with msvcp90. :040000 040000 8472290a57eeeb332f2c3a29c629baaabc438bf3 4ead5763a482e786809844f7b8f55d5ccbc829ea Mdlls game stalls early on launch. To install the game without waiting for hours, you can use patch from bug 33146 (http://www.winehq.org/pipermail/wine-patches/2013-June/124884.html; didn't get committed, though) -- 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=35181 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|regression | Regression SHA1|6d30d6be78a49e1add6d8c78864 | |84a2ceb950c71 | --- Comment #1 from Alexandre Julliard <julliard(a)winehq.org> --- Technically not a regression, the bug has always been present. The difference is that it's using builtin by default now. -- 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=35181 Vincent Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |msvcp -- 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=35181 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wine(a)JonnyJD.net --- Comment #2 from Alexandre Julliard <julliard(a)winehq.org> --- *** Bug 35189 has been marked as a duplicate of this bug. *** -- 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=35181 --- Comment #3 from Johannes Dewender <wine(a)JonnyJD.net> --- Well, from my perspective (as a user) it is a regression for the overall wine system: It worked before (because of automatic overrides) and it doesn't work now. That the functionality was not provided by a builtin dll is a technical detail, unknown to the normal user (since it doesn't show up in the config). What I take from this: Adding a dll override for msvcp100 (native then builtin) is the workaround that should be chosen starting with wine 1.7.9, even though it did work without explicitely specifying an override with wine 1.7.8. I tested this workaround and it seems to work (It opens up the window 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.
http://bugs.winehq.org/show_bug.cgi?id=35181 Xavier Vachon <xvachon(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xvachon(a)gmail.com --- Comment #4 from Xavier Vachon <xvachon(a)gmail.com> --- (In reply to comment #3)
Well, from my perspective (as a user) it is a regression for the overall wine system: It worked before (because of automatic overrides) and it doesn't work now.
That the functionality was not provided by a builtin dll is a technical detail, unknown to the normal user (since it doesn't show up in the config).
What I take from this: Adding a dll override for msvcp100 (native then builtin) is the workaround that should be chosen starting with wine 1.7.9, even though it did work without explicitely specifying an override with wine 1.7.8.
I tested this workaround and it seems to work (It opens up the window again).
Confirming that vcrun2010 works around 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=35181 --- Comment #5 from Jerome Leclanche <adys.wh(a)gmail.com> --- Affects the Battle.net agent. -- 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=35181 Frédéric Delanoy <frederic.delanoy(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Path of Exile doesn't start |Path of Exile crashes at |correctly, stalls |startup --- Comment #6 from Frédéric Delanoy <frederic.delanoy(a)gmail.com> --- As of wine-1.7.9-165-g0ae7b5f, no more stalling but a crash. No backtrace available though, but a "winedbg: Internal crash at 0x<address>" message. -- 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=35181 Rob Loach <robloach(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |robloach(a)gmail.com --- Comment #7 from Rob Loach <robloach(a)gmail.com> --- Confirmed crash at startup on Wine 1.7.9 . (In reply to comment #6)
As of wine-1.7.9-165-g0ae7b5f, no more stalling but a crash.
No backtrace available though, but a "winedbg: Internal crash at 0x<address>" message.
-- 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=35181 Jerome Leclanche <adys.wh(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |major --- Comment #8 from Jerome Leclanche <adys.wh(a)gmail.com> --- Affects several apps, technically a regression, bumping to major. -- 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=35181 Dmitry Timoshkov <dmitry(a)baikal.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal --- Comment #9 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- (In reply to comment #8)
Affects several apps, technically a regression, bumping to major.
http://bugs.winehq.org/show_bug.cgi?id=35181#c1 -- 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=35181 Jerome Leclanche <adys.wh(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |major --- Comment #10 from Jerome Leclanche <adys.wh(a)gmail.com> --- (In reply to comment #9) http://bugs.winehq.org/page.cgi?id=fields.html#importance
Major loss of functionality for a wide range of applications
-- 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=35181 Dmitry Timoshkov <dmitry(a)baikal.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |minor --- Comment #11 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- (In reply to comment #10)
http://bugs.winehq.org/page.cgi?id=fields.html#importance
Major loss of functionality for a wide range of applications
Actually it's minor since there is an easy workaround: 'winetricks vcrun2010'. -- 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=35181 Piotr Caban <piotr.caban(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |47f4e08a93eac8acbcf1ca307b3 | |0d5e531a8dbc4 Status|NEW |RESOLVED CC| |piotr.caban(a)gmail.com Resolution|--- |FIXED --- Comment #12 from Piotr Caban <piotr.caban(a)gmail.com> --- The game starts with builtin msvcp100. Marking as fixed. -- 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=35181 --- Comment #13 from Johannes Dewender <wine(a)JonnyJD.net> --- Sorry, but I don't understand this at all. According to http://wiki.winehq.org/Bugs you are not even supposed to create tickets when using *any* DLL overrides (when to report: clean wine directory) and now an issue is closed because an override "fixes" it? Either overrides are completely supported or the goal is to run stuff without any overrides. Not some weird kind of mixture. I do understand that an override is a good workaround and there might be more important things for now, but I don't think this is "works as intended". -- 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=35181 --- Comment #14 from Jerome Leclanche <adys.wh(a)gmail.com> --- (In reply to comment #13) "builtin" means Wine's. An override would be called "native". -- 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=35181 --- Comment #15 from Piotr Caban <piotr.caban(a)gmail.com> --- (In reply to comment #13)
According to http://wiki.winehq.org/Bugs you are not even supposed to create tickets when using *any* DLL overrides (when to report: clean wine directory) and now an issue is closed because an override "fixes" it? Your bug report is valid. It's ok to submit bugs when application uses native dlls shipped with it. The bug is marked fixed because the issue is resolved in git version of wine. It was not yet released so you can compile it yourself or wait for next unstable release to see the fix.
-- 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=35181 --- Comment #16 from Johannes Dewender <wine(a)JonnyJD.net> --- (In reply to comment #14)
(In reply to comment #13) "builtin" means Wine's. An override would be called "native".
I always get that wrong.. because it is *wine* builtin, but *windows* native, changing the POV. I always try to say "override" or "no override" for this exact reason and the comment didn't sound like something new was happening. Anyways, I tested again for Bug 35189 (duplicate I reported for Battle.net) and it seems to be fixed in latest git (not sure which commit). There is another problem, but that is because of the new version of the battle.net client. -- 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=35181 --- Comment #17 from Frédéric Delanoy <frederic.delanoy(a)gmail.com> --- (In reply to comment #16)
(In reply to comment #14)
(In reply to comment #13) "builtin" means Wine's. An override would be called "native".
I always get that wrong.. because it is *wine* builtin, but *windows* native, changing the POV. I always try to say "override" or "no override" for this exact reason and the comment didn't sound like something new was happening.
builtin = built in Wine, comes with Wine native = from Windows, since native apps run in Windows -- 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=35181 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #18 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 1.7.12. -- 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