GNOME Bugzilla – Bug 472563
crash in Tasks:
Last modified: 2007-09-06 15:18:15 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 150265856 vsize: 150265856 resident: 57511936 share: 34889728 rss: 57511936 rss_rlim: 4294967295 CPU usage: start_time: 1188657324 rtime: 2170 utime: 1983 stime: 187 cutime:2 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208158496 (LWP 11678)] [New Thread -1269834864 (LWP 12394)] [New Thread -1226191984 (LWP 11902)] [New Thread -1297081456 (LWP 11900)] (no debugging symbols found) 0x0050c402 in __kernel_vsyscall ()
+ Trace 159642
Thread 2 (Thread -1269834864 (LWP 12394))
----------- .xsession-errors --------------------- (evolution:11678): e-data-server-ui-CRITICAL **: e_source_combo_box_set_active_uid: assertion `gtk_tree_row_reference_valid (reference)' failed (evolution:11678): libebook-CRITICAL **: file e-book.c: line 3807: assertion `source && E_IS_SOURCE (source)' failed (evolution:11678): libebook-CRITICAL **: e_book_get_source: assertion `book && E_IS_BOOK (book)' failed (evolution:11678): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (evolution:11678): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (evolution:11678): libebook-CRITICAL **: e_book_async_open: assertion `book && E_IS_BOOK (book)' failed in emp_apps_open_in in emp_apps_open_in in emp_apps_open_in in emp_apps_open_in --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance! *** This bug has been marked as a duplicate of 464223 ***