GNOME Bugzilla – Bug 514387
crash in Tasks: I was moving mail from m...
Last modified: 2008-02-05 08:23:43 UTC
Version: 2.10 What were you doing when the application crashed? I was moving mail from my Inbox to another folder that I had just created. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 132665344 vsize: 132665344 resident: 54259712 share: 33730560 rss: 54259712 rss_rlim: 4294967295 CPU usage: start_time: 1202139877 rtime: 4770 utime: 4358 stime: 412 cutime:7964 cstime: 477 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 -1208781088 (LWP 4691)] [New Thread -1299190896 (LWP 6166)] [New Thread -1351640176 (LWP 6165)] [New Thread -1271948400 (LWP 5155)] [New Thread -1282499696 (LWP 4720)] [New Thread -1219286128 (LWP 4709)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 188086
Thread 1 (Thread -1208781088 (LWP 4691))
----------- .xsession-errors (1245646 sec old) --------------------- Channels : 1 Sample Rate : 11025 Time: 00:00.74 [00:01.35] of 00:02.09 ( 35.6%) Output Buffer: 35.52K Time: 00:01.49 [00:00.60] of 00:02.09 ( 71.1%) Output Buffer: 71.19K Time: 00:02.09 [00:00.00] of 00:02.09 ( 100.0%) Output Buff Done. Input File : '/usr/share/amsn/skins/default/sounds/online.wav' Sample Size : 16-bit (2 bytes) Sample Encoding: signed (2's complement) Channels : 1 Sample Rate : 11025 ...Too much output, ignoring rest... --------------------------------------------------
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 447591 ***