GNOME Bugzilla – Bug 446350
crash in Tasks: Sorting Sent messages by...
Last modified: 2007-06-12 01:03:25 UTC
What were you doing when the application crashed? Sorting Sent messages by name Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 257093632 vsize: 257093632 resident: 148008960 share: 25300992 rss: 148008960 rss_rlim: 4294967295 CPU usage: start_time: 1181052367 rtime: 198080 utime: 140106 stime: 57974 cutime:1 cstime: 41 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 -1208658208 (LWP 9910)] [New Thread -1264591984 (LWP 9946)] [New Thread -1295197296 (LWP 9945)] [New Thread -1230685296 (LWP 9930)] (no debugging symbols found) 0x00583402 in __kernel_vsyscall ()
+ Trace 140043
Thread 1 (Thread -1208658208 (LWP 9910))
----------- .xsession-errors --------------------- CConn: Throughput 20030 kbit/s - changing to full colour CConn: Using pixel format depth 24 (32bpp) little-endian rgb888 CConn: Using hextile encoding (evolution:9910): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:9910): camel-WARNING **: camel_exception_get_id called with NULL parameter. warning: .dynamic section for "/usr/lib/evolution/2.10/libeshell.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libnm_glib.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 431342 ***