GNOME Bugzilla – Bug 420000
crash in Movie Player: launching 30mb wmv.wm mo...
Last modified: 2007-05-01 05:58:55 UTC
Version: 2.16.2 What were you doing when the application crashed? launching 30mb wmv.wm movie totem got as far as showing the movie title in title bar then crash Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 154451968 vsize: 0 resident: 154451968 share: 0 rss: 33267712 rss_rlim: 0 CPU usage: start_time: 1174277854 rtime: 0 utime: 138 stime: 0 cutime:122 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 -1225611600 (LWP 12381)] [New Thread -1343927392 (LWP 12399)] [New Thread -1327793248 (LWP 12393)] [New Thread -1319400544 (LWP 12392)] [New Thread -1309119584 (LWP 12391)] [New Thread -1296626784 (LWP 12390)] [New Thread -1287963744 (LWP 12389)] [New Thread -1279534176 (LWP 12386)] [New Thread -1263031392 (LWP 12385)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 119934
Thread 5 (Thread -1309119584 (LWP 12391))
Useful info perhaps... I double clicked the file to play, and I consistently get the crash. If I open Totem first however, then choose to open a file from Movie > Open and open the same movie file that was causing the crash, it works ok.
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 364037 ***