GNOME Bugzilla – Bug 458810
crash in Tasks:
Last modified: 2007-07-21 21:35:56 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: 118710272 vsize: 118710272 resident: 46714880 share: 32702464 rss: 46714880 rss_rlim: 4294967295 CPU usage: start_time: 1184970445 rtime: 948 utime: 887 stime: 61 cutime:56 cstime: 16 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 -1208727840 (LWP 20920)] [New Thread -1273910384 (LWP 20961)] [New Thread -1242047600 (LWP 20959)] (no debugging symbols found) 0x00ef0402 in __kernel_vsyscall ()
+ Trace 149460
Thread 1 (Thread -1208727840 (LWP 20920))
----------- .xsession-errors (8 sec old) --------------------- (evolution:20920): e-dateedit.c-WARNING **: time_text:09:00 PM (evolution:20920): e-dateedit.c-WARNING **: time_text:09:00 PM (evolution:20920): e-dateedit.c-WARNING **: time_text:09:00 PM (evolution:20920): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed (evolution:20920): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed (evolution:20920): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed (evolution:20920): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed (evolution:20920): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 442949 ***