This is my first post, I have been running Amarok for about two years now.
I love it, and thanks for such awesome software

I am running Amarok 1.4.1-3 on Debian KDE 3.5.4
The Amarok database is on another server (mysql) and the music files (mp3,flac) are on the same server as the Mysql server, and Amarok grabs them via NFS.
I've had this same setup for almost two years, and now Amarok does not populate the collection.

I did an apt-get upgrade and dist-upgrade on both the server and my desktop today (which I do frequently, weekly), and now Amarok does not populate.
Is anybody else seeing this on a fully updated Debian computer?

It grinds away building the collection, like it always does.
And I have confirmed Amarok is talking to the mysql server.
And via Konquerer, I can browse the NFS share of the music files.
I can drag-and-drop the files from konquerer to Amarok and they will play fine.
But the "Build Collection" feature has stopped working

I have tried to build the collection using the mysql server only using local files, and nothing.
I've even tried using the local SQLite database, (using local or remote files) and I get nothing... It grinds away, but then nothing ever populates.
I've deleted the /kde/share/apps/amarok directory under my home directory and nothing.
I've even uninstalled Amarok and reinstalled it.
I can even confirm that Amarok is writing to the collection_scan.files and the collection_scan.log files while it is scanning (both remote and local files, both remote and local databases), but nothing ever happens.

I'm hoping that something is messed up on the Debian Repositories, and a quick dist-upgrade tomorrow will fix it.

Same problem here, although I'm not sure whether it's amarok or mysql related.

My system runs Debian testing i386 and Debian testing amd64.

On i386, same problem as keeblinmeister : the collection got emptied with last dist-upgrade, and amarok tries to rebuild it whenever it's started, but does not fill anything except playlists. The collection_scan logs do not show any error. One funny thing though, is that the mysql database is populated. I've tried to drop it, and it appears the scan does not recreate the tables ! If I change the collection db to SQLite, the collection gets filled correctly.

Amarok's connected to the mysql db (via UNIX socket):
mysql> show processlist;
+----+--------+-----------+--------+---------+------+-------+------------------+
| Id | User  | Host      | db    | Command | Time | State | Info            |
+----+--------+-----------+--------+---------+------+-------+------------------+
| 19 | root  | localhost | NULL  | Query  |    0 | NULL  | show processlist |
| 20 | amarok | localhost | amarok | Sleep  |  17 |      | NULL            |
| 21 | amarok | localhost | amarok | Sleep  |  16 |      | NULL            |
| 22 | amarok | localhost | amarok | Sleep  |  15 |      | NULL            |
+----+--------+-----------+--------+---------+------+-------+------------------+
4 rows in set (0.01 sec)

On amd64, no problem at all.

On both versions, amarok's package is version 1.4.1-3, but on i386 mysql server/libs/client is version 5.0.24-1 whereas on amd64 it's still 5.0.22-4.
Haven't found any bug report on the Debian Bug Tracking System for this anyway ...

Note : my music collection is accessed locally on my system (no NFS).

My Mysql server and my desktop are running client 5.0.24-1
My Mysql server is version 5.0.22-Debian_4-log

My Amarok db is named 'Amarok'
It is now completely empty, no tables

If I stick 'Amarok' into the database name, nothing happens.
And also, if I stick 'Amarok11111' as the database name, nothing happens either.
Amarok does not say 'invalid database name' or anything.
But if I stick an invalid database user name in there, Amarok will tell me it cannot connect to Mysql server.
Amarok is connecting to the database server, and authenticating, but it is not connecting to any database in the server that you specify.

have you followed the instructions on the amarok wiki for creating and initialising the mysql database?

http://amarok.kde.org/wiki/MySQL_HowTo

dangle_wtf wrote:have you followed the instructions on the amarok wiki for creating and initialising the mysql database?

http://amarok.kde.org/wiki/MySQL_HowTo

Of course I have.
Here's a bug report on the Debian Bug Tracking System.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=383894
They talk about re-compiling Amarok. I'm not going to go in that deep, I just install it via apt... I'll just wait until sid is corrected or keep using the SQLite db...

Just this week there was a commit by Jeff Mitchell which is supposed to fix some issues with Mysql 5.0.24. I cannot remember which, but if your problem is related to this, then it will be fixed with Amarok 1.4.2.

I'm confirming a simple re-compilation solves the problem.
I've build i386 1.4.1-4 binary .deb, and they're OK.

I guess that's because they were build over mysql 5.0.24 headers instead of 5.0.22, but can't assure it.
It just works, and that's fine not having amarok to rebuild the whole collection for nothing everytime it starts up  ! 

If somebody's interested, I can send them by mail, or explain how to compile yours (it's fairly easy, really).
Anyway, the impatient needs to know that this homebrew version ***WILL*** cause (small and easy to correct) upgrade troubles when Debian devs will release the official 1.4.1-4.

When is Amarok 1.4.1-4 going to be in sid?
I've been checking everyday...
I wouldn't really call the above post as 'solved', considering the words, 'homebrew', 'upgrade troubles', and 'it just works' are in the same post