Hi,

I just submitted a bug report regarding this issue:

http://bugs.pearsoncomputing.net/show_bug.cgi?id=1758

Any clue on this?

I'm not yet involved in TDE development, but I'd be willing to try to fix this if some people could give me few advices and directions. And basically, I don't want to dig in it if it's a well known fact that such inode64 issues on x86 platforms are not not fixable (in the context of TDE code only).

I think I have to start analyzing the scanning code of course and check C types used to handle inode values, if such things occur within Amarok code.

Another option might be that the bug lives in an external library that open the files for Amarok.

(People might ask me "Why I don't you swich to amd64 distro?" But that is not the question here.)

Nicolas