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

[Loïc Minier]

        Hi,

On Thu, Jun 23, 2005, Andreas Pakulat wrote:
> Do you use alsasink or artsdsink? I (normally) use the latter...

 I'm using osssink, I tried with artsdsink and esdsink too.  As I said,
 my crashes happens while initializing gstasf, prior to doing anything
 within amarok.

> > > (process:16763): GStreamer-WARNING **: pushing data on non-negotiat=
ed pad mad1:src, not allowed.
> >  Please try to run "gst-launch-0.8 filesrc location=/home/foo/bar.m=
p3 !
> >  spider ! audioscale ! audioconvert ! alsasink",
> Ok, now if I do use alsasink (which I normally don't) everythings fine.
> But if I use artsdsink I get the same output as mentioned before. Now I
> first thought that it might be due to the manual setting of 48KHz in
> artsd (which is necessary to work around a crash-bug between artsd and
> libasound) but even with no manual setting of the frequency artsdsink
> has the problems. The same is true when using alsasink from within
> amarok. So this bug is more about gstreamer and artsdsink,than gstreame=
r
> and amarok... 

 If you use artsdsink in the above pipeline and it doesn't work, that's
 a GStreamer bug, let's focus on this bug.

 Could you send me the output of the whole pipeline?  I'll forward it
 upstream.

> So for the artsd-Stuff, I do use KDE3.4.1 from experimental, I could tr=
y
> to get at least arts from unstable at the weekend and check wether it
> works or not.

 Please do that first, thanks.

      Bye,

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