GNOME Bugzilla – Bug 368660
crash in Movie Player: setting visualisation to...
Last modified: 2006-11-02 00:42:15 UTC
Version: 2.16.2 What were you doing when the application crashed? setting visualisation to large Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 159121408 vsize: 0 resident: 159121408 share: 0 rss: 40321024 rss_rlim: 0 CPU usage: start_time: 1162346675 rtime: 0 utime: 583 stime: 0 cutime:546 cstime: 0 timeout: 37 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 -1225259344 (LWP 10199)] [New Thread -1348031584 (LWP 10210)] [New Thread -1328206944 (LWP 10207)] [New Thread -1319814240 (LWP 10206)] [New Thread -1309533280 (LWP 10205)] [New Thread -1297040480 (LWP 10204)] [New Thread -1288377440 (LWP 10203)] [New Thread -1279947872 (LWP 10202)] [New Thread -1263572064 (LWP 10201)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 81264
Thread 1 (Thread -1225259344 (LWP 10199))
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 ***