Hey, I just moved my music files over to another pc on the network, and set up a samba share and mounted it. I wanted amarok to be able to play these files. I add them to the collection and that's fine, but when I go to scan, after about 86%, it gives me a list of files that it couldn't process. Somehow this leaves me with about 3/4 of my music unable to be added to the collection.

I checked the files and they do have the proper permissions, just like every other file in these folders.

Here is a screenshot of what the error message says:



Has anyone else had a problem like this? Is there a fix for it?

I don't know about anyone else, but I can't see the error message.  Can you just copy and paste it?

Also, this might seem like a silly question, but I see a lot people do it this way for some reason.  Is the machine you're hosting the files from a windows box?

for some reason I see people set up samba shares when connecting to directories on linux boxes. 

I have my entire collection on a linux server and it is connected to my laptop with NFS.  Amarok scans it without any problem.

It's not a Windows box, but there are other Windows boxes on the network. As for the error message, I couldn't copy and paste it because it gave me no text-cursor with which to copy from.

Do you have any suggestions?

Look here: http://amarok.kde.org/forum/index.php/t ... 916.0.html

Bug reported here: http://bugs.kde.org/show_bug.cgi?id=135243

http://amarok.kde.org/amarokwiki/index.php/Samba

Another thing to try, which worked last night for someone on irc, is to mount the share with mount.cifs instead of smbmount.

Hey, if you're still having the problem, this may help you.  I accidentally generated a similar problem by adding unicode mapping to my fstab:

Code: Select all

//FileServer/mp3 /remote/mp3 smbfs username=****,password=****,iocharset=utf8,codepage=unicode,unicode,dmask=777,fmask=777,auto,rw 0 0

I put that in to clean up how the files looked when I browsed them in Nautilus, but it made Amarok barf on a rescan with exactly the same kind of error you're having.

Returning it to its prior state made the problem go away:

Code: Select all

//FileServer/mp3 /remote/mp3 smbfs username=****,password=****,dmask=777,fmask=777,auto,rw 0 0

Everything tried, no solution yet.

Here is what "strace amarokcollectionscanner -r /media/daten/MP3" says: http://www.thebastardoperatorsfromhell. ... ace_rw.zip


fstab for mount: //Zerberus/Daten /media/daten cifs file_mode=0666,dir_mode=0777,noauto,rw,credentials=/etc/fstab_smb_devilsnetwork 0 0
User has full rw-rights and NO file is corrupted. I collected more than 300 files in one directory where amarok told me they may be corrupted and scanned this directory for its own. No file was dropped, all files were scanned successfully.

Not sure if this has been reported already on different threads, but I'm having this same collection scanner problem on my local reiserfs hard drive as well. My music folder I tried to scan is about 164G, so I'm not sure if size plays a factor here.

I also tried scanning the folder using my backup copy of the same collection on an external firewire reiserfs hard drive. Same problem.

I had this same collection working before w/Amarok. Not sure during which upgrade it broke.
amarok-1.4.3-0ubuntu8~dapper1
libtag1c2a-1.4-1~dapper1

-Lars

solved! thank you dwasifar

adding :
  unix charset = ISO8859-1

to my /etc/samba/smb.conf on the server solved things for me
so i guess this is a problem with charsets

dwasifar wrote:Hey, if you're still having the problem, this may help you.  I accidentally generated a similar problem by

Original poster, please check if this solves your problem, and add [SOLVED] to the topic subject if this is the case.

Ciao,

after migration to amarok 1.4.2 and then 1.4.3, my collection scan failed, as reported by several other users. The problem is often related to disks mounted with samba, but I actually had an NFS disk.
Now I installed amarok 1.4.3 on a different computer, with only a local disk. No samba, no nfs, nothing like that. The collection is in the local disk. But I still get that error when scanning the collection. I also tried the SVN version, but same behaviour.
Reducing the collection to few files (10), I managed to add most of them to the collection (but still two fails...). But for these files I cannot update the tag. I don't receive any error, simply the tag is not updated.
I think the two problems are related. There must be something wrong with the way the tags are read with amarok >1.4.2 and this also causes the scan fail. Maybe something about the charset, as suggested by some. But how to fix it?
I think this should be fixed with high priority, because it prevents many users from using amarok.

Thanks,

Stefano

This doesn't appear to have worked for me.