http://bugs.winehq.com/show_bug.cgi?id=1110
mike(a)theoretic.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
------- Additional Comments From mike(a)theoretic.com 2003-03-27 05:00 -------
No response, closing.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1110>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1156
------- Additional Comments From mike(a)theoretic.com 2003-03-27 04:59 -------
These messages can be ignored. What actually goes wrong? If no response in a few
weeks, this bug should be closed.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1156>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1295
------- Additional Comments From mike(a)theoretic.com 2003-03-27 04:53 -------
Can you get a backtrace from the crash?
Also if you could put up the last 100 lines before the debugger starts in a
relay trace, that would be good also:
wine --debugmsg +relay uoassist.exe 2>relay.log
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1295>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1253
------- Additional Comments From mike(a)theoretic.com 2003-03-27 04:42 -------
Can you give us the exact error? That function appears to be a partial stub,
some parts are in fact implemented.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1253>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1167
------- Additional Comments From mike(a)theoretic.com 2003-03-27 04:40 -------
When you get a debug window, can you give a backtrace?
FWIW I have the Java JDK working just fine here, v1.4
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1167>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1347
Summary: Screen is wiped/blanked on usage of DirectDraw
Product: Wine
Version: 20030318
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wine-directx
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: mike(a)theoretic.com
Some desktop apps that use DirectDraw, such as Java Swing and QuickTime cause
the contents of the screen to be erased. Forcing a repaint, by dragging windows
around, or by switching to a VT and back to X, restores the screen to what it
should be. The only ddraw fixmes I can see are:
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x4027f258)->(00000000,00000008)
fixme:ddraw:Main_DirectDrawClipper_Initialize
(0x4027cc90)->(0x4027f264,0x00000000),stub!
fixme:ddraw:get_display_window clipper clip lists not supported
So presumably this is a problem with clipping?
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1347>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1270
mike(a)theoretic.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From mike(a)theoretic.com 2003-03-27 04:31 -------
Closing to get this off the bug radar. MacOS X is unlikely to happen, ever.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1270>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1090
mike(a)theoretic.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
------- Additional Comments From mike(a)theoretic.com 2003-03-27 04:30 -------
Closing, the bug is old with no updates. Also the threading stuff is changing
lately, presumably the use of internal functions will be removed as well.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1090>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1343
------- Additional Comments From mike(a)theoretic.com 2003-03-27 04:29 -------
This sounds like the glibc upgrade broke you wine install. Please downgrade your
libc, recompile Wine, and see if it fixes it. If so, then this is a known issue,
it should probably be tracked in Bugzilla though.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1343>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=992
------- Additional Comments From mike(a)theoretic.com 2003-03-27 04:28 -------
Hmm, I run Galeon with Wine all the time. I don't think the two are related.
Can you get a backtrace for this?
Run the program in the wine debugger, winedbg foo.exe then when it freezes hit
ctrl-c and then when "bt", to get a backtrace.
If you're on CodeWeavers wine, you may wish to try it with the latest WineHQ.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=992>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.