Bug 198327

Summary: Screen corruption after running a Direct X application (games).
Product: [Fedora] Fedora Reporter: Gian Paolo Mureddu <gmureddu>
Component: wineAssignee: Andreas Bierfert <andreas.bierfert>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: extras-qa
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-07-18 09:19:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
This is how the screen looks like after running Diablo II with Wine 0.9.16 from Extras. none

Description Gian Paolo Mureddu 2006-07-11 05:32:32 UTC 
Description of problem:
When exiting a Direct X application the screen will be corrupted and a
greenish-blueish tint is also present. This has been the case since version
0.9.15 supporting gnome-mount. Once the screen is grabled, the only way to clean
the desktop is to quit and restar the session, even other programs will have
issues, like xine or totem will keep the area where the window of the program
showed.

Version-Release number of selected component (if applicable):
wine-0.9.15 through 0.9.16

How reproducible:
Always

Steps to Reproduce:
1. Install some Direct X game or application.
2. Run said application.
3. Quit the program. A blueish-greenish tint will be left on the screen. 
  
Actual results:
See attached screenshots.


Expected results:
Previous versions of Wine did not have this problem.

Additional info:
Comment 1 Gian Paolo Mureddu 2006-07-11 05:32:32 UTC 
Created attachment 132219 [details]
This is how the screen looks like after running Diablo II with Wine 0.9.16 from Extras.
Comment 2 Andreas Bierfert 2006-07-18 09:19:30 UTC 
This actually is a Diablo 2 bug/feature you can also see on some Windows
Versions.  As to wine bugs: DirectX not working is something that happens at the
moment because wine developers are changing code ther a lot lately. So if you
have the time report these bugs at winehq.org as these are wine bugs and not
packaging bugs on fedora (at least most likely).
Comment 3 Gian Paolo Mureddu 2006-07-18 09:24:29 UTC 
Indeed, as matter of fact other user reported this in the AppDB Entry for Diablo
2 and apparently Direct3D is broken for some "legacy" Direct3D < 7 applications
(which Diablo happens to be one of them) and apparently they've solved the issue
in CVS of 0.9.18, so I'd expect this to be resolved by 0.9.18, once more, thanks
for the heads up!