After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 649666 - Top menu bar is drawn as a rainbow and icons are not rasterized properly (ATI/fglrx)
Top menu bar is drawn as a rainbow and icons are not rasterized properly (ATI...
Status: RESOLVED INCOMPLETE
Product: gnome-shell
Classification: Core
Component: drivers
3.0.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-05-07 15:32 UTC by Thomas Dignan
Modified: 2013-01-06 19:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
fglrx screen shot (707.28 KB, image/png)
2011-07-05 13:09 UTC, Simon Wenner
Details

Description Thomas Dignan 2011-05-07 15:32:33 UTC
Issue:

When I start Gnome3, the top menu bar is composed of an odd horizontal rainbow gradient instead of the correct translucent black color. The icons are also not rasterized properly (they look perforated and dotty, grayscale). This problem persists unless I start gnome3 in fall back mode.

I have heard this problem can be avoided by using the open source Radeon driver. That's not an option, because radeon does not work well with 3d graphics at all on this system. Perhaps this is a problem with fglrx, if so, I really hope AMD will fix it!

Graphics Card:

02:00.0 VGA compatible controller: ATI Technologies Inc RV710 [Radeon HD 4350]

Kernel:

Linux tralfamadore 2.6.38-ARCH #1 SMP PREEMPT Tue May 3 07:40:34 CEST 2011 x86_64 AMD Phenom(tm) 9750 Quad-Core Processor AuthenticAMD GNU/Linux

Driver:

I'm using the catalyst-test drivers from arch linux's AUR. After examining the PKGBUILD, I found that it is using this installer: 

http://archive.ubuntu.com/ubuntu/pool/restricted/f/fglrx-installer/fglrx-installer_8.840.orig.tar.gz

Incase this helps, this is the entire PKGBUILD (maybe there is related information in it. I'm just including it for good measure) http://pastebin.ca/2054886


Other Details:

I am using multiple monitors on the same card. I believe this is called Big Desktop.

Thanks for your good work guys
Comment 1 Thomas Dignan 2011-05-08 12:06:24 UTC
To be clear, I mean the icons in the top menu specifically. Other icons work fine.
Comment 2 Rui Matos 2011-05-08 14:34:32 UTC
Can you post a screenshot?

In general the proprietary AMD drivers have always had problems with gnome-shell. If the latest mesa driver doesn't work for you I'd recommend you to file a bug at https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa .
Comment 3 Simon Wenner 2011-07-05 13:09:44 UTC
Created attachment 191316 [details]
fglrx screen shot

I'm affected by the same bug (see screenshot). The interface corruption starts with the top panel and its icons. If you use the shell longer the corruption spreads until all icons and even some interface elements get filled with random memory.

Gnome-Shell: 3.0.2
GPU: ATI Technologies Inc RV770 [Radeon HD 4850]
Driver: fglrx 1:11-6-2
Distro: Debian wheezy

This bug is probably the same issue:
https://bugzilla.gnome.org/show_bug.cgi?id=652029
Comment 4 Roderik 2011-08-23 02:17:54 UTC
I also have rainbow colored top bar and distorted icons (they do appear right when hovering though), also the icon from the active application show correctly.

Refreshing (ALT+F2, r) does not help for me.

Driver: AMD Catalyst 11.8
GPU: R5450 - MD512D3H/LP (MSI Radeon HD5450)
Distro: Fedora Core 15 x64

The odd thing is that applications do show up correctly, is there something special about displaying the bar?
Comment 5 André Klapper 2012-02-01 13:58:30 UTC
Is this still a problem in gnome-shell 3.2, and if so which driver and driver version do you use?
Comment 6 Florian Müllner 2012-08-23 17:47:21 UTC
Marking NEEDINFO as of comment #5
Comment 7 Tobias Mueller 2013-01-06 19:41:50 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!