http://bugs.winehq.org/show_bug.cgi?id=10117
Summary: Mpeg2Schnitt doesn't display video since wine v. 0.9.16
Product: Wine
Version: 0.9.47.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-directx-ddraw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jussaar(a)mbnet.fi
Created an attachment (id=8682)
--> (http://bugs.winehq.org/attachment.cgi?id=8682)
Full output of wine when running Mpeg2Schnitt
Since wine version 0.9.16, Mpeg2Schnitt (a program for cutting mpeg2-files) has
stopped showing video. This of course makes choosing the right cut points
virtually impossible.
When the program should display the video, wine prints out the following
errors:
fixme:win:EnumDisplayDevicesW ((null),0,0x34f544,0x00000000), stub!
err:ddraw:IDirectDrawImpl_SetDisplayMode Width=0, Height=0, what to do?
I have tested both multiple versions of wine (including the newest
0.9.47-version) and Mpeg2Schnitt (versions 0.71, 0.80 and 0.87).
Mpeg2Schnitt is distributed under GPL2 license and available for download at
http://www.mdienert.de/mpeg2schnitt/
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=10065
Summary: MSN Messenger Doesn't Show New Conversation Windows
Product: Wine
Version: 0.9.47.
Platform: PC
URL: http://www.microsoft.com/downloads/details.aspx?familyid
=CF49C56C-8B3E-4EAE-9904-9505F47BED45&displaylang=en
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-ole
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jaimerave(a)gmail.com
Created an attachment (id=8623)
--> (http://bugs.winehq.org/attachment.cgi?id=8623)
This is what the console shows when the error happens.
When someone talk to you and you haven't open a window whit that person, the
window is not showed. You had to open a window with all your contacst until you
find the one who write you.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=9913
Summary: Blue Wish Resurrection: crashes when loading program
Product: Wine
Version: 0.9.46.
Platform: PC-x86-64
URL: http://www004.upp.so-
net.ne.jp/x_xgameroom/Works/works.html
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-ole
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: 07067514(a)brookes.ac.uk
Created an attachment (id=8413)
--> (http://bugs.winehq.org/attachment.cgi?id=8413)
console output
When loading Blue Wish Resurrection the program displays a black rectangle,
then crashes. Attached is the console output.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=10236
Summary: Jazz Jackrabbit 2: Access Violation at 7DFC3B16h
Product: Wine
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wine-programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jmetal88(a)sbcglobal.net
Jazz Jackrabbit 2 installs beautifully, but after the splash screen at the
beginning of the game, it crashes with an error. In the most recent version of
Wine (obtained via WineCVS.sh, changelog last dated 2007-10-26) the error
reads:
Jazz Jackrabbit 2 has caused an access violation at address 7DFC3B16h by
attempting to "read" from address 000006F8h.
In 0.9.47:
Jazz Jackrabbit 2 has caused an access violation at address 7E176AB6h by
attempting to "read" from address 000006F8h.
In 0.9.46:
Jazz Jackrabbit 2 has caused an access violation at address 7E216856h by
attempting to "read" from address 000006F8h.
In 0.9.45:
Program runs as it should.
In 0.9.44:
Jazz Jackrabbit 2 has caused an access violation at address 00000000h by
attempting to "read" from address 00000000h.
In 0.9.43:
Program runs as it should.
In 0.9.42:
Program runs as it should.
So, something broke it in 0.9.44, fixed it in 0.9.45, and broke it again in
0.9.46 through the current version. Also, the address at which the access
violation occurs changes each time I run the program (in 0.9.46 and after) and
doesn't seem to actually have anything to do with which version of Wine is
installed.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=10112
Summary: BitBlt between 8 bit color index DIBs wrong
Product: Wine
Version: CVS/GIT
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-x11driver
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: alexd14(a)hushmail.com
Created an attachment (id=8678)
--> (http://bugs.winehq.org/attachment.cgi?id=8678)
test case
BitBlt from one 8 bit DIB to another 8 bit DIB produces wrong results. I'll
attach a simple test case that illustrates the problem. What it does: creates
two 8 bit, color index dib sections with a color table where color index 1 =
red, 2 = blue, 3 = green. Then it fills first DIB with 1 (red) and second with
2 (blue). It then does a BitBlt with SRCPAINT (OR) ROP from first DIB to
second. Finally, this DIB is drawn in a window, and a hex value of the first
pixel is drawn over it for convenience.
In such BitBlt Windows, apparently, operates on DIB pixels as color index
values w/o palette lookup; 1 OR 2 == 3, so it fills destination DIB pixels with
3, and, consequently, it is displayed as a green rectangle.
In Wine, this operation works like actual RGB values (red and blue) from
palettes are getting combined, and it's displayed as a magenta rectangle.
Probably, because wine seems to convert it to truecolor pixmaps internally.
Pixels as stored in memory become zeros.
Real app affected by it: igonwin.exe in bug #201
(http://bugs.winehq.org/show_bug.cgi?id=201). I don't have other apps that use
color index dibs to test, but I think any apps that use such DIBs AND "fancy"
ROPs (XOR, AND, OR etc) may be affected.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=9798
Summary: bioshock demo needs glsl enabled
Product: Wine
Version: CVS/GIT
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Created an attachment (id=8240)
--> (http://bugs.winehq.org/attachment.cgi?id=8240)
crash log with glsl disabled
Hello,
Bioshock demo crashes if glsl is not enabled.
Attached are relevant traces made with:
WINEDEBUG=+seh,+tid,+d3d,+d3d_shader wine ./Bioshock.exe -dx9
Using following registry settings enables bioshock demo to run:
--- snip ---
HKEY_CURRENT_USER/Software/Wine/Direct3D
UseGLSL = "enabled"
--- snip ---
Optional: OffscreenRenderingMode = "fbo"
==================
Addendum:
wine --version
wine-0.9.45-406-g2ba3247
Currently uses secuROM hack (http://bugs.winehq.org/attachment.cgi?id=8235
) to run, see http://bugs.winehq.org/show_bug.cgi?id=7065
Be sure to include "-dx9" command line to work around directx 10 issue.
Regards
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=10225
Summary: SafeDisc 2.x triggers async device ioctl status code
propagation bug in wine server
Product: Wine
Version: CVS/GIT
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-kernel
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Created an attachment (id=8843)
--> (http://bugs.winehq.org/attachment.cgi?id=8843)
relevant trace which shows ioctl status code propagation bug
Hello,
while testing my proof-of-concept patch which makes SafeDisc v2 (yuck!) finally
work, I stumbled across a nasty ioctl status code propagation (completion) bug
in wine server.
Wasted several hours on it .. I was suspecting SD issue whole time, but its a
wine server bug :(
Attached is relevant trace (WINEDEBUG=+seh,+tid,+relay,+ntoskrnl,+server wine
./BfVietnam.exe)
Before the bug is triggered, the SafeDisc security driver makes several device
ioctl requests which return 0xC0000001 (unsuccessful) on purpose, e.g. reading
debug Drx registers with index that does not exist.
This is intended to fool reversers :-)
The next operation - checking IDT entries should succeed - but does not (as
seen from calling client).
The kernel driver completes the operation successfully and returns
irp.IoStatus.u.Status == 0 with xxxx bytes in output buffer.
I verified it several times by debugging the kernel driver.
Upon driver ioctl call return, get_next_device_request() is triggered again in
ntoskrnl event loop which sets the return data (and status code) ->
set_ioctl_result().
This queues an APC, waking up the client (alertable state).
The client process device ioctl completes with 0 (FALSE) which is wrong.
Further debugging showed that ioctl_completion APC (dlls/ntdll/file.c) returns
the errornous status code in get_ioctl_result() when woken up by server.
This error is then propagated in server_ioctl_file() to result in wrong
NtDeviceIoControlFile() return code.
What puzzled me is that "ioctl->status" is correctly set by set_ioctl_result()
(=0) but get_ioctl_result() - called within client context - yields the
previous error code (0xC0000001 of failed request).
This is either a problem of global vs. thread local error status (global_error
vs. current->error/thread) or the ioctl call data is the wrong one.
The following patch works for me, letting SD 2.x continue - though i'm not sure
if it's right:
--- snip ---
diff --git a/server/device.c b/server/device.c
index 46b2796..8fe8f7c 100644
--- a/server/device.c
+++ b/server/device.c
@@ -528,7 +528,7 @@ DECL_HANDLER(get_ioctl_result)
ioctl->out_data = NULL;
}
}
- set_error( ioctl->status );
+
list_remove( &ioctl->dev_entry );
release_object( ioctl ); /* no longer on the device queue */
}
--- snip ---
Regards
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=9454
Summary: Panzer General III Scorched Earth hang with
seh:setup_exception nested exception
Product: Wine
Version: 0.9.44.
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-kernel
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: phajdan.jr(a)gmail.com
While normally playing in the battle screen, the game hanged, the music started
to repeat a short fragment, and the UI was unresponsive. The error printed was
err:seh:setup_exception nested exception on signal stack in thread 002b eip
ffffe405 esp 7ffdd648 stack 0x241000-0x350000
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=9400
Summary: Panzerg General III Scorched Earth random hang,
threading-related
Product: Wine
Version: 0.9.43.
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: phajdan.jr(a)gmail.com
At random moments the game hangs, will attach wine output in a moment.
Note that this log is only relevant for wine 0.9.43. Before it also hanged
sometimes, but the message
err:ntdll:RtlpWaitForCriticalSection section 0x7eb87ae0 "gdiobj.c: GDI_level"
wait timed out in thread 000c, blocked by 0009, retrying (60 sec)
wine: Critical section 7eb87ae0 wait failed at address 0x7ef97b20 (thread
000c), starting debugger...
was not present. And before upgrade to 0.9.43 it had some problems with music,
like randomly switching tracks etc (sometimes it hanged during these, sometimes
not). After the upgrade the problem is gone, when it hangs music still plays,
but the mouse does not move, and the game does not receive keyboard input.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=10211
Summary: gmax installer does not allow changing of installation
directory, fails to install
Product: Wine
Version: CVS/GIT
Platform: PC
URL: http://www.turbosquid.com/gmax
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ead1234(a)hotmail.com
When trying to install gmax the application fails to continue stating it will
be installing over existing installation and prompts you to choose a new
location, choosing a new location through the browse dialog does not change the
install path, and does not allow you to continue the installation.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.