http://bugs.winehq.org/show_bug.cgi?id=34514
Bug #: 34514 Summary: an odd regression on an old video card Product: Wine Version: 1.7.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: galtgendo@o2.pl CC: hverbeet@gmail.com Classification: Unclassified Regression SHA1: ad178a5b55a4ca0e9c9a288baecfba9c17120860
On an r200, ad178a5b55a4ca0e9c9a288baecfba9c17120860 caused a program, that was previously running without any *obvious* problems (besides those caused by the card's age) to stop working. After commenting out those two lines, it's working again (about as good as it was before, AFAICT).
http://bugs.winehq.org/show_bug.cgi?id=34514
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
http://bugs.winehq.org/show_bug.cgi?id=34514
--- Comment #1 from Henri Verbeet hverbeet@gmail.com 2013-09-16 05:25:31 CDT --- I think this is essentially a duplicate of bug 21708. Could you post a WINEDEBUG="+d3d" log? (Mostly just so I have an overview of what the hardware does and doesn't support.)
http://bugs.winehq.org/show_bug.cgi?id=34514
--- Comment #2 from Rafał Mużyło galtgendo@o2.pl 2013-09-18 09:18:43 CDT --- Created attachment 45992 --> http://bugs.winehq.org/attachment.cgi?id=45992 +d3d log for the card
Probably the only thing that this log shows is how old this card is.
http://bugs.winehq.org/show_bug.cgi?id=34514
--- Comment #3 from Henri Verbeet hverbeet@gmail.com 2013-09-19 14:26:43 CDT --- Created attachment 46004 --> http://bugs.winehq.org/attachment.cgi?id=46004 patch
Actually, perhaps this bug is easier than bug 21708. Does the attached patch make it any better?
http://bugs.winehq.org/show_bug.cgi?id=34514
--- Comment #4 from Rafał Mużyło galtgendo@o2.pl 2013-09-19 17:12:05 CDT --- Well, it seems it does. To be more exact, the app was displaying a dialog with some message about DirectX compatible card, with this patch, it pases that point without displaying that error.
http://bugs.winehq.org/show_bug.cgi?id=34514
Henri Verbeet hverbeet@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |8eb73cd0e9aaa1d2d4bd922d03b | |6ee7a51e865ec Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #5 from Henri Verbeet hverbeet@gmail.com 2013-09-25 03:01:05 CDT --- Should be fixed by commit 8eb73cd0e9aaa1d2d4bd922d03b6ee7a51e865ec.
http://bugs.winehq.org/show_bug.cgi?id=34514
--- Comment #6 from Rafał Mużyło galtgendo@o2.pl 2013-09-25 04:50:36 CDT --- (In reply to comment #5)
Should be fixed by commit 8eb73cd0e9aaa1d2d4bd922d03b6ee7a51e865ec.
Thanks.
http://bugs.winehq.org/show_bug.cgi?id=34514
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Alexandre Julliard julliard@winehq.org 2013-09-27 13:41:52 CDT --- Closing bugs fixed in 1.7.3.
http://bugs.winehq.org/show_bug.cgi?id=34514
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |1.6.x
http://bugs.winehq.org/show_bug.cgi?id=34514
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|1.6.x |---
--- Comment #8 from Alexandre Julliard julliard@winehq.org 2013-11-15 13:40:44 CST --- Removing 1.6.x milestone from bugs included in 1.6.1.