GNOME Bugzilla – Bug 521347
crash in Tasks: Checking HTML setting in...
Last modified: 2008-03-10 09:46:23 UTC
Version: 2.10 What were you doing when the application crashed? Checking HTML setting in the prefrences section of Evolution email client. 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.21-7.fc7xen #1 SMP Tue Feb 12 12:32:24 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 133332992 vsize: 133332992 resident: 25251840 share: 15224832 rss: 25251840 rss_rlim: 4294967295 CPU usage: start_time: 1205051472 rtime: 1775 utime: 1632 stime: 143 cutime:2 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208375584 (LWP 14216)] [New Thread -1260528752 (LWP 14243)] [New Thread -1249641584 (LWP 14241)] (no debugging symbols found) 0x00cce402 in __kernel_vsyscall ()
+ Trace 191847
Thread 1 (Thread -1208375584 (LWP 14216))
----------- .xsession-errors (172 sec old) --------------------- ** (gnome-help:14808): WARNING **: failure: no device event controller found. ** (gnome-help:14808): WARNING **: failure: no device event controller found. ** (gnome-help:14808): WARNING **: failure: no device event controller found. (gnome-help:14808): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed (evolution:14216): 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... --------------------------------------------------
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 447591 ***