GNOME Bugzilla – Bug 460996
crash in Tasks: Accessing E-mail
Last modified: 2007-07-28 13:10:22 UTC
Version: 2.10 What were you doing when the application crashed? Accessing E-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.20-2925.11.fc7xen #1 SMP Mon Jun 11 16:21:08 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: 172048384 vsize: 172048384 resident: 37875712 share: 14962688 rss: 37875712 rss_rlim: 4294967295 CPU usage: start_time: 1185517675 rtime: 45873 utime: 44615 stime: 1258 cutime:17 cstime: 77 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 -1208809760 (LWP 4002)] [New Thread -1274868848 (LWP 4455)] [New Thread -1264223344 (LWP 4086)] [New Thread -1226249328 (LWP 4047)] (no debugging symbols found) 0x00cd2402 in __kernel_vsyscall ()
+ Trace 150995
Thread 1 (Thread -1208809760 (LWP 4002))
----------- .xsession-errors (52 sec old) --------------------- (evolution:4002): GConf-CRITICAL **: gconf_client_set_string: assertion `val != NULL' failed (evolution:4002): e-data-server-CRITICAL **: e_source_get_uri: assertion `E_IS_SOURCE (source)' failed (evolution:4002): GConf-CRITICAL **: gconf_client_set_string: assertion `val != NULL' failed ** 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 --------------------------------------------------
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 426227 ***