GNOME Bugzilla – Bug 437625
crash in Movie Player: trying to resize in pref...
Last modified: 2007-05-12 11:06:31 UTC
Version: 2.16.2 What were you doing when the application crashed? trying to resize in preferences Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 141549568 vsize: 0 resident: 141549568 share: 0 rss: 39432192 rss_rlim: 0 CPU usage: start_time: 1178862510 rtime: 0 utime: 1275 stime: 0 cutime:1245 cstime: 0 timeout: 30 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 -1225292112 (LWP 12035)] [New Thread -1328190560 (LWP 12046)] [New Thread -1310635104 (LWP 12045)] [New Thread -1302242400 (LWP 12044)] [New Thread -1291961440 (LWP 12043)] [New Thread -1279468640 (LWP 12042)] [New Thread -1270805600 (LWP 12041)] [New Thread -1262412896 (LWP 12038)] [New Thread -1245942880 (LWP 12037)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 133611
Thread 1 (Thread -1225292112 (LWP 12035))
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!
After the interesting yak-shaving exercise getting all necessary development packages installed, I built totem 2.16.6 from source with debug configured on. Here are the resulting backtraces. BTW if you think it is video dependent I can probably upload it; its around 51M Backtrace was generated from '/usr/local/bin/totem' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1225234768 (LWP 31544)] [New Thread -1328698464 (LWP 31557)] [New Thread -1310598240 (LWP 31556)] [New Thread -1302205536 (LWP 31555)] [New Thread -1291924576 (LWP 31554)] [New Thread -1279431776 (LWP 31553)] [New Thread -1270768736 (LWP 31552)] [New Thread -1262376032 (LWP 31547)] [New Thread -1245885536 (LWP 31546)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 133741
Thread 1 (Thread -1225234768 (LWP 31544))
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 ***