http://bugs.winehq.org/show_bug.cgi?id=33413
Bug #: 33413 Summary: Diablo III: Random non-responding UI elements Product: Wine Version: 1.5.27 Platform: x86-64 URL: http://www.diablo3.com/ OS/Version: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: frederic.delanoy@gmail.com CC: julliard@winehq.org Classification: Unclassified Regression SHA1: 9181b7e8763e9070f6a1d636aeb882db829867d8
Since 1.5.27, I get random issue in the main interface (*not* while playing)
I don't get the issues in every application start, but is basically "all or nothing".
Typically, trying to join a chat channel or quitting one fails with no message in chat box. Also, hitting "Play" can fail as well (other buttons are grayed out as usual, but no actual game is launched) Sometimes one can't even login to battle.net to begin with.
Regression test gave:
commit 9181b7e8763e9070f6a1d636aeb882db829867d8 Author: Alexandre Julliard julliard@winehq.org Date: Thu Apr 4 13:01:04 2013 +0200
kernel32: Fetch the system information only once the memory limits are correct.
http://bugs.winehq.org/show_bug.cgi?id=33413
Erich Hoover ehoover@mines.edu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ehoover@mines.edu
http://bugs.winehq.org/show_bug.cgi?id=33413
Felipe Gustavo de Oliveira felipe.nemesis@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |felipe.nemesis@gmail.com
--- Comment #1 from Felipe Gustavo de Oliveira felipe.nemesis@gmail.com 2013-04-19 21:16:36 CDT --- Bug happens in any Wine version from 1.5.0 and up, while using proprietary FGLRX driver
In early Diablo 3 versions this bug didnt occurs, prior the patch 1.0.2 the bug started to happen.
http://bugs.winehq.org/show_bug.cgi?id=33413
--- Comment #2 from Frédéric Delanoy frederic.delanoy@gmail.com 2013-04-20 03:15:45 CDT --- (In reply to comment #1)
Bug happens in any Wine version from 1.5.0 and up, while using proprietary FGLRX driver
I'm using nVidia blob, and it only started happening with the specified regression commit (somewhere between 1.5.27 and 1.5.28)
In early Diablo 3 versions this bug didnt occurs, prior the patch 1.0.2 the bug started to happen.
Unfortunately one can only test with the latest Diablo 3 version, due to the way the game is designed.
http://bugs.winehq.org/show_bug.cgi?id=33413
--- Comment #3 from Felipe Gustavo de Oliveira felipe.nemesis@gmail.com 2013-04-20 20:34:25 CDT --- Are you using setarch i386 -3 wine diablo3.exe to lunch the game?
When warden its active on server side playing the game without setarch in a x86_64 enviroment always brings gui corruption, low fps and gui elements stopping to response. Also Auction house stops to work.
Lunching the game with setarch i386 -3 fix the insue, however the performance decreases a little.
(In reply to comment #2)
(In reply to comment #1)
Bug happens in any Wine version from 1.5.0 and up, while using proprietary FGLRX driver
I'm using nVidia blob, and it only started happening with the specified regression commit (somewhere between 1.5.27 and 1.5.28)
In early Diablo 3 versions this bug didnt occurs, prior the patch 1.0.2 the bug started to happen.
Unfortunately one can only test with the latest Diablo 3 version, due to the way the game is designed.
http://bugs.winehq.org/show_bug.cgi?id=33413
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Diablo III: Random |Diablo III: Intermittent |non-responding UI elements |non-responsive UI elements
http://bugs.winehq.org/show_bug.cgi?id=33413
--- Comment #4 from Frédéric Delanoy frederic.delanoy@gmail.com 2013-05-01 15:24:45 CDT --- (In reply to comment #3)
Are you using setarch i386 -3 wine diablo3.exe to lunch the game?
No. Never had.
When warden its active on server side playing the game without setarch in a x86_64 enviroment always brings gui corruption, low fps and gui elements stopping to response. Also Auction house stops to work.
I have no GUI corruption, just non-responsive stuff.
Lunching the game with setarch i386 -3 fix the issue, however the performance decreases a little.
Launching with "setarch i386 -3" works around the issue, yes (but that's not a real fix). Note I never had such issues before the mentioned "regression commit".
http://bugs.winehq.org/show_bug.cgi?id=33413
--- Comment #5 from Alexandre Julliard julliard@winehq.org 2013-06-11 09:33:04 CDT --- Actually, before the fix we would report wrong limits, so it would have essentially the same effect as setarch -3. Now that the limits are fixed it makes sense that you'd have to do setarch explicitly.
http://bugs.winehq.org/show_bug.cgi?id=33413
--- Comment #6 from Erich Hoover erich.e.hoover@gmail.com 2013-06-11 10:16:42 CDT --- (In reply to comment #5)
Actually, before the fix we would report wrong limits, so it would have essentially the same effect as setarch -3. Now that the limits are fixed it makes sense that you'd have to do setarch explicitly.
Should we maybe be reporting different limits if it's a WoW64 process?
http://bugs.winehq.org/show_bug.cgi?id=33413
--- Comment #7 from Frédéric Delanoy frederic.delanoy@gmail.com 2013-08-26 11:18:24 CDT --- (In reply to comment #6)
(In reply to comment #5)
Actually, before the fix we would report wrong limits, so it would have essentially the same effect as setarch -3. Now that the limits are fixed it makes sense that you'd have to do setarch explicitly.
Should we maybe be reporting different limits if it's a WoW64 process?
Any update/progress on this?
http://bugs.winehq.org/show_bug.cgi?id=33413
--- Comment #8 from Erich Hoover erich.e.hoover@gmail.com 2013-08-26 11:51:14 CDT --- (In reply to comment #7)
... Any update/progress on this?
Sorry, forgot to report back. In my testing it seemed that the WoW64 processes get the same limits as a normal process, but maybe I was doing something wrong.
http://bugs.winehq.org/show_bug.cgi?id=33413
--- Comment #9 from Jerome Leclanche adys.wh@gmail.com --- (In reply to comment #8) This still seems to be an issue.
https://bugs.winehq.org/show_bug.cgi?id=33413
--- Comment #10 from Jerome Leclanche adys.wh@gmail.com --- (In reply to Jerome Leclanche from comment #9) Still an issue in Diablo 3 2.x. Any progress?
http://bugs.winehq.org/show_bug.cgi?id=33413
--- Comment #11 from Jerome Leclanche adys.wh@gmail.com --- (In reply to Jerome Leclanche from comment #10)
Erich, I am marking this a dupe of bug 30849. I didn't realize there were two bugs open for it.
http://bugs.winehq.org/show_bug.cgi?id=33413
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE
--- Comment #12 from Jerome Leclanche adys.wh@gmail.com --- Dupe
*** This bug has been marked as a duplicate of bug 30849 ***
http://bugs.winehq.org/show_bug.cgi?id=33413
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|DUPLICATE |---
--- Comment #13 from Frédéric Delanoy frederic.delanoy@gmail.com --- (In reply to Jerome Leclanche from comment #12)
Dupe
*** This bug has been marked as a duplicate of bug 30849 ***
How can this be a dupe of bug 30849? - bug 30849 has been filed on 2012-06-05 - this very bug only appeared after 9181b7e8763e9070f6a1d636aeb882db829867d8 (2013-04-04), and didn't occur before that date, as the regression test indicates.
http://bugs.winehq.org/show_bug.cgi?id=33413
Silviu C. silviucc@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |silviucc@gmail.com
--- Comment #14 from Silviu C. silviucc@gmail.com --- The thing is that running the game with setarch cures both issues...
http://bugs.winehq.org/show_bug.cgi?id=33413
--- Comment #15 from Frédéric Delanoy frederic.delanoy@gmail.com --- (In reply to Silviu C. from comment #14)
The thing is that running the game with setarch cures both issues...
Using setarch can workaround multiple bugs; that's doesn't mean said bugs are dupes.
http://bugs.winehq.org/show_bug.cgi?id=33413
--- Comment #16 from Jerome Leclanche adys.wh@gmail.com --- (In reply to Frédéric Delanoy from comment #15) They describe the exact same issue... it just happens at different moments of play. Network goes to a hang; sometimes it happens at authentication, sometimes it happens past login screen.
You even said it yourself:
Sometimes one can't even login to battle.net to begin with.
So I don't really understand how this issue is actually different.
http://bugs.winehq.org/show_bug.cgi?id=33413
--- Comment #17 from Frédéric Delanoy frederic.delanoy@gmail.com --- (In reply to Jerome Leclanche from comment #16)
(In reply to Frédéric Delanoy from comment #15) They describe the exact same issue... it just happens at different moments of play. Network goes to a hang; sometimes it happens at authentication, sometimes it happens past login screen.
You even said it yourself:
Sometimes one can't even login to battle.net to begin with.
So I don't really understand how this issue is actually different.
This bug appeared for me after bisected commit. But *never* earlier, as in earlier bug 30849 (see comment 13).
The symptoms maybe the same, that doesn't mean the causes are the same. Think of it this way, you can get fever e.g. from flu or gout, but that doesn't mean flu = gout.
https://bugs.winehq.org/show_bug.cgi?id=33413
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |ABANDONED
--- Comment #18 from Frédéric Delanoy frederic.delanoy@gmail.com --- Abandoned
https://bugs.winehq.org/show_bug.cgi?id=33413
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #19 from Frédéric Delanoy frederic.delanoy@gmail.com --- Closing
-
wine-bugs＠winehq.org