GNOME Bugzilla – Bug 521938
crash in Movie Player: watching the movies!
Last modified: 2008-03-12 19:02:07 UTC
Version: 2.20.0 What were you doing when the application crashed? watching the movies! Distribution: Debian 3.1 (sarge) Gnome Release: 2.20.0 2007-09-21 (Debian) BugBuddy Version: 2.20.0 System: Linux 2.6.16-1-686 #2 Thu May 4 18:22:23 UTC 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 169267200 vsize: 169267200 resident: 61235200 share: 14569472 rss: 61235200 rss_rlim: 4294967295 CPU usage: start_time: 1203959986 rtime: 282316 utime: 250542 stime: 31774 cutime:0 cstime: 1 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 0xa6d846b0 (LWP 7259)] [New Thread 0xa06efb90 (LWP 7330)] [New Thread 0xa1f3ab90 (LWP 7327)] [New Thread 0xa2761b90 (LWP 7311)] [New Thread 0xa2faeb90 (LWP 7303)] [New Thread 0xa37afb90 (LWP 7302)] [New Thread 0xa3fb0b90 (LWP 7300)] [New Thread 0xa47b1b90 (LWP 7299)] [New Thread 0xa5023b90 (LWP 7293)] [New Thread 0xa5d47b90 (LWP 7285)] [New Thread 0xa6805b90 (LWP 7277)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 192160
Thread 10 (Thread 0xa5d47b90 (LWP 7285))
----------- .xsession-errors (34823 sec old) --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 Gtk-WARNING **: Failed to load module "libgnomebreakpad.so": libgnomebreakpad.so: cannot open shared object file: No such file or directory Gtk-WARNING **: Unable to locate loadable module in module_path: "libraleigh.so", Gtk-WARNING **: Unable to locate loadable module in module_path: "libraleigh.so", Message: device: default --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 358891 ***