GNOME Bugzilla – Bug 364844
crash in Movie Player: opening a wmv file
Last modified: 2006-10-27 15:32:21 UTC
Version: 2.16.2 What were you doing when the application crashed? opening a wmv file Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 129011712 vsize: 0 resident: 129011712 share: 0 rss: 30134272 rss_rlim: 0 CPU usage: start_time: 1161728910 rtime: 0 utime: 98 stime: 0 cutime:86 cstime: 0 timeout: 12 it_real_value: 0 frequency: 0 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 -1225365840 (LWP 28086)] [New Thread -1321419872 (LWP 28103)] [New Thread -1307980896 (LWP 28100)] [New Thread -1299588192 (LWP 28099)] [New Thread -1289307232 (LWP 28098)] [New Thread -1276814432 (LWP 28097)] [New Thread -1268151392 (LWP 28096)] [New Thread -1259758688 (LWP 28093)] [New Thread -1243341920 (LWP 28092)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 78132
Thread 5 (Thread -1289307232 (LWP 28098))
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. *** This bug has been marked as a duplicate of 364037 ***