Russell Weatherburn skrev:
Michel Dänzer wrote:
reassign 407371 wine
kthxbye
On Thu, 2007-01-18 at 09:55 +1100, Russell Weatherburn wrote:
After upgrading from XFree86 to Xorg, in preparation to upgrading to
Etch and to hopefully solve some other issues I was having, I noted
that there was an issue with not being able to view the video output
using the Mpeg2Schitt program.
Please elaborate on 'not being able to view the video output'. What
happens when you attempt it?
The slider and timer for the video move, however the preview screen
remains blank. Quite frustrating when you need to actually see the
video preview to know where to make your cut points.
I have tested using the same program (indeed, the whole same
.wine/fake_windows information for Wine) under a clean Sarge
installation in VMWare, and this problem does not occur. I can only
conclude that it is somewhere in Xorg that the issue lies.
What if you upgrade to X.org in VMWare as well, does the issue occur
there?
I will give that a go tonight, but I am positive that the issue will
occur there. I have tried all the currently available Wine packages
(i.e. Sarge, Etch, and Unstable) on the Xorg installation.
The stderr output from the wine execution is shown below:
[EMAIL PROTECTED]:~/.wine/fake_windows/Progs/Mpeg2Schnitt071$ wine
Mpeg2Schnitt.exe
fixme:commdlg:GetFileName95 Flags 0x00800000 not yet implemented
fixme:d3d:IWineD3DDeviceImpl_GetAvailableTextureMem (0x1340020) : stub,
simulating 64MB for now, returning 64MB left
fixme:ddraw:IDirectDrawImpl_SetCooperativeLevel
(0x1af298)->(0x10024,00000008)
err:ddraw:IDirectDrawImpl_SetDisplayMode Width=0, Height=0, what to do?
fixme:ddraw:IDirectDrawImpl_CreateSurface Wanted to get surface
dimensions from window 0x10024, but it has only
a size of 0x0. Using full screen dimensions
fixme:d3d_surface:IWineGDISurfaceImpl_Blt Can't handle DDBLT_WAIT flag
right now.
I don't see anything here that indicates an X issue, so I'm reassigning
to wine. Hopefully, the wine maintainer(s) can help you narrow down the
problem, and if it does turn out to be with X, feel free to reassign
back.
Thanks for your comments. I don't know why this is happening, but as
stated it only started to occur after an Xorg installation.
I don't know which version of Wine this is. Is this still a problem,
anyway? Possibly Wine was trying to use some type of hardware
acceleration that didn't work properly.
