GNOME Bugzilla – Bug 452516
crash in Movie Player: I don
Last modified: 2007-08-08 23:35:53 UTC
Version: 2.18.1 What were you doing when the application crashed? I don't know 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: Clearlooks Icon Theme: Fedora Memory status: size: 221048832 vsize: 221048832 resident: 69505024 share: 24801280 rss: 69505024 rss_rlim: 4294967295 CPU usage: start_time: 1183198470 rtime: 3393 utime: 3041 stime: 352 cutime:11 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/totem' (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 -1208444304 (LWP 5196)] [New Thread -1345795184 (LWP 5214)] [New Thread -1334682736 (LWP 5209)] [New Thread -1324192880 (LWP 5208)] [New Thread -1313703024 (LWP 5207)] [New Thread -1291478128 (LWP 5205)] [New Thread -1279763568 (LWP 5204)] [New Thread -1265124464 (LWP 5203)] [New Thread -1254634608 (LWP 5202)] (no debugging symbols found) 0x005cf402 in __kernel_vsyscall ()
+ Trace 144822
Thread 1 (Thread -1208444304 (LWP 5196))
----------- .xsession-errors (4478 sec old) --------------------- 1976: 43 35 94 11 5b dc 4c f6 1984: 93 3a 4b 2a c6 f1 75 62 1992: e8 87 2b e3 f ed bb a5 2000: 7c 14 f1 7f 86 7c 3f e2 2008: 1f 5 ea 1a 7d de af e5 2016: 4b 22 ea 3e 24 f0 fd 93 2024: c1 b da 4d 36 f0 92 ea 2032: 20 fc b3 42 6d d9 e4 f2 2040: e1 2e af b2 59 f 94 b2 2048: 80 6a a7 c2 cf 8b fe 20 2056: f1 2f 83 3c 47 aa 78 af 2064: c3 fe 1e d6 ac ac bc 49 2072: a7 ea b3 d8 db 36 a4 3 ---------=======================---- ...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 the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 426990 ***