[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Amarok Crashing ...



On Fri, 2005-08-05 at 11:50 +0200, Hervé Piedvache wrote:
> Hi,
> 
> I'm using SID ... and on several computers since last update ... I get this 
> message from Amarok ....
> 
> #amarok
> amaroK: [Loader] Starting amarokapp..
> amaroK: [Loader] Don't run gdb, valgrind, etc. against this binary! Use 
> amarokapp.
> 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
> KCrash: Application 'amarok' crashing...
> 
> Is there any solution ?
> 

I had a similar problem to this, but I can't remember if it was the
exact same message. Anyway, the problem for me was that I was configured
to use artsd. There is some issue at the moment (not sure if it's artsd
or amarok), but anyway, if you find your:
~/.kde/share/config/amarokrc
edit the engine (called "Sound System" in the config file) to be
gstreamer or xine-engine (or anything other than arts). Make sure that
if you change to gstreamer, that your output plugin is not set to arts.

That did it for me anyway. Good luck.

Regards,
Andrew



Reply to: