GNOME Bugzilla – Bug 495713
crash in Tasks: Had just forwarded an em...
Last modified: 2007-11-11 12:05:27 UTC
Version: 2.10 What were you doing when the application crashed? Had just forwarded an email with a large (XLS) attachment, then did File-Exit. That's when Evolution crashed (on normal exit.) I have debugging packages installed, so I hope that helps you. 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 207958016 vsize: 207958016 resident: 79867904 share: 61976576 rss: 79867904 rss_rlim: 4294967295 CPU usage: start_time: 1194551438 rtime: 3095 utime: 2886 stime: 209 cutime:282 cstime: 37 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208629536 (LWP 4814)] [New Thread -1274020976 (LWP 5891)] [New Thread -1357137008 (LWP 5056)] [New Thread -1272644720 (LWP 4864)] 0x00110402 in __kernel_vsyscall ()
+ Trace 176886
Thread 2 (Thread -1274020976 (LWP 5891))
----------- .xsession-errors (13 sec old) --------------------- Exiting... (Exit) BBDB spinning up... (evolution:4814): e-data-server-DEBUG: Loading categories from "/home/jhall/.evolution/categories.xml" (evolution:4814): e-data-server-DEBUG: Loaded 29 categories (evolution:4814): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail' camel-Message: -- ERROR: ld.so: object 'libjvm.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libawt.so' from LD_PRELOAD cannot be preloaded: ignored. in emp_apps_open_in in emp_apps_open_in inside eab_vcard_control_new inside eab_vcard_control_new inside eab_vcard_control_new --------------------------------------------------
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 445309 ***