GNOME Bugzilla – Bug 508425
crash in Tasks: Exiting from evolution.
Last modified: 2008-01-10 22:41:26 UTC
Version: 2.10 What were you doing when the application crashed? Exiting from evolution. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 154820608 vsize: 154820608 resident: 58646528 share: 36016128 rss: 58646528 rss_rlim: 4294967295 CPU usage: start_time: 1199924904 rtime: 1914 utime: 1534 stime: 380 cutime:0 cstime: 0 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 -1208375584 (LWP 17036)] [New Thread -1275069552 (LWP 18689)] [New Thread -1310725232 (LWP 18679)] [New Thread -1261327472 (LWP 18214)] [New Thread -1239020656 (LWP 17041)] [New Thread -1228530800 (LWP 17040)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 184738
Thread 2 (Thread -1275069552 (LWP 18689))
----------- .xsession-errors (3214 sec old) --------------------- (evolution:16808): libebook-WARNING **: invalid escape, passing it through (evolution:16808): libebook-WARNING **: invalid escape, passing it through (evolution:16808): libebook-WARNING **: invalid escape, passing it through (evolution:16808): libebook-WARNING **: invalid escape, passing it through CalDAV Eplugin starting up ... (evolution:16808): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?) BBDB spinning up... ***MEMORY-ERROR***: evolution[16808]: GSlice: assertion failed: sinfo->n_allocated > 0 CalDAV Eplugin starting up ... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 339602 ***