From amarok Mon Aug 16 18:54:56 2010 From: Thomas =?iso-8859-1?q?L=FCbking?= Date: Mon, 16 Aug 2010 18:54:56 +0000 To: amarok Subject: Re: amarok crash Message-Id: <201008162054.56731.thomas.luebking () web ! de> X-MARC-Message: https://marc.info/?l=amarok&m=128198511914104 onemoretime... This message is from the KUniqueApplication constructor and it says that it could not connect to the dbus process of the instance just launched. Regarding Amarok in particular, this message has *no* value. If Amarok crashes you should (just like for every other KDE application) get a bughandler, click on details -> you get a backtrace which hints why Amarok crashed. You should also ensure that you have a running dbus session daemon (try "qdbus") that the constructor can connect to, ie.: "that is not spammed by other processes" (iirc akonadi used to do that in some svn trunk version quite some time ago) If you've no or spammed dbus, you hower won't get a a bugtracker dialog either, i think ( - and this is then your problem!) :-\ Cheers Thomas Am Monday 16 August 2010 schrieb Donn Washburn: > Hey Group; > > Even before the bootsplash from a icon amarok just stops. If I run it > from a X terminal I get > > :~> amarok > > KCrash: Application 'amarok' crashing... > sock_file=/home/donn/.kde4/socket-m1l-suse/kdeinit4__0 > (3676)/: 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" " > > This is with several different git versions. > > Anyone else seeing this problem and/or solved it? _______________________________________________ Amarok mailing list Amarok@kde.org https://mail.kde.org/mailman/listinfo/amarok