Version: >=1.4.2 (using KDE KDE 3.5.4) Installed from: Ubuntu Packages The problem occurs on every linux distribution I checked (SuSE, Debian, Kubuntu). Since Amarok 1.4.2 collection scan fails on scanning my collection of about 12000 files on a samba/cifs network share printing the message "Cannot build collection (Collection scan was aborted, since too many problems...)". It does not matter whether I use the distribution-package or compile it for myself. Using 1.4.1 collection scan will work without problems. It seems to me 1.4.2+ tries to scan to greedy so there will be timeouts. This thread is very similar to my problem: http://amarok.kde.org/forum/index.php/topic,12916.0.html
My network connection is a 100 MBIT switched network.
I have Gigabit Ethernet and 60000 files on a server with smb and have no problem. My System: 4000+ Athlon 64 2048MB Ram
*** This bug has been marked as a duplicate of 109451 ***
It is equal if the smb-share is mounted read-only or read-write! It is about the speed and amount of files.
Yes, but it's related to TagLib, not Amarok.
hi all, i solved the problem for me by adding : unix charset = ISO8859-1 to my /etc/samba/smb.conf on the server so i guess this is a problem with charsets i mount the volume with the following line in /etc/fstab: //myserver/share /server/share cifs guest,uid=johannes,file_mode=0440,dir_mode=0550 0 0
Using cifs and iocharset=utf8 for mounting the smb-share on my windows machine solved my problems.
I'm having the same problem, but in local not in lan. I'm using reiser4fs where the files are. The system is using utf8. I'm currently using Amarok 1.4.4, and Kubuntu Edgy (6.10). I don't really know what I may need to add to this. Thanks,
I have the same problem with 1.4.2-1.4.4. (Kubuntu Dapper and Edgy). The collection is on a remote machine and it doesn't matter if it's mounted using cifs, smbfs (samba on remote machine) or nfs. It fails with too much errors (With different files when using smb or nfs). I digged around and found a hint to mount as read-only, and voila it works (tried nfs). It was mentioned in other bug reports that it may depend on taglib, but why does the scan not fail with 1.4.1?
This looks interesting : http://amarok.kde.org/forum/index.php/topic,12516.0.html
Look at http://amarok.kde.org/wiki/Samba I found the solution for all shares on Windows machines.
I encountered the same Bug w/ Kubuntu Edgy and Amarok 1.4.3 using a external Harddrive via USB2.0 through CardBus (hooked up directly, no network involved). Perhaps it is a problem occuring when the throughput is too slow?