GNOME Bugzilla – Bug 150259
crash with composite when editing toolbars
Last modified: 2005-01-21 14:26:01 UTC
1. $epiphany (Excute epiphany in gnome-terminal) 2. Click Edit menu 3. Click Toobar menu 4. epiphany 1.3.5 crash. 5. Error messages displayed below . (epiphany:14833): GLib-GObject-WARNING **: g_type_get_private() requires a prior call to g_type_add_private() (epiphany:14833): Gdk-CRITICAL **: file gdkdraw.c: line 265 (gdk_drawable_set_colormap): assertion `cmap == NULL || gdk_drawable_get_depth (drawable) == cmap->visual->depth' failed (epiphany:14833): Gdk-WARNING **: gdkpixbuf-drawable.c:1248: Source drawable has no colormap; either pass in a colormap, or set the colormap on the drawable with gdk_drawable_set_colormap() (epiphany:14833): Gdk-CRITICAL **: file gdkdraw.c: line 265 (gdk_drawable_set_colormap): assertion `cmap == NULL || gdk_drawable_get_depth (drawable) == cmap->visual->depth' failed (epiphany:14833): Gdk-WARNING **: gdkpixbuf-drawable.c:1248: Source drawable has no colormap; either pass in a colormap, or set the colormap on the drawable with gdk_drawable_set_colormap() The program 'epiphany' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 6106 error_code 8 request_code 70 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
X server version is xorg-x11-6.7.99.2-5.
Not reproducible for me, using ephy 1.3.5 with gtk+ 2.4.8 (cvs). If those warnings are reproducible, can you please start epiphany with "--g-fatal-warnings" argument, and get a trace from it?
Removed composite option in /etc/X11/xorg.conf, this problem disappear.
*** Bug 152488 has been marked as a duplicate of this bug. ***
*** Bug 164185 has been marked as a duplicate of this bug. ***
Same as bug 159767 but that one has better info so we'll keep this one closed.