[Bug 33319] New: Diabo 3 Freeze after 1-3 Minutes (Menu after login and ingame)
http://bugs.winehq.org/show_bug.cgi?id=33319 Bug #: 33319 Summary: Diabo 3 Freeze after 1-3 Minutes (Menu after login and ingame) Product: Wine Version: 1.5.26 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: bastik(a)gmx.de Classification: Unclassified Created attachment 44070 --> http://bugs.winehq.org/attachment.cgi?id=44070 Diablo console output with the given Diablo start command. Diablo 3 Freeze within 1-3 minutes after successfull login. Hardware: Notebook running Ubuntu 12.10 with wine 1.5.26 Tested Catalyst versions 12.6 / 13.1 / 13.3 beta All requirements and tips according to the Diablo 3 guide are done. (http://appdb.winehq.org/objectManager.php?sClass=version&iId=25953) CPU: Intel C2D T9300 Graphic: AMD HD4850 WINEDEBUG="-all,err+all,warn+all,fixme+all,+tid,+loaddll" WINEPREFIX=~/.local/share/wineprefixes/Diablo3 force_s3tc_enable=true WINEARCH=win32 setarch i386 -3 -L -B wine ~/Games/Diablo3/Diablo\ III.exe -launch -opengl (see attachement for output of this) The error is locking the whole XServer (Unity3D and Unity2D tested) interface. Keyboard is not responding, it is not possible to switch to another Terminal. The mouse courser is movable but will not respond to clicks. In Diablo 3 windowed mode the courser does not change when moving from the game window to the desktop. The game sound continous playing. The only way to restore the Xserver session is to remotely kill the Diablo 3 process with an SSH tunnel. I tried a lot of things to get it working, but without success. - I disabled sound - I worked around with wine registry keys (Direct3D settings) tried ervery possibile setting. Is there a possibilty to debug a running wine process after it is freezed? I tested a bit with winedbg but without success. Please advice me what to do, I don't have any ideas left, trying a few weeks to get it running. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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=33319 Bastik <bastik(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bastik(a)gmx.de -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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=33319 --- Comment #1 from Bastik <bastik(a)gmx.de> 2013-04-02 15:18:34 CDT --- Xorg.log, Dmesgand syslog do not include any traces for this issue. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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=33319 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |UPSTREAM --- Comment #2 from Austin English <austinenglish(a)gmail.com> 2013-04-02 16:53:57 CDT --- If X locks up, it's a kernel/driver bug. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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=33319 Bastik <bastik(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|UPSTREAM | --- Comment #3 from Bastik <bastik(a)gmx.de> 2013-04-03 12:44:00 CDT --- If this is a kernel/driver issue, I'm wondering about the depnedence to the "Diablo III.exe" process and that the logfiles did not show any issues after a freeze of the Diablo process. I think if Xserver freezes I should not be able to get it back running due to kill the Diablo process remotely by SSH tunnel. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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=33319 --- Comment #4 from Rico <kgbricola(a)web.de> 2013-04-03 13:25:50 CDT --- Does it also freeze with the open source graphics driver? Whats your kernel version and x version? Please have a look here http://wiki.cchtml.com/index.php/Hardware , the driver seems to be pretty picky about some dependency. If the x server hangs, it's a driver bug. A normal app (as wine) is not able to crash / hang a correctly working system. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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=33319 --- Comment #5 from Bastik <bastik(a)gmx.de> 2013-04-08 11:41:06 CDT --- Hello, the problem does not occur with mesa driver using software accelleration. It only occurs with catalyst driver using hardware acceleration. System: Intel Core 2 Duo 2.8Ghz Radeon Mobility HD4650 Tested driver versions: Catalyst 12.1, 12.6, 13.1 Kernel Version 3.2.0.39 On Ubuntu 12.04 Ubuntu 12.10 and 12.04.2 are also tested but this versions got problem with the catalyst driver support the hardware acceleration did not work with those versions. I also started a thread in AMD support forum, I think it's possibly a driver issue because software rendering is working. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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=33319 roger(a)mailinator.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roger(a)mailinator.com --- Comment #6 from roger(a)mailinator.com --- Shouldnt this be closed if the problem is upstream? -- 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=33319 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #7 from Bruno Jesus <00cpxxx(a)gmail.com> --- (In reply to Bastik from comment #5)
the problem does not occur with mesa driver using software accelleration. It only occurs with catalyst driver using hardware acceleration.
Resolving upstream then.
I also started a thread in AMD support forum, I think it's possibly a driver issue because software rendering is working.
Any news on 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=33319 Bastik <bastik(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|bastik(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.
https://bugs.winehq.org/show_bug.cgi?id=33319 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #8 from Austin English <austinenglish(a)gmail.com> --- Closing. -- 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=33319 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED --- Comment #9 from Austin English <austinenglish(a)gmail.com> --- This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG should only be closed when fixed upstream. Setting back to RESOLVED NOTOURBUG. Sorry for the 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=33319 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Diabo 3 Freeze after 1-3 |Diablo 3 freezes after 1-3 |Minutes (Menu after login |minutes on proprietary AMD |and ingame) |drivers -- 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