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

[Andreas Pakulat]

On 21.Jun 2005 - 22:35:07, Loïc Minier wrote:
> On sam, jun 18, 2005, Andreas Pakulat wrote:
> > today I did an upgrade of my sid system and with it came a new version
> > of libgstreamer. Now this broke amarok, amarok seems to be playing, but
> > I can't hear anything. Also the marker moves extremely fast, a 3 minute
> > song is done in a few seconds. This does not happen with version 0.8.9-2
> 
>  Ok, I finally installed kde and can reproduce the problem.  Amarok died
>  because of a SIGFPE (Floating Point Exception) in libgstasf. 

Hmm, I hope you don't mean that amarok completely dies (like "crashes")?
Because it doesn't here. What I see on the Xterm is:

QObject::connect: Cannot connect Engine::Base::statusText( const QString& ) to (null)::shortMessage( const QString& )
QObject::connect: Cannot connect Engine::Base::infoMessage( const QString& ) to (null)::longMessage( const QString& )
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow

(process:16763): GStreamer-CRITICAL **: gst_object_check_uniqueness: assertion `name != NULL' failed

(process:16763): GStreamer-WARNING **: Name (null) is not unique in bin thread1, not adding

Caps negotiation succeeded with 1 Hz @ 1 channels
Caps negotiation succeeded with 1 Hz @ 1 channels
Caps negotiation succeeded with 1 Hz @ 1 channels
STARTUP

And after starting to play:

(process:16763): GStreamer-WARNING **: pushing data on non-negotiated pad mad1:src, not allowed.

floods the XTerm.

>  A temporary workaround is to move gstasf away and run gst-register-0.8
>  and gst-compprep-0.8, but you want be able to use that plugin anymore.

How would I do that? apt-file did not find any gstasf. I guess I have to
rebuilt gstreamer?

Andreas

-- 
You will be aided greatly by a person whom you thought to be unimportant.