GNOME Bugzilla – Bug 386625
crash in Movie Player: Played an mpc file
Last modified: 2006-12-17 17:59:31 UTC
Version: 2.16.2 What were you doing when the application crashed? Played an mpc file Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 154968064 vsize: 0 resident: 154968064 share: 0 rss: 34545664 rss_rlim: 0 CPU usage: start_time: 1166305419 rtime: 0 utime: 12411 stime: 0 cutime:11975 cstime: 0 timeout: 436 it_real_value: 0 frequency: 5 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 -1225759056 (LWP 11750)] [New Thread -1359471712 (LWP 12911)] [New Thread -1315107936 (LWP 12907)] [New Thread -1334293600 (LWP 12906)] [New Thread -1393296480 (LWP 12836)] [New Thread -1306715232 (LWP 12745)] [New Thread -1289929824 (LWP 12744)] [New Thread -1270928480 (LWP 12743)] [New Thread -1298322528 (LWP 12742)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 94715
Thread 6 (Thread -1306715232 (LWP 12745))
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!
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. If you could make the file that caused this crash available to us somehow (for example put it up on a website) that would be very helpful. Also, if you could do $ sudo apt-get install libgstreamer0.10-0-dbg gstreamer0.10-plugins-base-dbg gstreamer0.10-plugins-good-dbg gstreamer0.10-plugins-ugly*dbg gstreamer0.10-plugins-bad*dbg and then try to do the crash again (and create a new stack trace with bug buddy), that would also be very useful. Thanks! *** This bug has been marked as a duplicate of 378130 ***