GNOME Bugzilla – Bug 626340
crash in Movie Player: Opening an FLV file that...
Last modified: 2010-08-07 22:26:58 UTC
Version: 2.30.2 What were you doing when the application crashed? Opening an FLV file that was downloaded via youtube-dl script. Distribution: Gentoo Base System release 2.0.1 Gnome Release: 2.30.2 2010-07-01 (Gentoo) BugBuddy Version: 2.30.0 System: Linux 2.6.35-gentoo #1 SMP Fri Aug 6 10:00:17 CDT 2010 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10802000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: c2 Icon Theme: gnome GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 587649024 vsize: 587649024 resident: 47919104 share: 22659072 rss: 47919104 rss_rlim: 18446744073709551615 CPU usage: start_time: 1281215237 rtime: 352 utime: 256 stime: 96 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 0x7f1763b50710 (LWP 3728)] [New Thread 0x7f1764778710 (LWP 3714)] [New Thread 0x7f1774440710 (LWP 23295)] 0x00007f177f725cad in __libc_waitpid (pid=3729, stat_loc=<value optimized out>, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 223156
Thread 1 (Thread 0x7f1784b51880 (LWP 23294))
Inferior 1 [process 23294] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** GLib-GObject **: g_object_get: assertion `G_IS_OBJECT (object)' failed Output of custom script "/usr/libexec/totem/totem-bugreport.py": gst-typefind-0.10 version 0.10.30 GStreamer 0.10.30 Unknown package origin Listened to a "" file on 2010-08-02T18:28:14
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 bug 623318 ***