GNOME Bugzilla – Bug 520009
crash in Movie Player: I was scrolling backward...
Last modified: 2008-05-10 14:15:40 UTC
Version: 2.20.3 What were you doing when the application crashed? I was scrolling backwards through the audio file, using the time slider. Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 2242043904 vsize: 2242043904 resident: 35569664 share: 14905344 rss: 35569664 rss_rlim: 4294967295 CPU usage: start_time: 1204508923 rtime: 3613 utime: 3399 stime: 214 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/totem' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6d146b0 (LWP 8049)] [New Thread 0xb2df3b90 (LWP 8095)] [New Thread 0xb3cfdb90 (LWP 8056)] [New Thread 0xb44feb90 (LWP 8055)] [New Thread 0xb4cffb90 (LWP 8054)] [New Thread 0xb5cb5b90 (LWP 8052)] [New Thread 0xb67c7b90 (LWP 8051)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 191102
Thread 4 (Thread 0xb44feb90 (LWP 8055))
----------- .xsession-errors (85 sec old) --------------------- checking for new mail (2008/03/02 18:47:54) no new messages ---------- checking for new mail (2008/03/02 18:48:20) no new messages ---------- checking for new mail (2008/03/02 18:48:48) no new messages ---------- checking for new mail (2008/03/02 18:49:18) no new messages ---------- checking for new mail (2008/03/02 18:49:46) no new messages ---------- checking for ne --------------------------------------------------
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 and reopen this bug or report a new one. Thanks in advance!
Dear sir, do I need to install the GDB debugging package in order to output symbols? Or do I only just append --debug to totem command from terminal? Thanks! Tom
(In reply to comment #2) > Dear sir, do I need to install the GDB debugging package in order to output > symbols? Or do I only just append --debug to totem command from terminal? You'll need to install totem-dbg and all the gstreamer0.10-*-dbg packages then reproduce the crash. Running Totem with --debug would also be helpful. :-) In short, do it all. Thanks.
*** Bug 524001 has been marked as a duplicate of this bug. ***
*** Bug 527244 has been marked as a duplicate of this bug. ***
*** Bug 532321 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 527572 ***