Bug 582746 - Trouble when switching monitor resolutions while running glxgears under compiz
Summary: Trouble when switching monitor resolutions while running glxgears under compiz
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 14
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-15 17:27 UTC by Alexander E. Patrakov
Modified: 2012-02-20 22:08 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-02-20 22:08:40 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Alexander E. Patrakov 2010-04-15 17:27:37 UTC 
Description of problem:
I tried to follow
http://fedoraproject.org/wiki/QA:Testcase_intelvideo_glx , see BZ #582712 for exact configuration. While the testcases indicated in that page worked correctly, attempting to rearrange the two monitors while glxgears are rotating under compiz leads to graphical corruption.

Steps to Reproduce:
1. Move the Sony TV (DVI1, 1920x1080) to the right of the VGA1 monitor (1280x1024).
2. Enable desktop effects, run glxgears.
3. Move the Sony TV to the left of the VGA1 monitor, click Apply.
  
Actual results:
Corrupted image (dark-blue stripes) at the bottom of the TV.

Expected results:
Just the normal background there, as this area was never covered by glxgears.
Comment 1 Bug Zapper 2010-07-30 11:21:43 UTC 
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:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 2 Adam Williamson 2010-10-06 22:02:22 UTC 
I think the assignment of this bug to F14 is a mistake, as it was part of the F13 test day.
Comment 3 Adam Jackson 2012-02-20 22:08:40 UTC 
F14 is EOL.  Please reopen this if you can reproduce the issue on F16 or newer.
Note You need to log in before you can comment on or make changes to this bug.