GNOME Bugzilla – Bug 501736
crash in Tasks:
Last modified: 2007-12-06 01:47:33 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.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: 185327616 vsize: 185327616 resident: 87760896 share: 44277760 rss: 87760896 rss_rlim: 4294967295 CPU usage: start_time: 1196854755 rtime: 7198 utime: 6786 stime: 412 cutime:29 cstime: 12 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 -1208424736 (LWP 5698)] [New Thread -1293169776 (LWP 5890)] [New Thread -1229972592 (LWP 5768)] [New Thread -1230562416 (LWP 5718)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 180815
Thread 1 (Thread -1208424736 (LWP 5698))
----------- .xsession-errors (6322 sec old) --------------------- mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Playing file:///home/ldormoy/.evolution/cache/tmp/evolution-tmp-Qq8bY7/msg0000.WAV. Audio file file format detected. ========================================================================== Opening audio decoder: [msgsm] native GSM/MSGSM audio decoder AUDIO: 8000 Hz, 1 ch, s16le, 13.0 kbit/10.16% (ratio: 1625->16000) Selected audio codec: [msgsm] afm: msgsm (MS GSM) ========================================================================== AO: [alsa] 48000Hz 1ch s16le (2 bytes per sample) Video: no video Starting playback... A: 0.0 (00.0) of 21.0 (21.0) ??,?% A: 0.0 (00.0) of 21.0 (21.0) ??,?% A: 0.0 (00.0) of 21.0 (21.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 440388 ***