GNOME Bugzilla – Bug 536204
crash in Evolution Mail and Calendar: Inserting To:
Last modified: 2008-06-02 14:28:01 UTC
What were you doing when the application crashed? Inserting To: Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 109580288 vsize: 109580288 resident: 65589248 share: 10190848 rss: 65589248 rss_rlim: 4294967295 CPU usage: start_time: 1212399424 rtime: 541 utime: 489 stime: 52 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb664e9a0 (LWP 8670)] [New Thread 0xb58fdb90 (LWP 8918)] [New Thread 0xb63b0b90 (LWP 8672)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 199384
Thread 1 (Thread 0xb664e9a0 (LWP 8670))
----------- .xsession-errors (40 sec old) --------------------- (evolution:8662): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed (evolution:8662): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed (evolution:8662): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed (evolution:8662): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed (evolution:8662): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed (evolution:8662): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed (evolution:8662): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed BBDB spinning up... --------------------------------------------------
*** This bug has been marked as a duplicate of 512605 ***