Problems with copying music to MSC microSD card on Sansa Fuze with Amarok 2.2

Brian Morrison bdm at fenrir.org.uk
Sat Oct 24 02:19:39 UTC 2009


On Sat, 17 Oct 2009 02:22:49 +0100
Brian Morrison <bdm at fenrir.org.uk> wrote:

> On Sat, 17 Oct 2009 02:11:56 +0100
> Brian Morrison <bdm at fenrir.org.uk> wrote:
> 
> > I'm still having some serious problems with copying music to my Fuze.
> > 
> > A lot of albums will not copy, the message I get is that the track is
> > already on the device but a check using either command line or file
> > manager shows that there are no tracks named that way on there. I do
> > note that when the copy does work the system load jumps to between 25
> > and 35, although the desktop is not sluggish when this happens.
> > 
> > It isn't clear what is happening with this, but I can only say that in
> > Amarok 1.4 it just worked.
> > 
> > If anyone has any comments about the reliability of the new MSC code in
> > Amarok 2.2 I'd be interested to know what you think.
> > 
> 
> I'm not trying to get multiple tracks to copy, it seems to be
> proceeding, but the system load average is now over 140! All the
> processes seem to be of this type:
> 
> kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-bdmowHRBc/klauncherMT3184.slave-socket local:/tmp/ksocket-bdmowHRBc/amarokPW3
> 
> so clearly Amarok is causing them. 140 processes seems excessive just
> to copy some files from one disk to another.
> 

Any thoughts on this from the developers? I can't imagine why Amarok is
creating literally hundreds of processes just to copy to a UMS device.

-- 

Brian Morrison

                "I am not young enough to know everything"
                                                          Oscar Wilde



More information about the Amarok mailing list