Bug 785707 - graphic artefacts with gnome-shell
Summary: graphic artefacts with gnome-shell
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-30 12:18 UTC by Pierre Ossman
Modified: 2013-02-13 20:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 20:20:23 UTC
Type: ---


Attachments (Terms of Use)
Screen shot of artefacts (720.18 KB, image/png)
2012-01-30 12:19 UTC, Pierre Ossman
no flags Details

Description Pierre Ossman 2012-01-30 12:18:58 UTC
Not sure if this is a graphics driver bug, or gnome-shell doing something wrong, but I've got to start somewhere so I'm filing it with gnome-shell for now.

Attached screen shot shows [at least] two kinds of graphical artefacts that I'm seeing in Fedora 16. The image is mainly the old X11 weave, which seems to provoke this bug fairly well.

The two artefacts are:

 a) Horizontal banding. I pulled out the levels tool as you can see in the screen shot, and even though the image is only supposed to contain pure black and pure white, you still get a bunch of not-quite-black and not-quite-white there. Dragging the window around keeps the banding stationary, so it seems the bug has something to do with the screen coordinates rather then window coordinates.

 b) Window trailing noise. This is most of the gunk in the screen shot. It was created by dragging the Levels dialog on top of the main gimp window. These artefacts tend to disappear now and then, so it seems like a full redraw of the window will remove them.

Hardware is a Radeon HD 4550 (RV710).

~
[ossman@ossman]$ rpm -q xorg-x11-drv-ati mesa-libGL libdrm gnome-shell clutter
xorg-x11-drv-ati-6.14.3-3.20111125git534fb6e41.fc16.x86_64
mesa-libGL-7.11.2-1.fc16.x86_64
mesa-libGL-7.11.2-1.fc16.i686
libdrm-2.4.27-2.fc16.x86_64
libdrm-2.4.27-2.fc16.i686
gnome-shell-3.2.1-2.fc16.x86_64
clutter-1.8.2-3.fc16.x86_64

Comment 1 Pierre Ossman 2012-01-30 12:19:36 UTC
Created attachment 558308 [details]
Screen shot of artefacts

Comment 2 Fedora End Of Life 2013-01-16 16:31:59 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 3 Fedora End Of Life 2013-02-13 20:20:27 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.


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