GNOME Bugzilla – Bug 454137
crash in Tasks:
Last modified: 2007-09-29 00:06:58 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 159834112 vsize: 159834112 resident: 53137408 share: 41660416 rss: 53137408 rss_rlim: 4294967295 CPU usage: start_time: 1183685668 rtime: 120 utime: 108 stime: 12 cutime:0 cstime: 1 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 -1208789280 (LWP 10906)] [New Thread -1266136176 (LWP 10928)] [New Thread -1244763248 (LWP 10927)] [New Thread -1234273392 (LWP 10924)] (no debugging symbols found) 0x0076c402 in __kernel_vsyscall ()
+ Trace 146021
Thread 1 (Thread -1208789280 (LWP 10906))
----------- .xsession-errors (36495 sec old) --------------------- Selected audio codec: [ffwmav2] afm: ffmpeg (DivX audio v2 (FFmpeg)) ========================================================================== AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... VDec: vo config request - 640 x 480 (preferred colorspace: Planar YV12) VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is undefined - no prescaling applied. VO: [xv] 640x480 => 640x480 Planar YV12 A: 3.0 V: 3.0 A-V: 0.030 ct: 0.000 1/ 1 ??% ??% ??,?% 0 0 A: 3.1 V: 3.0 A-V: 0.019 ct: -0.003 2/ 2 ??% ??% ??,?% 0 0 A: 3.1 V: 3.1 A-V: 0.007 ct: -0.0 A: 28.3 V: 28.1 A-V: 0.149 ct: 0.015 101/101 ??% ??% ??,?% 0 0 A: 28.3 V: 28.2 A-V: 0.159 ct: 0.018 102/102 ??% ??% ??,?% 0 0 A: 28.3 V: 28.2 A-V: 0.147 ct: 0.0 A: 78.3 V: 78.1 A-V: 0.211 ct: 0.021 153/153 ??% ??% ??,?% 0 0 A: 78.3 V: 78.1 A-V: 0.178 ct: 0.024 154/154 ??% ??% ??,?% 0 0 A: 78.3 V: 78.2 A-V: 0.167 ct: 0.0 A: 203.6 V: 203.1 A-V: 0.482 ct: 0.048 456/456 ??% ??% ??,?% 0 0 A: 203.6 V: 203.2 A-V: 0.448 ct: 0.052 457/457 ??% ??% ??,?% 0 0 A: 203.6 V: 203.2 A-V: 0.437 ct: 0.0 A: 253.2 V: 253.1 A-V: 0.130 ct: 0.013 525/525 ??% ??% ??,?% 0 0 A: 253.3 V: 253.1 A-V: 0.119 ct: 0.016 526/526 ??% ??% ??,?% 0 0 A: 253.3 V: 253.2 A-V: 0.107 ct: 0.0 A: 928.3 V: 928.1 A-V: 0.221 ct: 0.022 2282/2282 ??% ??% ??,?% 0 0 A: 928.4 V: 928.2 A-V: 0.210 ct: 0.025 2283/2283 ??% ??% ??,?% 0 0 A: 928.4 V: 928.2 A-V: 0.197 ct: 0.0 ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
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 431459 ***