Bug#314762: libgstreamer0.8-0: last update breaks amarok

[Loïc Minier]

        Hi,

On Thu, Jun 23, 2005, Andreas Pakulat wrote:
> (process:8297): GStreamer-CRITICAL **: gst_object_check_uniqueness: ass=
ertion `name != NULL' failed
> (process:8297): GStreamer-WARNING **: Name (null) is not unique in bin =
pipeline0, not adding
> FÃœHRE Leitung AUS ...
> (process:8297): GStreamer-WARNING **: pushing data on non-negotiated pa=
d mad0:src, not allowed.

 Reading this upstream report:
    <http://bugzilla.gnome.org/show_bug.cgi?id=167283>
 with this fix:
    <http://bugzilla.gnome.org/attachment.cgi?id=37433&action=view>

 makes me think that amarok is probably borken, if it arrives to such a
 situation.

 I propose we debug this together.

 First, it would be nice to get an amarok built with debugging symbols,
 this is easy to do by following:
    <http://wiki.debian.net/?HowToGetABacktrace>

 Once your ready, fire amarokapp from gdb like this:
    % gdb /usr/lib/amarok/amarokapp

 And set a break point on "g_log":

    (gdb) break g_log
    Function "g_log" not defined.
    Make breakpoint pending on future shared library load? (y or [n]) y

    Breakpoint 1 (g_log) pending.
    (gdb) run

 When you reach the break point, type "bt", or even "thread apply all bt
 full" in gdb, this will show you where the breakpoint was reached
 (when the log was printed).

 This will permit us to pinpoint when amarok calls gstreamer with a NULL
 pointer.

 When we're there, we'll eventually go up the stack trace, and debug the
 reason "name" is NULL, but let's try to get there first.

 Let me know if you need any help for this.

   Bye,

-- 
Loïc Minier <lool@dooz.org>
"Neutral President: I have no strong feelings one way or the other."