Collectionscanner can't read UTF-8 encoded files

Bug #72673 reported by Kevin Kubasik
16
Affects Status Importance Assigned to Milestone
Amarok
Fix Released
Medium
amarok (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

On startup.

Revision history for this message
Kevin Kubasik (kkubasik) wrote :
Revision history for this message
ville palo (vi64pa) wrote :

Does this happen every time you try or just once?

Revision history for this message
koshari (holto2go) wrote :

i get the error when the scanner attempts to scan filenames with umhlets or other charactors over a cifs share.

this happens consistantly unles i change the offending charactors on the filename on the share .

Revision history for this message
AnRuaRi (anruari) wrote :

scanning a large collection for the first time after a complete reinstall of ubuntu.

The collection was on a ReiserFS drive with known physical unrepaired errors.

Revision history for this message
Michal Maňas (michal-manas) wrote :

crash report,

scanned large collection on non-linux drive (NTFS or FAT32, I do not know).

Revision history for this message
RJ Marsan (rjmarsan) wrote :

more info? sorry to keep asking but it helps.

Changed in amarok:
status: Unconfirmed → Needs Info
Revision history for this message
Samsap (samze) wrote :

Happens every time I scan my whole collection.
And get an error message at the end saying that some music file could not be scanned. They seem to have special caracters. (french accents)

Revision history for this message
RJ Marsan (rjmarsan) wrote :

So it appears that wierd characters in file names crash AmaroK, can anyone confirm this?

Revision history for this message
Andrew Ash (ash211) wrote :

The same bug has been entered into the KDE bug tracker as #137824. They are looking for example files encoded in UTF-8 that cause the scanner to crash. See if you can help them out.

Thanks. I'm also confirming this bug and setting it to medium importance.

Changed in amarok:
importance: Undecided → Medium
status: Needs Info → Confirmed
Changed in amarok:
status: Unknown → Unconfirmed
Revision history for this message
Andrew Ash (ash211) wrote :

Status update:

It turns out this bug depends on changing the way Amarok is compiled, which is being worked on. See bug 81768 for more details.

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

fixed in 1.4.5

Changed in amarok:
status: Confirmed → Fix Released
Changed in amarok:
status: Unconfirmed → Fix Released
Revision history for this message
freecheeseman (acortelyou) wrote :

I am experiencing this issue with the 1.4.5 package.

Revision history for this message
Hans (hans-gabriel) wrote :

Hi,

the problem seem to be not fixed in version 1.4.5. I still have that problem:

shortly before the end of collection scanning (aprox. 91%) apaers a error message like described from Koshari.

But the best of all: Amarok ist running well ...

Revision history for this message
Ing0R (ing0r) wrote :

Bug 76938 does not seem to be an dublicate of this here.

Revision history for this message
Apostata (m-cahill) wrote :

Running 1.4.6 over here (Feisty) and it does not support UTF-8 encoding.

Revision history for this message
Pascal Bach (pascal-bach) wrote :

I can confirm this with kubuntu 7.04 and amarok 1.4.6. It crashes while updating the Collection from a VFAT partition with filenames containing german special characters.

Revision history for this message
Pascal Bach (pascal-bach) wrote :

After running the command:

convmv -f iso-8859-1 -t utf8 -r --nfc --notest *

inside my collection directory, amarok doesn't seem to crash anymore, maybe this may help someone.

Changed in amarok:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.