GNOME Bugzilla – Bug 486051
[playbin] gaim/pidgin suddenly stalls
Last modified: 2009-01-23 01:54:13 UTC
(11:24:33) msim: msim_markup_xmlnode_to_gtkhtml: RETURNING <p><font face='Perpetua' size='0'><i><font color='#ff0080'><span style='background-color: rgba(255, 255, 255, 0)'>Homemade peanut butter cookies are the best! And yeah it's very weird down here.</p></font></font></i></p> (11:24:33) msim: msim_markup_to_html: returning <p><font face='Perpetua' size='0'><i><font color='#ff0080'><span style='background-color: rgba(255, 255, 255, 0)'>Homemade peanut butter cookies are the best! And yeah it's very weird down here.</p></font></font></i></p> (11:24:33) docklet: created (11:24:33) docklet: embedded (11:24:34) gstreamer: Internal GStreamer error: state change failed. Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer. (gaim:13099): GStreamer-CRITICAL **: Trying to dispose element play, but it is not in the NULL state. You need to explicitly set elements to the NULL state before dropping the final reference, to allow them to clean up. (11:24:34) gstreamer: Internal GStreamer error: state change failed. Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer. (gaim:13099): GStreamer-CRITICAL **: gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed (11:24:34) GLib-GObject: invalid uninstantiatable type `(null)' in cast to `GstObject' (gaim:13099): GStreamer-CRITICAL **: gst_object_unref: assertion `((GObject *) object)->ref_count > 0' failed (11:24:34) GLib-GObject: invalid uninstantiatable type `(null)' in cast to `GstPlayBaseBin'
Can you reproduce this problem? If yes, could you run pidgin like this from a terminal/command line like this: $ export G_DEBUG=fatal_warnings $ gdb --args /usr/bin/pidgin Welcome to the GNU debugger .. blablabla (gdb) run ... wait for warning, gdb should abort ... (gdb) bt ... copy and paste the output here into the bug report please ... (gdb) thread apply all ... if possible, also copy and paste the output from here ... (gdb) kill (gdb) quit If you know how to, it would be great if you could install GLib and GStreamer debug packages before you do that (libglib2.0-dbg and libgstreamer0.10-dbg on debian/ubuntu).
*** Bug 477086 has been marked as a duplicate of this bug. ***
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
(pidgin:25261): GStreamer-CRITICAL **: Trying to dispose element play, but it is not in the NULL state. You need to explicitly set elements to the NULL state before dropping the final reference, to allow them to clean up. (pidgin:25261): GStreamer-CRITICAL **: gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed (pidgin:25261): GStreamer-CRITICAL **: gst_object_unref: assertion `((GObject *) object)->ref_count > 0' failed (pidgin:25261): GStreamer-CRITICAL **: gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed (pidgin:25261): GStreamer-CRITICAL **: gst_object_unref: assertion `((GObject *) object)->ref_count > 0' failed (pidgin:25261): GStreamer-CRITICAL **: gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed (pidgin:25261): GStreamer-CRITICAL **: gst_object_unref: assertion `((GObject *) object)->ref_count > 0' failed [Thread 0x41fda950 (LWP 25297) exited] ^C Program received signal SIGINT, Interrupt.
+ Trace 198153
Thread 140330179667696 (LWP 25261)
I interrupted it when pidgin was completely hung. I'm using gstreamer 0.10.19 and gst-plugins-base 0.10.19 GNOME 2.22 & Pidgin 2.4.2 (same issue with 2.4.1)
So this bug is still valid... could someone follow Tim's instructions to get a useful backtrace? > $ export G_DEBUG=fatal_warnings > $ gdb --args /usr/bin/pidgin > Welcome to the GNU debugger .. blablabla > (gdb) run > ... wait for warning, gdb should abort ... > (gdb) bt > ... copy and paste the output here into the bug report please ... > (gdb) thread apply all > ... if possible, also copy and paste the output from here ... > (gdb) kill > (gdb) quit