GNOME Bugzilla – Bug 471813
crash in Tasks: fetching mail
Last modified: 2007-09-24 18:28:07 UTC
Version: 2.10 What were you doing when the application crashed? fetching mail 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 146427904 vsize: 146427904 resident: 34734080 share: 28241920 rss: 34734080 rss_rlim: 4294967295 CPU usage: start_time: 1188475839 rtime: 81 utime: 73 stime: 8 cutime:2 cstime: 5 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 -1208355104 (LWP 20373)] [New Thread -1304458352 (LWP 20402)] [New Thread -1252009072 (LWP 20396)] [New Thread -1241519216 (LWP 20395)] [New Thread -1231029360 (LWP 20394)] [New Thread -1219257456 (LWP 20393)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 159049
Thread 1 (Thread -1208355104 (LWP 20373))
----------- .xsession-errors (132214 sec old) --------------------- Album: Comin' On With The Quintet Year: 1965 Comment: Track: 1 Genre: Jazz ========================================================================== Opening audio decoder: [mp3lib] MPEG layer-2, layer-3 AUDIO: 44100 Hz, 2 ch, s16le, 128.0 kbit/9.07% (ratio: 16000->176400) Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-3) ========================================================================== AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Video: no video Starting playback... A: 0.0 (00.0) of 444.0 (07:24.0) ??,?% A: 0.0 (00.0) of 444.0 (07:24.0) ??,?% A: 0.1 (00.0) of 444.0 (07:24.0) ??, ...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 ***