Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 584999 - Compiz desktop cube broken with dual-head
Compiz desktop cube broken with dual-head
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Ben Skeggs
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-04-22 17:06 EDT by Ondrej Zary
Modified: 2011-06-27 11:48 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-27 11:48:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
screenshot (352.11 KB, image/png)
2010-04-22 17:07 EDT, Ondrej Zary
no flags Details
dmesg (34.82 KB, text/plain)
2010-04-22 17:07 EDT, Ondrej Zary
no flags Details
X log (199.77 KB, text/plain)
2010-04-22 17:08 EDT, Ondrej Zary
no flags Details

  None (edit)
Description Ondrej Zary 2010-04-22 17:06:20 EDT
Description of problem:
When compiz is enabled with two monitors attached, rotating the desktop cube is broken (see screenshot). This is present at least on NV44A (GeForce 6200) and NV17 (GeForce4 MX 420).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Boot desktop-i386-20100418.17 with two monitors
2. Enable compiz
3. Rotate the desktop cube
Actual results:
Desktop cube broken.

Expected results:
Normal desktop cube.

Additional info:
Comment 1 Ondrej Zary 2010-04-22 17:07:10 EDT
Created attachment 408447 [details]
Comment 2 Ondrej Zary 2010-04-22 17:07:42 EDT
Created attachment 408448 [details]
Comment 3 Ondrej Zary 2010-04-22 17:08:05 EDT
Created attachment 408449 [details]
X log
Comment 4 Bug Zapper 2010-07-30 07:26:40 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
Comment 5 Adam Williamson 2010-10-07 15:37:20 EDT
Is this still valid for current 13/14? Thanks.
Comment 6 Bug Zapper 2011-06-02 10:58:37 EDT
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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: 
Comment 7 Bug Zapper 2011-06-27 11:48:48 EDT
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

Note You need to log in before you can comment on or make changes to this bug.