GNOME Bugzilla – Bug 486085
crash in Tasks: Copying a message from t...
Last modified: 2007-11-15 19:31:19 UTC
Version: 2.10 What were you doing when the application crashed? Copying a message from the input to another folder 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-prw1 #1 PREEMPT Tue Oct 2 18:52:00 BST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 670556160 vsize: 670556160 resident: 75501568 share: 48873472 rss: 75501568 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192208625 rtime: 2042 utime: 1928 stime: 114 cutime:0 cstime: 3 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 47910045628656 (LWP 27647)] [New Thread 1191237968 (LWP 7354)] [New Thread 1082132816 (LWP 7226)] [New Thread 1099184464 (LWP 7212)] [New Thread 1090525520 (LWP 27656)] 0x00002b92e17df97f in waitpid () from /lib64/libpthread.so.0
+ Trace 169780
Thread 2 (Thread 1191237968 (LWP 7354))
----------- .xsession-errors --------------------- CamelFolder:get_message('prw', '915') = class: CamelMimeMessage mime-type: multipart/alternative; boundary=MIMEBoundaryf25f8e567eb048bceb8e8ff507ac676e content class: CamelMultipart content mime-type: multipart/alternative; boundary=MIMEBoundaryf25f8e567eb048bceb8e8ff507ac676e class: CamelMimePart mime-type: text/plain; charset=ISO-8859-1 content class: CamelDataWrapper content mime-type: text/plain; charset=ISO-8859-1 class: CamelMimePart mime-type: text/html; charset=ISO-8859-1 warning: the debug information found in "/usr/lib/debug//usr/lib64/libdbus-glib-1.so.2.1.0.debug" does not match "/usr/lib64/libdbus-glib-1.so.2" (CRC mismatch). --------------------------------------------------
*** This bug has been marked as a duplicate of 427105 ***