GNOME Bugzilla – Bug 519665
crash in Tasks:
Last modified: 2008-03-01 09:43:19 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.14-60.fc7 #1 SMP Mon Jan 14 22:14:17 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 115183616 vsize: 115183616 resident: 34906112 share: 28258304 rss: 34906112 rss_rlim: 4294967295 CPU usage: start_time: 1204338940 rtime: 81 utime: 71 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 -1208260896 (LWP 11744)] [New Thread -1346417776 (LWP 11760)] [New Thread -1231029360 (LWP 11748)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 190909
Thread 1 (Thread -1208260896 (LWP 11744))
----------- .xsession-errors (1066777 sec old) --------------------- [mpeg4 @ 0x11481a4]header damaged [mpeg4 @ 0x11481a4]header damaged [mpeg4 @ 0x11481a4]header damaged [mpeg4 @ 0x11481a4]header damaged [mpeg4 @ 0x11481a4]header damaged [mpeg4 @ 0x11481a4]header damaged [mpeg4 @ 0x11481a4]header damaged [mpeg4 @ 0x11481a4]header damaged [mpeg4 @ 0x11481a4]header damaged [mpeg4 @ 0x11481a4]header damaged [mpeg4 @ 0x11481a4]header damaged [mpeg4 @ 0x11481a4]header damaged [mpeg4 @ 0x11481a4]header damaged ...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 ***