GNOME Bugzilla – Bug 612378
crash in Movie Player: Clicked the Time slider.
Last modified: 2010-05-02 10:59:21 UTC
Version: 2.28.5 What were you doing when the application crashed? Clicked the Time slider. Distribution: Debian squeeze/sid Gnome Release: 2.28.2 2009-12-18 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.32-2-686 #1 SMP Thu Feb 11 04:08:42 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10705000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 153264128 vsize: 153264128 resident: 39817216 share: 24162304 rss: 39817216 rss_rlim: 18446744073709551615 CPU usage: start_time: 1268195299 rtime: 3001 utime: 2568 stime: 433 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/totem' [Thread debugging using libthread_db enabled] [New Thread 0xb14a3b70 (LWP 6811)] [New Thread 0xb1ca4b70 (LWP 6808)] [New Thread 0xb24a5b70 (LWP 6802)] [New Thread 0xb2cf8b70 (LWP 6801)] [New Thread 0xafbc1b70 (LWP 6800)] [New Thread 0xb03c2b70 (LWP 6799)] [New Thread 0xb4bc4b70 (LWP 6797)] [New Thread 0xb564db70 (LWP 6786)] 0xb7799424 in __kernel_vsyscall ()
+ Trace 220893
Thread 1 (Thread 0xb65a3750 (LWP 6785))
Inferior 1 [process 6785] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] Output of custom script "/usr/lib/totem/totem/totem-bugreport.py": Please give a filename to typefind ----------- .xsession-errors (7641 sec old) --------------------- (firefox-bin:4242): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:4242): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:4242): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:4242): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:4242): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:4242): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:4242): Gdk-WARNING **: XID collision, trouble ahead ...Too much output, ignoring rest... --------------------------------------------------
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://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
*** Bug 617413 has been marked as a duplicate of this bug. ***
Marking as a dupe of bug #617413, since it's got a much better stacktrace. *** This bug has been marked as a duplicate of bug 617413 ***