Bug 744865

Summary: Warzone 2100 doesn't play nice with KDE's compositing
Product: [Fedora] Fedora Reporter: mark gress <mgress>
Component: warzone2100Assignee: Karol Trzcionka <karlikt>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: karlikt
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 15:30:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
opening screen effects on
none
opening screen effects off
none
In game, effects on
none
In game, effects off none

Description mark gress 2011-10-10 17:38:33 UTC
Created attachment 527280 [details]
opening screen effects on

Description of problem: Warzone2100 plays just fine with desktop effects disabled.  With them enabled, many on screen objects go dark or flicker.

Version-Release number of selected component (if applicable): Warzone 2100 2.3.7-1
kde 4.6.5-2

How reproducible:  Always

Steps to Reproduce: (See screenshots)
1. Enable desktop effects, launch warzone
2. Disable desktop effects, launch warzone
3. 
  
Actual results: Depending on the state of desktop effects, the game is playable.  It doesn't crash with the compositor enabled, it just looks horrible.

Expected results: Should work the same regardless of the state of desktop effects.

Additional info: My videocard is an r200-class chip

Comment 1 mark gress 2011-10-10 17:39:37 UTC
Created attachment 527281 [details]
opening screen effects off

Comment 2 mark gress 2011-10-10 17:41:26 UTC
Created attachment 527282 [details]
In game, effects on

Comment 3 mark gress 2011-10-10 17:42:56 UTC
Created attachment 527283 [details]
In game, effects off

Comment 4 mark gress 2011-11-22 23:45:55 UTC
Same in F16

Comment 5 Fedora End Of Life 2013-01-16 14:28:13 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Fedora End Of Life 2013-02-13 15:30:56 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.