[Bug 13696] New: [S.T.A.L.K.E.R] Bug with -dsound (blocking device?)

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=13696

           Summary: [S.T.A.L.K.E.R] Bug with -dsound (blocking device?)
           Product: Wine
           Version: 0.9.6.
          Platform: Other
        OS/Version: other
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: directx-dsound
        AssignedTo: wine-bugs at winehq.org
        ReportedBy: ggrabler at gmail.com


I'm experiencing problems with patch 1.0006 and the -dsound option. 

Following strange thing occurs: 
-> I'm using kde4 
-> Wine is configured to use ALSA
-> esound (esd) disabled 
-> starting stalker with -dsound option 
-> First movie plays sound 
-> 2nd movie plays no sound 
-> no sound in the menu 
-> adding -nointro 
-> sound in the menu 
-> when starting a new game, the sound seems to "lock up", not continueing
playing / starting to loop the past 1-2 secs 
-> I'm getting the following error (after the sound locked up): 
err:ntdll:RtlpWaitForCriticalSection section 0x1ad3f60 "?" wait timed out in
thread 001b, blocked by 0009, retrying (60 sec) 

Seems as if my output device got blocked - allthough, it's playing the OLD
sound (of the menu) and blocks the device with this. 
Some time later, the sound stops, and another few secs later the error above
occurs.

// G


-- 
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.