After upgrading to x11-libs/gtk+-2.16.0 and gnome-base/gnome-panel-2.26.0 notification icons using GtkStatusIcon appear as gray rectangles in the notification area when the Composite extension is enabled (using an Nvidia graphic card trying both nv and nvidia drivers). Icons which still use libegg are not affected, so this should be related to the new RGBA support introduced in both gtk+ and gnome-panel. Upgrading Xorg to ~arch fixes the issue. As stable Xorg will apparently be upgraded soon, this will hopefully be a non-issue when gnome-2.26 hits the tree. Nevertheless it took me almost a week to figure this one out, so I thought I'd share ...
what do you want us to do about it ? Without knowing which lib or program is making this an issue there is not much we can do. CCing x11 guys.
(In reply to comment #1) > what do you want us to do about it ? Without knowing which lib or program is > making this an issue there is not much we can do. Quite frankly, I did not expect you to do anything - recent changes to GTK+ (and gnome-panel) seem to require a version of Xorg > 7.2. According to this (http://blogs.gentoo.org/remi/2009/03/30/xorg-1-5-3-is-going-stable) post, Xorg can be expected to be updated pretty soon, which should fix the issue, so putting any work into this bug would be pretty much useless. So my suggestion would be to leave the bug "as is" as documentation for people running into the issue, and to close it when Xorg has stabilized.
I don't really like the uncertainty it leaves wrt dependencies minimums but we tried to figure out it for libxklavier-3.8 too and couldn't. I guess I should just bite the bullet for now.
RGBA/Composite support in servers prior to 1.4 is just broken. And I wouldn't bet on 1.4 doing the right thing either. I definitely suggest waiting for Xorg 1.5 to go stable. For the record, it's already stable on ppc and ppc64. amd64 folks are working on it. Hopefully, x86 shouldn't take more than a week or two. Thanks
Acknowledged that after Xorg upgrade the issue is fixed. Thanks.
Xorg 1.5.3 is stable on all major arches. Let's just assume this bug is history. If you can still reproduce the bug after upgrading to 1.5.3, don't hesitate to reopen this bug. Thanks