GNOME Bugzilla – Bug 368020
crash in Movie Player: Maximitzar totem
Last modified: 2006-10-31 19:39:14 UTC
Version: 2.16.2 What were you doing when the application crashed? Maximitzar totem Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 158445568 vsize: 0 resident: 158445568 share: 0 rss: 37236736 rss_rlim: 0 CPU usage: start_time: 1162254836 rtime: 0 utime: 290 stime: 0 cutime:274 cstime: 0 timeout: 16 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 -1225914704 (LWP 1875)] [New Thread -1325974624 (LWP 1913)] [New Thread -1309144160 (LWP 1888)] [New Thread -1300751456 (LWP 1887)] [New Thread -1290470496 (LWP 1886)] [New Thread -1277977696 (LWP 1885)] [New Thread -1269314656 (LWP 1884)] [New Thread -1260885088 (LWP 1883)] [New Thread -1244505184 (LWP 1882)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 80748
Thread 1 (Thread -1225914704 (LWP 1875))
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://www.gnome.org/projects/totem/#bugs 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 351181 ***