Version: 1.4.3 (using KDE KDE 3.5.4) Installed from: Mandriva RPMs OS: Linux $ ls -l ~/Music total 0 music1 -> /mnt/win_d/My documents/My Music// music2 -> /mnt/win_f/mp3s// As you may see, there is nothing but symbolic links to my Windows partitions in ~/Music. Amarok doesn't like ~/Music folder, it cannot display anything in collection selection dialog next time I start it. And if Amarok want to rescan the collection, it says there is nothing inside my collection.
does you parition is mounted correctely?
> does you parition is mounted correctely? Yes. It is mounted automatically at boot.
I think I have a smiliar problem. I have a removable disk (via usb). If I unmount or disconnect it, amarok deletes all its contents out of the collection database. Thats a good behaviour if it is a local harddisk but not for removable ones. My suggestion is: there should be a possibility for different collections (so one can mark a collection not to be removed if the files cannot be found at the moment). Should I open a new bug for this (wish)?
I also have a similar problem to #3. My music collection resides on a remote fileserver mounted via NFS. If the connection drops for some reason, Amarok attempts to rescan, finds no files, and empties its collection. This behavior is not optimal.
to comment 3 and comment 4 : which version of amarok ? try to upgrade to the latest one, if not running it already. with dynamic collection enabled and working correctly, these cases should be handled nicely - data would be removed from the collection browser (bu _not_ from the db) instantly (without requiring a rescan) and corresponding entries disabled in the playlist. after the device comes back, collection browser contents should be repopulated and entries in the playlist enabled, again, all this without a rescan. if this is not working for any of you with the latest version of amarok, ask for help mailing list or on freenode/#amarok, as this is more of a support issue - and i'd guess, different one from the initial report.
Since no further feedback from reporter, this bug is presumed fixed. Thank you for your report, please report again, if this behavior persists in amarok 2.