GNOME Bugzilla – Bug 336254
GtkTreeItem broken
Last modified: 2006-05-13 22:04:35 UTC
Yes, I know it's deprecated, but I'm currently hacking on an old application which still uses the GtkTree classes (and which still needs the GtkTree code by GtkTreeView etc). The attached demo application throws out a lot of warnings which should be fixed IMHO (having errors that always appear makes finding new ones very hard).
Created attachment 62161 [details] c source file This simple file throws out these warnings: (demo:24665): Gdk-CRITICAL **: gdk_drawable_get_depth: assertion `GDK_IS_DRAWABLE (drawable)' failed (demo:24665): Gtk-CRITICAL **: gtk_pixmap_set: assertion `gdk_colormap_get_visual (gtk_widget_get_colormap (GTK_WIDGET (pixmap)))->depth == gdk_drawable_get_depth (GDK_DRAWABLE (val))' failed (demo:24665): Gdk-CRITICAL **: gdk_drawable_get_depth: assertion `GDK_IS_DRAWABLE (drawable)' failed (demo:24665): Gtk-CRITICAL **: gtk_pixmap_set: assertion `gdk_colormap_get_visual (gtk_widget_get_colormap (GTK_WIDGET (pixmap)))->depth == gdk_drawable_get_depth (GDK_DRAWABLE (val))' failed
Here's a stack trace:
+ Trace 67281
Created attachment 62162 [details] [review] Patch Proposed patch. gtk_pixmap_finalize() calls gtk_pixmap_set(pixmap, NULL, NULL), so val is not always a GDK_DRAWABLE()
2006-03-28 Sven Herzberg <herzi@gnome-de.org> reviewed by: Tim Janik * gtk/gtkpixmap.c: (gtk_pixmap_set): only check for equal colormaps if the new pixmap is not NULL; fixes a warning when gtk_pixmap_set is called from gtk_pixmap_finalize (bug 336254)
Was this a regression in just a certain GTK version(s)? If that's the case, then what versions of GTK are affected? I have reports of the same problems after some wxGTK changes, and I'm inclined to believe some GTK+ upgrades just happened at the same time, to temporarily introduce these warnings which will be fixed in a later GTK+-2.8.x version. Is this the case?
look for changes to gtk_pixmap_set in ChangeLog
Thanks, I found that 2.8.14, 2.8.15 and 2.8.16 are affected with the warning, and 2.8.17 has it fixed from the patch from this bugzilla entry.
*** Bug 335424 has been marked as a duplicate of this bug. ***