Mark Kretschmann wrote:Erm, upgrade to 1.4.3 then.

The problem persists in 1.4.3.

I'm seeing the same problem (on 1.4.3) - my collection is on a mounted samba share, the database is mysql.

There are some more people with similar problems:

http://ubuntuforums.org/showthread.php?t=249442
https://launchpad.net/distros/ubuntu/+s ... +bug/58613

Should I file a bug in bugs.kde.org?

--
sven

I'm using Dapper and it is exactly the same here.

It's no different in *any* new version. I compiled from SVN and still got the error...

Problem still exists in current "Kubuntu Edgy" developer release.

If this may help in anyway, I don't only have this problem when building a collection but also when I queue a good amount of files to be transferred to my mtp device. I just quits sending after a while...

Amarok 1.4.3 (compiled from source to enable mtp)
Kubuntu 6.0.6 updated (except for latest kernel which seems to break wi-fi pcmcia)
smb mounted usb disk (Tried the same disk as a share on two different comps... (1 XP Home SP2, 1 MacOS X 10.4.8 using sharepoints).

Hope this can lead in another area in debugging the problem as I actually managed to get my collection built a couple of times in the past weeks. Once the collection was there, I tagged a 100 or so albums (roughly 10 to 12 songs per album) for transfer onto my mtp device (Zen Vision M). This has never completely finished and **** out everytime (3-4 tries). When I ask for 2-3 albums, works fine! Now I had to rebuild my Thinkpad laptop because of newbie mistakes and I can
Hope this helps!

Remi

I have been struggling with this for a while, it seems the hardest part is actually pinning down a) what exactly the result is and then b) what the closest cause of the problem is.  I have experienced the above and have found a few additional bits of information.

My collection is roughly 12,500 tracks and is mounted on an NFS share.  Prior it was mounted via smb to an smb server until I changed it for fault finding purposes.  I run SLED10 and OpenSuSE 10.1. 

1) It appears that at times not only do I have scanning problems but the settings, configure amarok, collection folders untick themselves, yet remain highlighted blue.

2) This occurs on MySQL and SQLite.

3) If I delete the .kde/share/apps/amarok directory, it DOES resolve the problem temporarily (at least when using SQLite)

4) It may be partially random, I lost my entire collection (perhaps coincidentally) simply by inserting a CDROM in the drive (perhaps it tried to scan it and died)

5) So far it seems to be only with externally mounted storage (whether it be network or USB etc)

6) If it was fixed there would be a lot of happy people cause the support for external devices is near perfect 

Obviously the below bug actually started off as another perceived issue and then became clearer as I realised what was going on.  Please bare that in mind ;}

I tried to log a bug and explain it at the thread below, but wasn't doing very well, those poor developers have a hard time dealing with us end-users and admins etc!
http://bugs.kde.org/show_bug.cgi?id=134930

Another interesting fact.  (I have replicated this twice).  If I am on say a wireless network with one IP address, then shut down amarok, change to a wired network, wait for that address to be up then start amarok, my collection is no longer present.  I can browse to the nfs share via bash shell, nautilus or konqueror.  It says I have 0 tracks, 0 artists, 0 play time etc.  in ps I get a number of processes running.  I killed all the processes and amarok finally closed properly when reaching the one at the top (process 20468).  And before you ask, yes I did quit amarok properly and no the tray icon was not running.  Upon restarting Amarok it still shows up with no collection even though the collection is ticked under the configure collection area.
quentinj 20468  1.6  3.3  77996 34224 ?        S    15:27  0:04 amarokapp
quentinj 20474  0.0  1.4  87864 15220 ?        Sl  15:27  0:00 amarokapp
quentinj 20475  0.0  1.4  87820 15200 ?        Sl  15:27  0:00 amarokapp
quentinj 20478  0.0  0.5  75120  5708 ?        S    15:27  0:00 amarokapp
quentinj 20479  0.0  0.5  75120  5644 ?        S    15:27  0:00 amarokapp
quentinj 20482  0.0  0.5  75120  5708 ?        S    15:27  0:00 amarokapp
quentinj 20483  0.0  0.5  75120  5644 ?        S    15:27  0:00 amarokapp

When I start amarok again I get:
ps aux |grep amarok
quentinj 20395  0.0  0.6  25120  7236 ?        S    15:26  0:00 kio_file [kdeinit] file /tmp/ksocket-quentinj/klauncherUgiU4a.slave-socket /tmp/ksocket-quentinj/amarok7dxVpc.slave-socket
quentinj 20634  2.5  3.0  67104 31408 ?        R    15:33  0:02 amarokapp
quentinj 20641  0.0  0.7  50440  7928 ?        S    15:33  0:00 kio_http [kdeinit] http /tmp/ksocket-quentinj/klauncherUgiU4a.slave-socket /tmp/ksocket-quentinj/amarokucEEBb.slave-socket
quentinj 20642  0.0  0.6  25052  7100 ?        S    15:33  0:00 kio_file [kdeinit] file /tmp/ksocket-quentinj/klauncherUgiU4a.slave-socket /tmp/ksocket-quentinj/amarokN0xGda.slave-socket
quentinj 20646  0.0  1.6  89532 16920 ?        Rl  15:33  0:00 amarokapp
quentinj 20647  0.0  1.6  89488 16904 ?        Rl  15:33  0:00 amarokapp
quentinj 20649  0.0  0.7  69216  7952 ?        S    15:33  0:00 amarokapp
quentinj 20650  0.0  0.7  69216  7888 ?        S    15:33  0:00 amarokapp
quentinj 20655  0.0  0.7  69216  7952 ?        S    15:33  0:00 amarokapp
quentinj 20656  0.0  0.7  69216  7888 ?        S    15:33  0:00 amarokapp
quentinj 20665  0.0  0.2  3636  2260 ?        S    15:33  0:00 ruby /opt/kde3/share/apps/amarok/scripts/score_default/score_default.rb
quentinj 20666  0.0  0.6  25052  7116 ?        S    15:33  0:00 kio_file [kdeinit] file /tmp/ksocket-quentinj/klauncherUgiU4a.slave-socket /tmp/ksocket-quentinj/amarokfodzla.slave-socket
quentinj 20667  0.0  0.6  24856  6784 ?        S    15:33  0:00 kio_file [kdeinit] file /tmp/ksocket-quentinj/klauncherUgiU4a.slave-socket /tmp/ksocket-quentinj/amarokcJHWGa.slave-socket
quentinj 20668  0.0  0.6  24856  6784 ?        S    15:33  0:00 kio_file [kdeinit] file /tmp/ksocket-quentinj/klauncherUgiU4a.slave-socket /tmp/ksocket-quentinj/amaroktzreTb.slave-socket
quentinj 20689  0.0  0.0  2764  704 pts/0    R+  15:35  0:00 grep amarok

quentinj@exlt01:~> kill 20689
bash: kill: (20689) - No such process
quentinj@exlt01:~> kill 20668
quentinj@exlt01:~> kill 20667
quentinj@exlt01:~> kill 20666
quentinj@exlt01:~> kill 20665
quentinj@exlt01:~> kill 20656
quentinj@exlt01:~> kill 20655
quentinj@exlt01:~> kill 20650
quentinj@exlt01:~> kill 20649
quentinj@exlt01:~> kill 20647
quentinj@exlt01:~> kill 20646
quentinj@exlt01:~> kill 20642
quentinj@exlt01:~> kill 20641
quentinj@exlt01:~> kill 20634
quentinj@exlt01:~> kill 20395

Still the same, I bet if I now reboot it, or just leave it sitting for a day it will come back.  Either that or delete the afformentioned amarok directory.  I know this seems as though it's bordering on a different problem but if so the result is the same, I cannot build, or view the already built collection.

Well now I rebooted and yep the problem with the scanner got fixed, well sort of.  I'm still plugged into wired LAN and I can now see the database is back again and all my music is in it,  unfortunately it's doing a completely new scan over the top (so that will take about an hour), and sometimes this actually removes the music.  So it might be OK until the next time I have to do it all over again! 

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

http://amarok.kde.org/wiki/Samba

I've tried all the solutions that are suggested and still have the same problem, even though the permissions seem to be fine.

Idem for me I've try all of solution described here, but i have still the same problem.
I have tried with samba and cifs, in read only, in utf8, in iso8859-01 but I have still the same errors if i choose like MORE than 20 albums from my collection.  I don't know what to do. someone have some news about this weird problem / bug ?

Any new information on this topic?  With Version 1.4.4 I am still unable to build a collection with any of the database options.

Yes, in fact we have some new information as of yesterday. The Kubuntu Amarok packages have a problem: They are built with a wrong compiler option. This makes the collection scanner crash in some cases.

The package maintainer is informed and will probably provide fixed packages, although maybe only for Kubuntu Feisty. So at the moment your best option is to uninstall the package and build Amarok yourself, if you are using (K)ubuntu.

Thanks, i'm running Fedora Core 6 final, same problem apply?