

I don't think that is the issue here. I got k3b but it's version 0.12.14. It could be mysql as Kaste and Pteppic suggested. I recently upgraded mysql from v4.x to v5.x. After that the collection was behaving weirdly.Flameeyes wrote:If you happen to be using k3b 1.0_pre versions, that is the culprit. Amarok 1.4.3 and later, and K3b 1.0_pre don't seem to like each other.


Code: Select all
#!/bin/sh
# Put this in your cron.weekly, dont forget to chmod a+x
# Backup the Amarok MySQL database
dir=`date +%Y-%m-%d`
if [ -d /home/backup/amarok ]; then
mkdir /home/backup/amarok/$dir
mysqldump -u amarok -pPASSWORD amarok > /home/backup/amarok/$dir/amarok.mysql
fi
That is exactly the problem I am having right now.Robelix wrote:I also get always the "THIS FILE IS NOT IN YOUR COLLECTION!" in the Context-Tab. But the collection does not get lost.
And another strange thing: When I unset the cover image and grab a new one the Context-Tab shows the old one again. Everywhere else (Cover manager, drag'n'drop, OSD) I see the new one.
amarok-1.4.4 with mysql-5.0.26.
I just lost all my statistics today in amarok today, but they're still there in the mysql db. Will downgrading mysql fix this or should I just emerge postgresql and be done with it?Conan wrote:Amarok still has some problems with 5.0.26, not sure when they will be fixed, no ones been doing any work on it in SVN afaik.

It wasn't a permission problem. I was able to log into mysql using 'mysql -u amarok -p' and query the database myself; all the stats were still there. I guess amarok just got confused and duplicated everything. It's not the first time Amarok has done this to me after an upgrade (amarok upgrade, not mysql). In any event, I deleted the table and rescaned my collection and everything was ok.Kaste wrote:I'd suggest you check wether you can really access those. I guess you changed your password or Amarok forgot about it or you lost permissions, or the mysql server wasn't started when you opened Amarok.
It took me a while to figure these out when they happened to me because the error is just reported in one of those little popup boxes and vanishes very soon. maybe start Amarok from console and see what it tells you when you start