GNOME Bugzilla – Bug 519786
crash in Tasks:
Last modified: 2008-03-01 21:09:53 UTC
Version: 2.10 What were you doing when the application crashed? 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.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 168976384 vsize: 168976384 resident: 65003520 share: 33013760 rss: 65003520 rss_rlim: 4294967295 CPU usage: start_time: 1204399046 rtime: 251 utime: 231 stime: 20 cutime:0 cstime: 1 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 -1208432928 (LWP 25411)] [New Thread -1333224560 (LWP 25448)] [New Thread -1261442160 (LWP 25438)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 190983
Thread 1 (Thread -1208432928 (LWP 25411))
----------- .xsession-errors (174799 sec old) --------------------- Channels : 1 Sample Rate : 22050 Time: 00:00.37 [00:01.37] of 00:01.74 ( 21.3%) Output Buffer: 17.76K Time: 00:00.74 [00:01.00] of 00:01.74 ( 42.6%) Output Buffer: 35.60K Time: 00:01.11 [00:00.63] of 00:01.74 ( 63.9%) Output Buffe Done. Input File : '/usr/share/sounds/ekiga/voicemail.wav' Sample Size : 16-bit (2 bytes) Sample Encoding: signed (2's complement) Channels : 1 Sample Rate : 22050 Time: 00:00.37 [00:01.37] of 00:01.74 ( 21.3%) Output Buffer: 17.76K Time: 00:00.74 [00:01.00] of 00:01.74 ( 42.6%) Output Buffer: 35.60K Time: 00:01.11 [00:00.63] of 00:01.74 ( 63.9%) Output Buffe ...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 364700 ***