Hello,

suddenly my amarok cease to start up. The application itself starts but there is no window or icon in the systray appearing. System is Kubuntu 10.04 with Amarok 2.3.1 from ppa.

Output is:

florian@horus ~ % amarok -d --nofork
Calling appendChild() on a null node does nothing.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
amarok(1710)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(1710)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(1710)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
QGraphicsLinearLayout::removeAt: invalid index 1
amarok(1710)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:

I tried an aptitude reinstall und to do kbuildsycoca4 --noincremental.
As I said no change from my side that could have caused the problem as far as I know. Yesterday I added a buch of mp3s, listen to them and this morning it cease to work.

Please tell me, if I can provide more information.

Thanks,

Florian

Reinstalling an application is in general not a way to solve anything in Linux. If an application that did work well before in the same version doesn't work anymore, it usually points to a bad configuration.

Pleas remove the amarok* files in $HOME/.kde/share/config/ and try again. If that doesn't help, try removing the file current.xspf which is in $HOME/.kde/share/apps/amarok/

Well, it works again.

Reinstalling may not be exactly the method of choice, but it almost worked. I've downgraded to the 2.3.0 that was delivered with Kubuntu, used that for the last two days and just upgraded again to 2.3.1 from ppa and it worked again.

I've I have something like that again, I'll try out your hints first.

Florian

I'm having the same issue. Had to downgrade to 2.3.0 to get it to work. Think it may be the packaging with Kubuntu but to let you know, even if I rename the amarok sub-folder to something else it doesn't help. It doesn't get far enough to write the folder again. Eventually I get an error that says it can't connect to the dbus. I know I haven't updated amarok but I can't say if something else has been updated and amarok doesn't work with the new setup or something else is breaking amarok. I'm using Kubuntu 10.04 with the dev install source for amarok 2.3.1 and the latest updates from all those sources.

Can you please run Amarok from the console?

Code: Select all

amarok -d --nofork

Watch the output, and see if there is anything interesting there. Downgrading should never be necessary.

Valorie

Instead of reinstalling or downgrading it would be much easier to remove the amarok* configuration files in $HOME/.kde/share/config/

Sorry, thought I put that in my previous post. I deleted the entire directory and it didn't help at all (actually, I moved it to amarok2 but a new amarok directory was never created), leading me to believe it's dying before it makes it to that point. I thought I did try with debug turned on but I didnt' try the -nofork option. I'll try that one as well. I will point out that at some point Amarok 2.3.1 did work for me so I'm not trying to say that something is completely amarok's fault but some update since updating to 2.3.1 has caused a break, I just can't tell if it's in amarok or another process. With a ps -ef I do see amarok processes running, although most say defunkt. I have to run a pkill amarok to try and start it up again.

I see the same issue here with the same setup (KUbuntu 10.10-x64), don't know when exactly this happened but it must have been within the last few days or so. I see that amarok is running in background after system start but there is no foreground activity (no icon is systray).

I removed the config files but to no avail.

Code: Select all

gerd@jupiter:~/.kde4/share/config$ amarok -v
Qt: 4.6.2
KDE: 4.4.2 (KDE 4.4.2)
Amarok: 2.3.1

gerd@jupiter:~/.kde4/share/config$ rm amarok-appletsrc
gerd@jupiter:~/.kde4/share/config$ rm amarok_homerc
gerd@jupiter:~/.kde4/share/config$ rm amarokrc
gerd@jupiter:~/.kde4/share/config$ amarok -d  --nofork
Calling appendChild() on a null node does nothing.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
amarok(3268)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(3268)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(3268)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
QGraphicsLinearLayout::removeAt: invalid index 1
amarok(3268)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:

Since there haven't been any updates to this machine besides the regular updates per KUbuntu default channels I am really puzzled.

Any advice on how to get back my music memories will be highly appreciated


Thanks

Gerd

Well, the default location on Kubuntu is $HOME/.kde/... not .kde4/...
Please try again, you are not supposed to have a .kde4/.. folder in the first place.

I need glasses...

And thanks a million times, got my amaROCK'ing again.

Amarok's first random choice was

Earth & Fire - Weekend


Definitely another most appreciated advice

Is there any known issue that can lead to this auto-misconfiguration?
Is it worth filing a bug with the config files attached?



Again, thanks a lot

Gerd

starman wrote:Is there any known issue that can lead to this auto-misconfiguration?
Is it worth filing a bug with the config files attached?

No, not really. I guess your /home took this over from an older Kubuntu version, and what you erased were files from an old version. IIRC at some point both KDE3 and KDE4 were shipped where this distinction needed to be made.

Worked for me as well. In case anyone was wondering it was the amarokrc file. The others were fine

This is not limited to Kubuntu but happens in Fedora 12 & 13 with Amarok 2.3.1.

Removing the amarokrc file does solve the problem. However that causes amarok to loose its settings and it then insists on rescanning the music which corrupts the collection data, albums are listed under the wrong artist, lyrics are displayed with the wrong track, tracks are missing etc.

Reinstating backups starts the whole process again with amarok being unable to start.

I haven't investigated any further, just removed all of the amarok* files as suggested and got back a working environment again.

As far as my understanding goes the database (built-in MySQL here) content remains in place. Seems like I haven't lost anything but some display settings which were easy to re-adjust.

starman wrote:As far as my understanding goes the database (built-in MySQL here) content remains in place. Seems like I haven't lost anything but some display settings which were easy to re-adjust.

Yes, there is a caching bug with the Collection Browser, usually a rescan restart of Amarok solves the problem. That bug is not easy to solve.