GNOME Bugzilla – Bug 309618
GDK critical warnings when starting up evolution
Last modified: 2013-09-13 12:24:52 UTC
Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `GDK_IS_GC (gc)' failed aborting... Program received signal SIGTRAP, Trace/breakpoint trap.
+ Trace 61603
Thread NaN (LWP 5028)
trace looks unique.
I'm seeing a problem with evolution and the backtrace in this bug suggests this is the same issue. I'm using evolution 2.3.8 and gtk+ 2.8.3. When run from the commandline, evolution seems to hang, and the only output is the following: --- cut --- adding hook target 'source' Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object --- cut --- Running it through gdb ends with a segfault and the following backtrace can be retrieved: Program received signal SIGSEGV, Segmentation fault.
+ Trace 62709
Thread 16384 (LWP 9430)
As a work-around, I tried the following patch, which seems to work, and now at least I can run evolution: --- evolution-2.3.8/widgets/misc/e-canvas-background.c 2005-08-22 05:52:55.000000000 -0500 +++ evolution-2.3.8-patched/widgets/misc/e-canvas-background.c 2005-09-01 23:13:54.000000000 -0500 @@ -427,6 +427,7 @@ ecb_style_set (ECanvasBackground *ecb, GtkStyle *previous_style) { GnomeCanvasItem *item = GNOME_CANVAS_ITEM (ecb); + g_return_if_fail (ecb->priv->gc != NULL); gdk_gc_set_foreground (ecb->priv->gc, >K_WIDGET(item->canvas)->style->base[GTK_STATE_NORMAL]); gnome_canvas_item_request_update (GNOME_CANVAS_ITEM (ecb)); } However, I suspect the problem may be related to Gtk+, as evolution worked correctly with Gtk+ 2.8.0. Please let me know if you want me to specify more information, I'd be glad to. Thanks.
Getting an identical backtrace as in comment #2 with the only exception that instead of "realloc ()" I have "pango_cairo_fc_font_get_type ()" - the corrupt stack possibility warning is there aswell. The problem appeared after upgrading to gtk+-2.8.3 from 2.8.2. gnome-volume-manager, gnome-applets, pmount and gnome-session were upgraded around the same time.
Still seeing the warnings here with 2.4.1.
*** Bug 323518 has been marked as a duplicate of this bug. ***
Fix committed to HEAD.