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 606210 - With RGBA enabled by default, the Nautilus desktop is broken
With RGBA enabled by default, the Nautilus desktop is broken
Status: RESOLVED INCOMPLETE
Product: gnome-desktop
Classification: Core
Component: libgnome-desktop
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Desktop Maintainers
Desktop Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-01-06 14:47 UTC by Cody Russell
Modified: 2012-10-16 09:40 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Proposed patch (383 bytes, patch)
2010-01-06 14:50 UTC, Cody Russell 		none Details | Review

Description Cody Russell 2010-01-06 14:47:41 UTC 
When I have enabled RGBA colormaps by default in GTK+ for client-side-decorations [1], Nautilus desktop drawing is broken due to colormap mismatches and stuff when creating the pixmaps.

There are two components of this: Nautilus itself, and GnomeBG from libgnomedesktop.


[1]. https://bugzilla.gnome.org/show_bug.cgi?id=587475
Comment 1 Cody Russell 2010-01-06 14:50:18 UTC 
Created attachment 150893 [details] [review]
Proposed patch
Comment 2 Matthias Clasen 2010-01-06 15:28:35 UTC 
I must say that this feels like a bug in gdk somewhere. If the system colormap is RGBA, then either get_default_colormap should return that instead of NULL, or setting a NULL colormap on a drawable should use the system colormap (what else ?)
Comment 3 Cody Russell 2010-01-06 15:41:21 UTC 
No, the *system* colormap is RGB and that doesn't change with my gtk+ patch.  The default colormap is currently RGB, and my patch changes it to RGBA.
Comment 4 Cody Russell 2010-01-06 15:42:00 UTC 
Also for tracking purposes, here is the Nautilus bug/patch:

https://bugzilla.gnome.org/show_bug.cgi?id=606212
Comment 5 Bastien Nocera 2012-06-20 14:32:52 UTC 
Is this still a problem with GNOME3?
Comment 6 Tobias Mueller 2012-10-16 09:40:18 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!