GNOME Bugzilla – Bug 470715
crash in Email: downloading e-mail
Last modified: 2007-10-11 18:18:51 UTC
Version: 2.10 What were you doing when the application crashed? downloading 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.22.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 620109824 vsize: 620109824 resident: 65040384 share: 55103488 rss: 65040384 rss_rlim: 18446744073709551615 CPU usage: start_time: 1188226801 rtime: 66 utime: 55 stime: 11 cutime:2 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496406672 (LWP 4506)] [New Thread 1115699536 (LWP 4577)] [New Thread 1084229968 (LWP 4544)] (no debugging symbols found) 0x0000003f9f00d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 158202
Thread 1 (Thread 46912496406672 (LWP 4506))
----------- .xsession-errors (14 sec old) --------------------- localuser:liliana being added to access control list SESSION_MANAGER=local/coreduo:/tmp/.ICE-unix/4274 winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running Initializing nautilus-search-tool extension ** Message: failed to load session from /home/liliana/.nautilus/savedl2h4Md CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:4506): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4506): DEBUG: mailto URL program: evolution --------------------------------------------------
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 ***