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 561911 - Gtk draw ops are trying to draw to an incorrect depth on ARGB windows
Gtk draw ops are trying to draw to an incorrect depth on ARGB windows
Status: RESOLVED DUPLICATE of bug 568365
Product: metacity
Classification: Other
Component: Iain's compositor
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Metacity compositor maintainers
Metacity compositor maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-22 13:25 UTC by iain
Modified: 2009-01-29 16:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description iain 2008-11-22 13:25:34 UTC 
Quoth:

I have seen something similar to this in my own themes, where if:

 - Metacity's compositor is enabled
 - A client window is using an RGBA visual (such as gnome-terminal)
 - GTK+ based draw_ops don't appear (such as gtk_arrow, gtk_box, or gtk_vline)

Also may be relevant: I found this in ~/.xsession:

Window manager warning: Log level 8: gtk_paint_arrow: assertion `style->depth
== gdk_drawable_get_depth (window)' failed
Comment 1 Thomas Thurman 2008-11-23 14:04:49 UTC 
*** Bug 550670 has been marked as a duplicate of this bug. ***
Comment 2 Thomas Thurman 2008-11-23 14:09:13 UTC 
Iain, is this related to bug 513944?
Comment 3 iain 2008-11-23 14:14:19 UTC 
Hmm, it could be, although 513944 says that it happens when the compositor is turned off, which would mean that frame windows were always depth 24.
Comment 4 Screwtape 2009-01-29 11:16:32 UTC 
Fixed by bug 568365?
Comment 5 Thomas Thurman 2009-01-29 15:12:02 UTC 
I believe so, yes.

*** This bug has been marked as a duplicate of 568385 ***
Comment 6 Thomas Thurman 2009-01-29 16:55:34 UTC 
er, typo.

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