Red Hat Bugzilla – Bug 144752
Amarok fails to start after first start
Last modified: 2007-11-30 17:10:58 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.5)
Description of problem:
The first time amarok is started, it runs fine. But, after starting
once it cannot find the communication sockets it expects.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install amarok
2. Start amarok and close
3. Start again
Actual Results: Amarok fails to start and provides user with an error
message. Debug logs show that it is failing to connect to KDE sockets.
Expected Results: Amarok should start.
There is a more current release of amarok (1.1.1) available. Perhaps
this would be easier to target than trying to fix 1.1.0?
What do you see? Something like...?
[amaroK loader] connecting to
[amaroK loader] exiting.
Are you sure that Amarok has quit and has not docked into the KDE panel?
Amarok is composed of two programs :
- amarokapp: the "real" amarok
- amarok: a simple loader, which reacts like Michael's commment. It's
used to make sure only one amarok is running, and to pass commands
like --next, --stop, etc
A possible problem could be that you do not use the dock, and as
clicking on the "close window" button defaults to minimizing Amarok to
dock, you cannot access it afterwards. Are you using KDE with kicker ?
I'll update Amarok when 1.2 is stable (currently beta3, it should
Oh yes, and by the way, version 1.1.1 is in the QA queue at fedora.us :
I forgot a bit about this one, I'll probably publish it soon.
Created attachment 109655 [details]
Amarok 1.1.1 spec
Yes, the output is very similar to the output I was getting. Amarok
wasn't running, and wasn't docked. I am using KDE and kicker.
I went ahead and modified the amarok spec for 1.1.1 and built it on
x86_64 and all seems well now.
Amarok 1.2.2 seems to be out in between -- Is this bug still valid or can it be
Bug is fixed with new version, so it should probably be closed.