Comment 31 for bug 334082

I have this problem too, but I've found something interesting which may help figure out what's going on. Steps to reproduce:

1. Find an affected song in the collection, where the duration is "Unknown" in the Time column.
2. Right-click, choose Properties.
3. Modify at least one of the tags (e.g. Title, Artist, Album, etc.) so that Rhythmbox is forced to write it to the song file.
4. Click close - Rhythmbox will write the tags, and in doing so, re-calculate the duration correctly.
5. Play the song. You may need to start playing another song first, then play the modified one.
6. Seeking should now work correctly.

There are a few possibilities and speculations:

1. The tags in the file are corrupt, and Rhythmbox is rewriting the tag header correctly, which allows it to correctly calculate the song length. This is unlikely however, since I've been quite meticulous with my tag curation in Amarok 1.4 and Ex Falso over the past few years.
2. Because the songs were not imported into the collection using Rhythmbox (they were simply indexed from a collection managed by Amarok 1.4), the indexing may not have been doing the duration calculation correctly, or at all, for some files.

I have tested this on files that I know beforehand have valid ID3v2 tags and the durations and seeking works correctly in Amarok 1.4