The dbus stuff is a message by the KUniqueApplication constructor - it tries 
to connect to "it's own" dbus service and fails since amarok is either not up 
(in quite some time) or has already crashed. (The background is to ensure the 
*unique* application runs only once ;-)

I do not think this is really your problem. If amarok crashes (happened 
randomly due to some Automated Playlist stuff, i unfortunately deleted the 
traces...), inspect the backtrace and make a bugreport.

Cheers,
Thomas

Am Thursday 12 August 2010 schrieb Donn Washburn:
>   I am becoming very afraid that KDE4/DBus and all of it headache are
> going to kill amarok.  This come from a very recent git of Amarok and
> getting all of the left out depends solved.  It seems permission to use
> DBus is a possible cause.
> openSuSE Version came up but is missing mp3 support
> 
> ~> amarok
> <unknown program name>(717)/: Communication problem with  "amarok" , it
> probably crashed.
> Error message was: "org.freedesktop.DBus.Error.ServiceUnknown" : " "The
> name org.kde.amarok was not provided by any .service files" "
> KCrash: Application 'amarok' crashing...
> sock_file=/home/donn/.kde4/socket-m1l/kdeinit4__0
> 
> 
> Yes it did crash.  There was a few error mentioning plasma during the
> compile.
> 
> Good news VLC works

_______________________________________________
Amarok mailing list
Amarok@kde.org
https://mail.kde.org/mailman/listinfo/amarok