I'm a happy Amarok user, using it for playing/browsing/querying my music collection, but this weekend I encountered a problem: Amarok didn't start anymore. When I launched Amarok (version 1.3.1, that is) from the command line I got the following error:
$> amarok amaroK: [Loader] Starting amarokapp.. amaroK: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp. QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow kio (Scheduler): FATAL: BUG! _ScheduleJob(): No extraJobData for job!
I experimented with changing/deleting my Amarok settings in ~/.kde/share/apps/amarok and it became clear that there was some problem with collection.db. Deleting (after a backup of course) that file would solve the problem, but I did not want to lose the statistical information about my music collection in that file.
Another observation was the fact that Amarok did not crash if there was no internet connection, it only complained it could not contact some amazon server (for information about cd cover images, I presume). Consequently I assumed some amazon synchronisation/update job was the culprit for the crashing. This amazon thing was apparently triggered by some contents in collection.db, so I tried the following.
The file collection.db is a sqlite version 3 database file (the alternative is using a MySQL database, but that seems a bit overkill to me). I installed the sqlite3 command line client and made a SQL dump of the file as follows:
$> sqlite3 collection.db .dump > collection.sql
Next, I removed all the entries in the "amazon" table from the SQL file (with grep and its match inverting option "-v"):
$> grep -v 'INSERT INTO "amazon"' collection.sql > collection_edit.sql
Then I backed up my old collection.db file and imported the edited SQL in a new collection.db database file:
$> mv collection.db collection.db.backup $> sqlite3 collection.db < collection_edit.sql
Now Amarok starts up again and I still have my collection/statistical data.
Hey, thanks, perfect
Hey, thanks, perfect guide.
I had a problem, i accidentally downgraded to amarok 1.4.1 and i've lost my moodbar support.
now i cannot activate it again. ( i can't compile the external moodbar and i can't find amarok-moodbar in the debian mirrors.)
i tried to reinstall amarok 1.4.3 but nothing worked, even with apt-get remove --purge and deleting files manually :(
then i went back to 1.4.1 and amarok crashed when launching, and this guide helped me. thanks.
Great finding, Save me Lot of headaches
Exactly same problem here, five minutes to solve it thanks to YOU, I think that it should be treated by the amarok developers, I have no Idea how it comes to happen.
GREAT!
You are great!! exactly the same problem and i solved it in 1 sec thanks to u!!
TIME (the journal) had right when in the past cover page (something like 1 month ago or 2) it puts a mirror and it says "the TIME person of the months is you" dedicated to everyone has ever written anything useful on the net.. these are the persons that contributs to a better world!! keep on going like this, so when we have some problem, we can just go on google and solve it for free!!! that's great!!
Thank you, your way allowed
Thank you, your solution allowed me not to install some other version of amarok out of ubuntu one.
thank you
Post new comment