GNOME Bugzilla – Bug 494830
crash in Tasks: starting Evolution
Last modified: 2007-11-11 12:10:34 UTC
Version: 2.10 What were you doing when the application crashed? starting Evolution 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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 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: 125595648 vsize: 125595648 resident: 34832384 share: 28221440 rss: 34832384 rss_rlim: 4294967295 CPU usage: start_time: 1194489148 rtime: 71 utime: 64 stime: 7 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 -1208535328 (LWP 30257)] [New Thread -1231029360 (LWP 30273)] [New Thread -1325438064 (LWP 30270)] [New Thread -1241519216 (LWP 30262)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 176214
Thread 1 (Thread -1208535328 (LWP 30257))
----------- .xsession-errors (107543 sec old) --------------------- Album: Gershwin Songbooks Year: 1959 Comment: Track: 17 Genre: Jazz ========================================================================== Opening audio decoder: [mp3lib] MPEG layer-2, layer-3 AUDIO: 44100 Hz, 2 ch, s16le, 224.0 kbit/15.87% (ratio: 28000->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 193.0 (03:13.0) ??,?% A: 0.0 (00.0) of 193.0 (03:13.0) ??,?% A: 0.0 (00.0) of 193.0 (03:13.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 ***