GNOME Bugzilla – Bug 479049
crash in Tasks:
Last modified: 2007-09-29 01:37:53 UTC
Version: 2.10 What were you doing when the application crashed? 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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 258834432 vsize: 258834432 resident: 89186304 share: 30244864 rss: 89186304 rss_rlim: 4294967295 CPU usage: start_time: 1190396454 rtime: 10270 utime: 9099 stime: 1171 cutime:0 cstime: 0 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 -1208902928 (LWP 3025)] [New Thread -1320297584 (LWP 3416)] [New Thread -1340478576 (LWP 3385)] [New Thread -1270936688 (LWP 3198)] [New Thread -1331180656 (LWP 3190)] [New Thread -1249449072 (LWP 3112)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 164478
Thread 1 (Thread -1208902928 (LWP 3025))
----------- .xsession-errors (16 sec old) --------------------- Sample Rate : 11025 Time: 00:00.74 [00:00.67] of 00:01.41 ( 52.7%) Output Buffer: 8.19K Time: 00:01.41 [00:00.00] of 00:01.41 ( 100.0%) Output Buffer: 15.55K Done. Input File : '/usr/share/amsn/skins/default/sounds/type.wav' Sample Size : 16-bit (2 bytes) Sample Encoding: signed (2's complement) Channels : 1 Sample Rate : 11025 Time: 00:00.74 [00:00.67] of 00:01.41 ( 52.7%) Output Buffer: 8.19K Time: 00:01.41 [00:00.00] of 00:01.41 ( 100.0%) Output Buffer: 15.55K Done. --------------------------------------------------
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 467763 ***