Comment 2 for bug 395956

I am confirming the bug, I had the same behaviour:

Ubuntu 9.04
amarok packages from: Unsupported updates (Jaunty backports)
* amarok 2:2.1.1mysql5.1.30-0ubuntu1~jaunty1
*amarok-common 2:2.1.1mysql5.1.30-0ubuntu1~jaunty1

Enabling the unsupported updates (Jaunty backports) caused Amarok to upgrade in version 2.1.1.

After the upgrade, more than half of the non latin strings are replaced with question marks. I cannot understand the pattern, the change seems random. All files in the collection have been processed with EasyTAG before importing and they tags were UTF8. The question marks can be seen in every view (e.g. collection, playlist) and in the "Edit track details" context menu.

Further examination showed that this is issue of the amarok database and not the ID3 tags themselves. The tags are perfectly OK (unless you try to edit and save the details of a track).
Opening the amarok database with mysql (*) shows that all non latin characters are indeed replaced by question marks in the varchar columns.

Rescanning the collection had no effect.
Using the perl MP3::Mplib to set the UTF8 header on the tag as suggested by the amarok FAQ, had no effect too.

Reverting back to the 2.1 version from the launchpad kubuntu ppa (http://ppa.launchpad.net/kubuntu-ppa/backports) and rescanning the collection solves the problem but seems to create a different problem:

I found at least one track that was in my playlist during rescanning to now show under a different album of a different artist. Maybe this is a bug and collection should never be rescanned with tracks in the playlist.

After repetitive scans the track now shows under the wrong artist/album. This is not as worrying as the fact that I am not sure how many other errors there could be.