GNOME Bugzilla – Bug 487732
crash in Tasks: fetching pop mail
Last modified: 2007-10-22 22:24:44 UTC
Version: 2.10 What were you doing when the application crashed? fetching pop 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 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: 118992896 vsize: 118992896 resident: 37548032 share: 29249536 rss: 37548032 rss_rlim: 4294967295 CPU usage: start_time: 1192670573 rtime: 128 utime: 117 stime: 11 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 -1209157920 (LWP 22164)] [New Thread -1232077936 (LWP 22243)] [New Thread -1295017072 (LWP 22180)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 171008
Thread 1 (Thread -1209157920 (LWP 22164))
----------- .xsession-errors (183447 sec old) --------------------- mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Playing /home/web/Music/5/13 Good for the Soul.mp3. Audio file file format detected. ========================================================================== 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 987.0 (16:27.0) ??,?% A: 0.0 (00.0) of 987.0 (16:27.0) ??,?% A: 0.1 (00.0) of 987.0 (16:27.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 ***