GNOME Bugzilla – Bug 486898
crash in Tasks: checking mail
Last modified: 2007-10-22 22:22:52 UTC
Version: 2.10 What were you doing when the application crashed? checking mail 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.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 141828096 vsize: 141828096 resident: 53805056 share: 40763392 rss: 53805056 rss_rlim: 4294967295 CPU usage: start_time: 1192469685 rtime: 806 utime: 718 stime: 88 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 -1208383776 (LWP 6568)] [New Thread -1325155440 (LWP 6704)] [New Thread -1234175088 (LWP 6574)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 170385
Thread 1 (Thread -1208383776 (LWP 6568))
----------- .xsession-errors (18 sec old) --------------------- (evolution:6568): GConf-CRITICAL **: gconf_client_set_string: assertion `val != NULL' failed I/O warning : failed to load external entity "/home/jonny/.gaim/blist.xml" bbdb: Could not open Gaim buddy list. ** Message: Clearing selection ** Message: Unsetting for Personal ** Message: Unsetting for Birthdays & Anniversaries ** Message: Setting for Personal ** Message: Clearing selection ** Message: Unsetting for Personal ** Message: Unsetting for Birthdays & Anniversaries ** Message: Setting for Personal ** Message: Setting for Birthdays & Anniversaries (evolution:6568): e-data-server-ui-WARNING **: Key file does not have key 'pop:__tcom%40tcomwireless.com@mail.tcomwireless.com_' --------------------------------------------------
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 364700 ***