GNOME Bugzilla – Bug 392448
crash in Movie Player:
Last modified: 2007-01-23 02:08:54 UTC
Version: 2.16.4 What were you doing when the application crashed? Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 170569728 vsize: 0 resident: 170569728 share: 0 rss: 54091776 rss_rlim: 0 CPU usage: start_time: 1167852302 rtime: 0 utime: 16433 stime: 0 cutime:15719 cstime: 0 timeout: 714 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 -1225300304 (LWP 13732)] [New Thread -1356858464 (LWP 13742)] [New Thread -1329079392 (LWP 13741)] [New Thread -1320686688 (LWP 13740)] [New Thread -1310405728 (LWP 13739)] [New Thread -1297912928 (LWP 13738)] [New Thread -1289249888 (LWP 13737)] [New Thread -1280820320 (LWP 13736)] [New Thread -1264448608 (LWP 13735)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 99109
Thread 6 (Thread -1297912928 (LWP 13738))
Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug. Also, 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 308251 ***