Bug 707842 - Glitchy white lines above notification area in Fedora 15 on ATI HD5450(RV810)
Summary: Glitchy white lines above notification area in Fedora 15 on ATI HD5450(RV810)
Keywords:
Status: CLOSED DUPLICATE of bug 704822
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11
Version: 15
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-26 06:39 UTC by Zhang, Yin
Modified: 2011-05-27 07:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-27 07:57:31 UTC
Type: ---


Attachments (Terms of Use)
Screenshot of the white lines (394.41 KB, image/png)
2011-05-26 06:39 UTC, Zhang, Yin
no flags Details

Description Zhang, Yin 2011-05-26 06:39:34 UTC
Created attachment 500994 [details]
Screenshot of the white lines

Description of problem:
I have a computer with an Intel GMA 3100 integrated graphic card and an ATI HD5450 graphic card. When I unplug the HD5450 graphic card, Fedora 15 works well. But if I plug in the HD5450 graphic card, there are glitchy white lines above the notification area, and somewhere else, such as the screen shows up when I click on the "Activities" button. These lines also show up when I use the live CD version of Fedora 15 with the HD5450 graphic card. I've also test live CD on another computer with an ATI HD2400 graphic card, but Fedora 15 runs well and no glitchy lines show up.

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


How reproducible:
Run Fedora 15 using an ATI HD5450 graphic card


Steps to Reproduce:
1.Plugin an ATI HD5450 graphic card
2.Boot the computer with Fedora 15 live CD
3.
  
Actual results:
Glithcy white lines show up over notification area.

Expected results:
No such white lines.

Additional info:

Comment 1 Dave Airlie 2011-05-27 07:57:31 UTC

*** This bug has been marked as a duplicate of bug 704822 ***


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