[Bug 33319] New: Diabo 3 Freeze after 1-3 Minutes (Menu after login and ingame)

wine-bugs at winehq.org wine-bugs at winehq.org
Tue Apr 2 15:13:42 CDT 2013


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 at winehq.org
        ReportedBy: bastik at 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.



More information about the wine-bugs mailing list