GNOME Bugzilla – Bug 465600
crash in Tasks:
Last modified: 2007-08-18 14:17:49 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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 134549504 vsize: 134549504 resident: 48226304 share: 32104448 rss: 48226304 rss_rlim: 4294967295 CPU usage: start_time: 1186784190 rtime: 9606 utime: 9484 stime: 122 cutime:2 cstime: 9 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 -1208715552 (LWP 2679)] [New Thread -1272980592 (LWP 15070)] [New Thread -1228903536 (LWP 2781)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 154371
Thread 1 (Thread -1208715552 (LWP 2679))
----------- .xsession-errors (27064 sec old) --------------------- [mpeg4 @ 0x11d91a4]marker does not match f_code [mpeg4 @ 0x11d91a4]marker does not match f_code [mpeg4 @ 0x11d91a4]marker does not match f_code [mpeg4 @ 0x11d91a4]marker does not match f_code [mpeg4 @ 0x11d91a4]marker does not match f_code [mpeg4 @ 0x11d91a4]marker does not match f_code [mpeg4 @ 0x11d91a4]marker does not match f_code [mpeg4 @ 0x11d91a4]marker does not match f_code [mpeg4 @ 0x11d91a4]marker does not match f_code [mpeg4 @ 0x11d91a4]marker does not match f_code [mpeg4 @ 0x11d91a4]marker does not match f_code [mpeg4 @ 0x11d91a4]marker does not match f_code [mpeg4 @ 0x11d91a4]marker does not match f_code ...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 the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 431459 ***