GNOME Bugzilla – Bug 574983
crash in Movie Player:
Last modified: 2009-03-11 19:38:19 UTC
Version: 2.22.2 What were you doing when the application crashed? Distribution: Debian squeeze/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: ClearlooksClassic Icon Theme: iComity Memory status: size: 628899840 vsize: 628899840 resident: 42823680 share: 16285696 rss: 42823680 rss_rlim: 18446744073709551615 CPU usage: start_time: 1236798582 rtime: 174 utime: 161 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/totem' [Thread debugging using libthread_db enabled] [New Thread 0x7fac0a788750 (LWP 13942)] [New Thread 0x43bf3950 (LWP 13950)] [New Thread 0x433f2950 (LWP 13949)] [New Thread 0x42bf1950 (LWP 13948)] [New Thread 0x423f0950 (LWP 13947)] [New Thread 0x41bef950 (LWP 13946)] [New Thread 0x40a57950 (LWP 13945)] [New Thread 0x413ee950 (LWP 13944)] 0x00007fac061c4384 in __lll_lock_wait () from /lib/libpthread.so.0
+ Trace 213390
Thread 3 (Thread 0x433f2950 (LWP 13949))
----------- .xsession-errors (6 sec old) --------------------- sh: mpg123: command not found sh: mpg123: command not found Got Event! 22, -1 (totem:13942): GStreamer-CRITICAL **: gst_caps_is_fixed: assertion `GST_IS_CAPS (caps)' failed (totem:13942): GStreamer-CRITICAL **: gst_caps_is_empty: assertion `GST_IS_CAPS (caps)' failed (totem:13942): GStreamer-CRITICAL **: gst_caps_is_any: assertion `GST_IS_CAPS (caps)' failed (totem:13942): GStreamer-CRITICAL **: gst_caps_is_empty: assertion `GST_IS_CAPS (caps)' failed (totem:13942): GStreamer-CRITICAL **: gst_caps_is_any: assertion `GST_IS_CAPS (caps)' failed (totem:13942): GStreamer-CRITICAL **: gst_caps_copy: assertion `GST_IS_CAPS (caps)' failed --------------------------------------------------
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 555631 ***