GNOME Bugzilla – Bug 309397
Evolution crashes at first startup
Last modified: 2005-07-07 08:59:51 UTC
On a freshly build (with jhbuild) evolution from CVS evolution crashes at first time startup (i.e. when it's asking for your name etc) when I have to specify the type of server. If I then select a server evolution crashes. This is what evolution gives on the command line ----------------------------------- es menu class init adding hook target 'source' (evolution-2.4:4808): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed (evolution-2.4:4808): GLib-GObject-CRITICAL **: g_value_get_pointer: assertion `G_VALUE_HOLDS_POINTER (value)' failed (evolution-2.4:4808): GLib-GObject-CRITICAL **: g_value_get_pointer: assertion `G_VALUE_HOLDS_POINTER (value)' failed (evolution-2.4:4808): Gtk-CRITICAL **: gtk_window_set_type_hint: assertion `!GTK_WIDGET_VISIBLE (window)' failed (evolution-2.4:4808): Gtk-WARNING **: gtk_window_set_wmclass: shouldn't set wmclass after window is realized! (evolution-2.4:4808): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed (evolution-2.4:4808): GLib-GObject-CRITICAL **: g_value_get_pointer: assertion `G_VALUE_HOLDS_POINTER (value)' failed (evolution-2.4:4808): GLib-GObject-CRITICAL **: g_value_get_pointer: assertion `G_VALUE_HOLDS_POINTER (value)' failed (evolution-2.4:4808): GLib-GObject-CRITICAL **: g_value_get_pointer: assertion `G_VALUE_HOLDS_POINTER (value)' failed (evolution-2.4:4808): GLib-GObject-CRITICAL **: g_value_get_pointer: assertion `G_VALUE_HOLDS_POINTER (value)' failed This a backtrace produced by bug-buddy -------------------- Backtrace was generated from '/opt/gnome2/bin/evolution-2.4' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1229510176 (LWP 4851)] [New Thread -1237660752 (LWP 4853)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 61578
Thread 1 (Thread -1229510176 (LWP 4851))
*** This bug has been marked as a duplicate of 307794 ***