Hello,

amarok at my computer doesn't play files with an umlaut in the filename. xmms does. the problem is not related to the read-only mounted fat partition my music is on, i tried copiing some tracks over. googling didn't help because there are so much problem with umlauts and amarok that don't match mine. the songs show up in the playlist just fine, but when i try to play them it just switches to the next track, and if amarok comes across such a track in the playlist during normal playback (without me explicitly clicking play/doubleclicking on the track) it stays and stops. My KDE is perfectly german, including amarok.

locale in Konsole however shows en_US for me and POSIX for root.

I don't know how to change that and i don't know how to get debug output from amarok besides starting it from console, which doesn't bring up anything useful here, so maybe pointing me in the right direction here or there would be enough.
amarok takes a while to start (like one minute), but that might be normal.

You can change your locale in /etc/profile.d/lang.sh

It's been a long time since I tried to play music in Amarok off a FAT or NTFS drive so I can't remember what needs to be done to get those kind of files working. I've had similar problems though.

1 members found this post helpful.

As i already stated, the filesystem is not the problem, files on my ext4 "/" partition have the same problem.

As for changing the locale, there's really nothing more to do than this? no single program will break because of me just changing it?

Well, your original post wasn't entirely clear about where you had copied, and I believe it is still possible to have problems after copying based on the origin of the file being FAT when your locale is not set up properly.

That's it. Just change it to export LANG=de_DE.utf8 or whatever your locale is. I can't say for sure this will solve your problem with Amarok, however. You might want to try looking at the tags with a tag editor.

After changing the locale, the Umlaute in dolphin had become questionmarks-in-a-diamond, and amarok woulnd't even add them. Funny that it worked with en_US.
However, umlaut-tainted songs from the ext4-partion now do play.

now i try attaching utf8 to the mount options

Okay, after changing the locale and mounting the drive with ,utf8 the original problem is solved, amarok plays the songs without complaining.

However, I now have a new major problem: all files with an umlaut in the filename that i saved since i set my slackware system up are now unusable ("file doesn't exist" or the like errors). am i supposed to open a new thread on that? will the fix maybe even work when i change the locale back and only leave the mount option in?

Hello P42,

I'd suggest to read this: http://www.piir.ch/slackware-linux/unicode-utf-8.html
Slackware (by default) handles the locales in a slightly different way than other distributions.

Markus

The source of the problem is probably that the FAT drive doesn't encode the names in unicode so when you copy them to ext3 the original non-unicode remains. With the default Slackware set up it 'understands' the non-unicode umlauts but when you change to utf8, it doesn't understand these previously created encodings properly. You have to rename the files and it should work. If you have lots of files you could write a script to do the renaming for you or use a tool from Slackbuilds if there is one.

I think that you should somehow convert names of the files containing german letters, which were written to your partition before mounting as utf. You can try doing it in midnight commander. Run mc, open location containing your files in one of the windows and try setting a different encoding (RIGHT (or LEFT) --> Encoding in the menu).
If the filenames look good now copy the files to a different location opened in the other mc window (you can as well try copying the whole directory, just make sure the encoding is set to the one you need). Now the filenames in the new location should be ok.

I'm quite sure that there is another solution, which may not require copying of the affected files, but this one is simple and was good enough for me ;-)

there is a very nice tool on slackbuilds named convmv that converts the broken filenames (also recursively). the only other solution was to rename every file on the console, because every other way would fail with something like "no such file".


btw i read that vfat filenames are always stored in utf-16... mounting with utf-8 does it nevertheless