GNOME Bugzilla – Bug 521937
crash in Movie Player: wacthing a movie dvd!;
Last modified: 2008-03-12 19:01:51 UTC
Version: 2.20.0 What were you doing when the application crashed? wacthing a movie dvd!; 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: 155049984 vsize: 155049984 resident: 63860736 share: 14688256 rss: 63860736 rss_rlim: 4294967295 CPU usage: start_time: 1203965298 rtime: 176171 utime: 151157 stime: 25014 cutime:0 cstime: 0 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 0xa6cdd6b0 (LWP 9290)] [New Thread 0xa1f0eb90 (LWP 9319)] [New Thread 0xa2cffb90 (LWP 9318)] [New Thread 0xa36fbb90 (LWP 9317)] [New Thread 0xa3f48b90 (LWP 9314)] [New Thread 0xa4749b90 (LWP 9313)] [New Thread 0xa4fbbb90 (LWP 9312)] [New Thread 0xa5cdfb90 (LWP 9311)] [New Thread 0xa675eb90 (LWP 9306)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 192159
Thread 8 (Thread 0xa5cdfb90 (LWP 9311))
----------- .xsession-errors (3258 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 closing gnome-mount 0.6 ** Message: Error: Resource not found. gstfilesrc.c(971): gst_file_src_start (): /play/source: No such file "/media/New" closing gnome-mount 0.6 --------------------------------------------------
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 ***