Registered Member
|
Hi,
after upgrading to amarok 1.4.2 I get this error:
Here is everything I get when starting amarok
I just get this error on one machine. the upgrade on my laptop did well. Where is the problem?
Last edited by Anonymous on Sun Aug 27, 2006 6:51 pm, edited 1 time in total.
|
KDE Developer
|
From which version of Amarok did you upgrade to 1.4.2?
|
Registered Member
|
|
Registered Member
|
I reinstalled amarok 1.4.2 and 1.4.1 a couple of times and also reinstalled the mysql-client. Now i can start amarok and it loads my music-collection. But it does not get the statistics. on my laptop i get this and of course the stats are in the mysql database on my server.
here is the output i get when starting amarok 1.4.2:
Sorry, but i had to delete some parts of the output cause of a postlimit on the forum. |
Moderator
|
odd. Can you try backing up and deleting ~/.kde/share/config/amarokrc and see whether you get any better results?
"There are two theories to arguing with women. Neither one works."
. If men could get pregnant, we'd learn the true meaning of "screaming nancyboy wuss" |
Registered Member
|
When I do this i get:
|
Moderator
|
If you've ever downgraded from 1.4.2_beta (or 1.4.2) back to 1.4.anything, then tried to upgrade again, sorry. your database is broken.
You'll need to drop and recreate your mysql amarok db (see mysql man page for details). Note: this goes for sqlite as well - you'll need to delete your ~/.kde/share/apps/amarok/collection.db to fix the problem.
Last edited by dangle_wtf on Fri Aug 25, 2006 8:02 am, edited 1 time in total.
"There are two theories to arguing with women. Neither one works."
. If men could get pregnant, we'd learn the true meaning of "screaming nancyboy wuss" |
Registered Member
|
But why is amarok on my laptop running allright? It connects to the same database on my server.
|
Moderator
|
what's the Amarok version on your laptop?
If the two versions aren't the same, this could also be causing problems. Not sure why the laptop is working - have you tried deleting the entire ~/.kde/share/apps/amarok/ directory on the desktop machine? It could be something specific there causing the problem.
"There are two theories to arguing with women. Neither one works."
. If men could get pregnant, we'd learn the true meaning of "screaming nancyboy wuss" |
Registered Member
|
Deleting the directory does not change anything. My laptop is running amarok 1.4.2.
Something suspicious I have established: amarok on my Desktop starts a new rating etc for my songs but does not touch my db on the server. that means that entries in the db are the same after playing a song. It seams my desktop is running its own database somewhere else. |
KDE Developer
|
Sounds like the Desktop is using the SQLite backend, then.
--
Mark Kretschmann - Amarok Developer |
Registered Member
|
How can I figure out if amarok is using sqlite? I set it up with the correct mysql server ... the same as the on my laptop.
|
Registered Member
|
O.K. seams I found the problem.
I did not had installed a MySQL-Server package, just a client and mysql-common how ubuntu it calls. I did not thought that is a problem cause i do not use the mysql-server on my desktop - i use the mysql-server one on my network-server. and amarok said mysql is allright after "./configure --enable-mysql". But it aint! Amarok needs having a server on the mashine running you are using amarok, even if you don't use this server. maybe it's a bug (or feature ). |
Registered Member
|
Re: Database statistics version too new for this version of Amarok [UNSOLVED]
Mon Sep 04, 2006 9:46 am
Hi, I have just read your thread and I still have the same problem.
I just installed a Kubuntu with "multiverse" and at first, amarok did start. I could even connect to my old mysql-database (Ver. 4.1) on my network server. But after I have installed MySQL 5.0 server, client and some database tools, Amarok refuses to start. After removing ~/.kde/share/config/amarokrc , amarok claims: amarok: [CollectionDB] Beginning database update amarok: [CollectionDB] Different database stats version detected! Stats table will be updated or rebuilt. amarok: [CollectionDB] [ERROR!] Database statistics version too new for this version of Amarok. Quitting... This might be a hint. If I use my old ~/.kde/share/config/amarokrc with the database connection to an SQL-server, amarok sais: amarok: FAILED QUERY: SELECT value FROM admin WHERE noption = 'Database Devices Version'; amarok: [CollectionDB] MYSQL INSERT FAILED: table 'amarok.admin' does not exist amarok: FAILED INSERT: INSERT INTO admin (value, noption) values ( '1', 'Database Devices Version' ); ... It looks like amarok doens't realy care about the sql error but always assumes a "record not found". amarok: END__: void CollectionDB::initialize() - Took 0.027s amarok: [CollectionDB] INotify not available, using QTimer! amarok: END__: CollectionDB::CollectionDB() - Took 0.079s amarok: BEGIN: void CollectionDB::checkDatabase() amarok: [CollectionDB] MYSQL QUERY FAILED: table 'amarok.podcastchannels' does not exist amarok: FAILED QUERY: SELECT COUNT( url ) FROM podcastchannels LIMIT 1 OFFSET 0; amarok: [CollectionDB] MYSQL QUERY FAILED: table 'amarok.podcastepisodes' does not exist amarok: FAILED QUERY: SELECT COUNT( url ) FROM podcastepisodes LIMIT 1 OFFSET 0; amarok: [CollectionDB] MYSQL QUERY FAILED: table 'amarok.admin' does not exist amarok: FAILED QUERY: SELECT value FROM admin WHERE noption = 'Database Stats Version'; amarok: [CollectionDB] Beginning database update amarok: [CollectionDB] MYSQL QUERY FAILED: table 'amarok.admin' does not exist amarok: FAILED QUERY: SELECT value FROM admin WHERE noption = 'Database Stats Version'; amarok: [CollectionDB] Different database stats version detected! Stats table will be updated or rebuilt. amarok: [CollectionDB] MYSQL QUERY FAILED: table 'amarok.admin' does not exist amarok: FAILED QUERY: SELECT value FROM admin WHERE noption = 'Database Stats Version'; amarok: [CollectionDB] [ERROR!] Database statistics version too new for this version of Amarok. Quitting... The last line shows it again: The version isn't actually too high, but there was an SQL error, which is apparently treated the same way. |
Registered users: Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]