Hi,
first of all thanks for this piece of software.
I have some trouble with my music collection stored in a NFS mounted filesystem: when the NFS server is not reachable, Amarok wait forever something without start the interface (splash screen forever).
My collection is splitted in two parts, one locally and one at home in a NFS server (so when I'm not at home the NFS server is unreachable...).

Is this a known problem? may I hope that someone cares for my issue?
thanks in advance

Amarok Version 2.2-GIT
Using KDE 4.3.00 (KDE 4.3.0)
(Build Date: Aug 29 2009)

Try to set the mount folder as "root" of your (NFS)-collection. So the folder exists, even if it is empty, when the share's not mounted.
Multiple collections will be available in A2. So you can have a "Home" and a "Away" collection.

m0nk

Many thanks for your hints, the problem was just that!
Changing /etc/auto.master from

Code: Select all

/mnt/nfs /etc/auto.myserver --timeout=30

to

Code: Select all

/nfs /etc/auto.myserver --timeout=30

solved the amarok hang issue (was a filesystem hang issue ).
Now I'm waiting the multiple collections features because at the moment amarok don't know that half of my collection is at home...never mind at the moment because the collection scanner is very very fast!

Regards

EDIT: now at home I finally understand... /nfs is checked in amarok collection folders, not the mounted directory...