amaroK - Can't Build Collection (1.3.8-14.1)
 

i'm currently running SuSE 10.0 and amaroK 1.3.8-14.1 which refuses to scan my MP3 collection correctly.

Tag data are not displayed correctly in the Playlist (the filename appears in 'Title' only) and running 'Build Collection' does nothing. The collection is scanned but nothing is added.

However, running amaroK 1.3.8-14 on SuSE 9.2 works perfectly. Tag data are displayed correctly and the Collection is buit as it should be.

Any ideas what might be amiss?

Thats a bug witht the amarok 1.4 beta. To solve that problem, I had to delete my old amarok config and settings files (backed them up first) from ~/.kde.

Cheers - tried it, same problem. i even tried copying over the ~/.kde/share/apps/amarok folder and ~/.kde/share/config/amarokrc file from the working SuSE 9.2 partition. Again, same problem.

If it's a Beta software, I would downgrade back to your old verson (if it ain't broke don't fix it)

It's isn't beta, 1.3.8 is the latest stable release. i have, however, tried downgrading the 1.3.8-8 (the default version which comes with SuSE 10.0) and it too has this problem.

Are you using the same sound engine?

Yep, xine all the way.

I'm having this problem too. I don't know what your exact setup is but heres what I've found out. I'm using SuSE 10.0 and the same version of Amarok. My music is on a windows computer. I mounted that folder to /mnt/music with mount -t smbfs //comp_name/music /mnt/music. Trying to build the collection failed. So to test it out I copied one of the bands folders to the desktop. I tried building a collection using just that and it worked. So I'm wondering if its something to do with it being a samba share.

It might be a permission error if you are just doing it through the samba share, are you mounting it as root, and running Amarok as your user? Are the permissions on the file set up so that you cna access it?

Bingo. Same problem here.

i'm actually having problems with Samba elsewhere on SuSE 10.0 (samba-3.0.20b-3.1). i've found that even if i use the same smb.conf and setup as my SuSE 9.2 (samba-3.0.9-2.3) setup my Windows machines can't read the shares on my Linux box.

I was having a similar problem in which I couldn't build my music collection on another machine through a mounted samba share. My problem however involved two Suse 10.0 machines. The fix was to change the share's "read only" setting to no and it's "force user" setting to a user besides root on the machine holding the share. I don't know how you can achieve the same effect on the windows server setup though.