GNOME Bugzilla – Bug 495372
crash in Tasks: Closing Evolution
Last modified: 2007-12-06 05:04:05 UTC
Version: 2.10 What were you doing when the application crashed? Closing Evolution 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.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 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: 146837504 vsize: 146837504 resident: 62660608 share: 44023808 rss: 62660608 rss_rlim: 4294967295 CPU usage: start_time: 1194625723 rtime: 1840 utime: 1730 stime: 110 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 -1208772896 (LWP 11787)] [New Thread -1282094192 (LWP 11800)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 176619
Thread 1 (Thread -1208772896 (LWP 11787))
----------- .xsession-errors (90 sec old) --------------------- ** (gnome-help:12026): WARNING **: failure: no device event controller found. (gnome-help:12026): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed Unmatched element: br (gnome-help:12243): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed (evolution:11787): 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... (evolution:11787): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa0f9008' (evolution:11787): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa0f9128' Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x360267e (My baby's ); these messages lack timestamps and therefore suck. --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 447591 ***