GNOME Bugzilla – Bug 453120
crash in Tasks: Reading my morning email...
Last modified: 2007-07-02 22:29:25 UTC
Version: 2.10 What were you doing when the application crashed? Reading my morning emails; deleting a lot of them, as they are mostly just for information purposes and do not require a response. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (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: Crux Icon Theme: Crux Memory status: size: 249851904 vsize: 249851904 resident: 154812416 share: 43745280 rss: 154812416 rss_rlim: 4294967295 CPU usage: start_time: 1183386112 rtime: 1791 utime: 1419 stime: 372 cutime:41 cstime: 82 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 -1208420640 (LWP 18705)] [New Thread -1279087728 (LWP 19082)] [New Thread -1224983664 (LWP 19081)] [New Thread -1247618160 (LWP 18768)] [New Thread -1247351920 (LWP 18730)] [New Thread -1235477616 (LWP 18728)] (no debugging symbols found) 0x008dd402 in __kernel_vsyscall ()
+ Trace 145264
Thread 1 (Thread -1208420640 (LWP 18705))
----------- .xsession-errors (294957 sec old) --------------------- (evolution:27348): camel-WARNING **: camel_exception_get_id called with NULL parameter. I/O error : Permission denied I/O error : Permission denied I/O error : Permission denied I/O error : Permission denied I/O error : Permission denied I/O error : Permission denied I/O error : Permission denied I/O error : Permission denied I/O error : Permission denied I/O error : Permission denied I/O error : Permission denied I/O error : Permission denied ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us a stack trace with debugging symbols? Please install some debugging packages [1] and reproduce the crash, if possible. Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or simply report a new one. Thanks! [1] debugging packages for evolution, evolution-data-server and gtkhtml, plus debugging packages for glib, gtk+ and gnome-vfs, GNOME's main libraries
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 444924 ***