GNOME Bugzilla – Bug 386353
crash in Movie Player: mirando george and drago...
Last modified: 2007-03-27 22:43:55 UTC
Version: 2.16.2 What were you doing when the application crashed? mirando george and dragon Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 89702400 vsize: 0 resident: 89702400 share: 0 rss: 23445504 rss_rlim: 0 CPU usage: start_time: 1166226653 rtime: 0 utime: 159 stime: 0 cutime:86 cstime: 0 timeout: 73 it_real_value: 0 frequency: 21 Backtrace was generated from '/usr/bin/totem' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226479952 (LWP 9867)] [New Thread -1285555296 (LWP 9876)] [New Thread -1270191200 (LWP 9873)] [New Thread -1261720672 (LWP 9872)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 94506
Thread 2 (Thread -1285555296 (LWP 9876))
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. Thanks in advance!
*** Bug 386754 has been marked as a duplicate of this bug. ***
*** Bug 386860 has been marked as a duplicate of this bug. ***
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 335288 ***
*** Bug 401338 has been marked as a duplicate of this bug. ***
*** Bug 414678 has been marked as a duplicate of this bug. ***
*** Bug 422713 has been marked as a duplicate of this bug. ***
*** Bug 422726 has been marked as a duplicate of this bug. ***
*** Bug 423087 has been marked as a duplicate of this bug. ***
*** Bug 423462 has been marked as a duplicate of this bug. ***