GNOME Bugzilla – Bug 331743
Evolution crashes on first start
Last modified: 2013-09-13 00:58:50 UTC
Steps to reproduce: 1. Start Evolution as a user without an existing profile Stack trace: Backtrace was generated from '/usr/bin/evolution-2.6' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1230522704 (LWP 11053)] 0xffffe410 in ?? ()
+ Trace 66313
Thread 1 (Thread -1230522704 (LWP 11053))
Other information: Running latest released versions of all Gnome 2.13 packages, including evolution-data-server 1.5.91 and evolution 2.5.91. On running Evolution (either from menu or terminal), it crashes prior to any UI being shown, bringing up the crash reporter. This occurs only for a new user, i.e create a new user, login to Gnome as that user, and run Evolution. If I reboot into a second partition to run an older version of Evolution (2.5.5.1) as that user, it runs the usual new-user setup, after which subsequent attempts to run 2.5.91 work fine. When run from a terminal, the following output is produced. The CalDAV message occurs before the "this is a development release" popup message, everything after that occurs after that popup is closed. (evolution-2.6:11079): Gdk-WARNING **: locale not supported by Xlib (evolution-2.6:11079): Gdk-WARNING **: cannot set locale modifiers CalDAV Eplugin starting up ... GLib-GObject-CRITICAL **: g_value_get_pointer: assertion `G_VALUE_HOLDS_POINTER (value)' failed aborting... (gnome_segv:11080): Gdk-WARNING **: locale not supported by Xlib (gnome_segv:11080): Gdk-WARNING **: cannot set locale modifiers
I'm seeing this too, even in Evolution-2.7.x (CVS HEAD).
Created attachment 66918 [details] [review] evolution-331743-emap-scroll-adjustments.diff This fixes the problem. We were using the wrong signal marshaller, and the obsolete gtk_signal_new().
Looks good. Please commit to both HEAD and the gnome-2-14 branch. Thanks for the patch.
Committed to gnome-2-14 and HEAD. 2006-06-07 Federico Mena Quintero <federico@novell.com> * e-map.c (e_map_class_init): Don't use gtk_signal_new() for the set_scroll_adjustments signal, and use the correct marshaler. Fixes bug #331743.
Huh... I'd completely forgotten logging this bug until a flurry of email appeared today. Well, good to see it fixed...