On the \"Current\" Tab amarok gives me \"This file is not in your Collection!\" for files I just dragged from the Collection tab into my playlist. I checked the path of my collection setup and the path of the file and they match perfectly, no symbolic links.

Amarok was working perfectly fine before, but one day restarting it, it started claiming all the files (in the playlist I\'ve been using all along) are suddenly not in my collection. It still gives the correct \"Score\" for all those files, and all those file still show up when I search for them in the Collection tab. Yet when I drag one into the playlist, and play it, it claims the file is not in the collection.

Rescanning the collection does not solve the problem.

I\'m using an older version of amarok (1.2.4) but couldn\'t find any bug reports that said this problem might have been fixed in a newer version. I can problably just delete the entire SQLLite database and get it to work again, but that seems silly.

The only thing I changed that might have any influence that I can think of is that I also installed mysql recently.. but I\'m not using that for Amarok.

Any hints before I just reinstall the entire thing?

--John

Well, 1.2.4 is very old. I don\'t remember what collection bugs existed way back then, but you can try by just moving the collection.db out of the way and let amaroK recreate it.

Do the files still play and do they still show up in the collection browser?

i got the same \"not in your collection\" message in 1.3.1 - the problem was the playlist. i had to open the .pls-file and replace every \"///media\" with \"/media\" -> solved

Hello!
I have the same problem with amarok 1.4.2_beta1 (Had the issue also with the version before). Deleting the collection.db didn't fix it. My playlist have all absolute paths in it, no "media/". They all are like /home/data/mp3/...
Any ideas what this could be?

Guys you need to realize that we can't offer support for stone age versions like 1.2.4 (oh my God), or 1.3.1. Noone remembers what obscure bugs those versions had. And rest assured, they had many.

I am using the latest version amarok 1.4.2_beta1!

Martux wrote:I am using the latest version amarok 1.4.2_beta1!

Obviously I wasn't referring to you.

Sorry, thought so I was reopening this thread because i have the exact same problem. Just recompiled amarok but it didn't fix it
Regards, Marcus

I had the same problem with 1.4.2-beta1 with just 1 album. i can't reproduce it exactly as i use amarok-svn now but i think it occured when i renamed a new folder with mp3s while amarok was rescanning the collection. i had no chance to get it back in the collection back then.

Your best bet is rescanning your collection. I recently had the same issue, and while i didn't delve into exactly what was causing it, a rescan fixed it. So all you do is lose some time, nothing more ( ratings and stats remain ).

I did rescan, even after manually deleting the collection.db files. Also checked permissions > all ok. Even recompiling amarok did nor succeed