GNOME Bugzilla – Bug 478264
crash in Tasks:
Last modified: 2007-09-24 17:38:08 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 115036160 vsize: 115036160 resident: 35332096 share: 28504064 rss: 35332096 rss_rlim: 4294967295 CPU usage: start_time: 1190173460 rtime: 107 utime: 97 stime: 10 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 -1208277280 (LWP 6537)] [New Thread -1251554416 (LWP 8062)] [New Thread -1293968496 (LWP 6549)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 163916
Thread 1 (Thread -1208277280 (LWP 6537))
----------- .xsession-errors (102692 sec old) --------------------- Album: The Road To You Year: 1993 Comment: Greetings from JazzySOB Track: 8 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 305.0 (05:05.0) ??,?% A: 0.0 (00.0) of 305.0 (05:05.0) ??,?% A: 0.0 (00.0) of 305.0 (05:05.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 ***