Amarok no longer MTP transfers to my Creative Zen V+

darkmeerkat · 05-31-2007, 09:47 PM

Hello,

I use Amarok (version 1.4.5) with my Creative Zen V Plus. This worked great previously, but Amarok has suddenly started refusing to MTP transfer files. The specific error message is:

Code:

Failed to copy track to media device: (the file's location was here)

I think it stopped working when I tried to add more files to the transfer queue during another transfer (Amarok hung up the whole system, so I had to do a hard reboot - oops).

I tried to get a more specific error by running Amarok from the terminal, but it didn't produce anything unusual; just the normal "PTP: Opening session" and "PTP: Closing session" messages. If I run mtp-detect, it successfully finds the device, and I can load files to it with mtp-sendfile without errors, so I'm pretty sure the error lies in Amarok.

Any ideas?

(EDIT: I tried moving my ~/.kde/shared/apps/amarok directory before starting Amarok [so that it would start from scratch] and it could add music files to the device just fine. So maybe a configuration file is corrupt?)

(EDIT #2: If it helps at all, I just noticed a small button on the statusbar that appears when I get the error; when I click on it it says "Cannot create parent folder. Check your structure." Doesn't make much sense.)

chup · 06-01-2007, 05:43 AM

You could use gnomad2, it does the job. I have a Zen V Plus myself as well, and it works perfectly. Only thing I needed to figure out was that you select player info the see the disk space. Hope this helps.

darkmeerkat · 06-01-2007, 07:59 AM

Thanks, I'll try that.

I'd still like to try to fix Amarok though, it be a shame to lose it. It's a great program, glitches aside.

EDIT:
After some work with Amarok's configuration directory, I've fixed it (for now). What I did was to go into the .kde/share/apps/amarok/ directory and delete the 'collection.db' file. (I have zero experience with SQLite, but I assume that 'collection.db' is an SQLite file.) I haven't noticed anything missing but, just in case, I made a backup copy of the amarok/ directory. So, to sum it up:

Code:

$ cd .kde/share/apps/
$ cp -R amarok amarok_backup
$ cd amarok
$ rm collection.db

Then restart Amarok and let it begin rebuilding the collection (which shouldn't require any input).

EDIT II: THE RETURN:
The above fix worked for one transfer, then conked out again. I finally fixed it, so far for good, by compiling amarok, as opposed to my previous (binary) install method (Arch Linux's 'pacman' system). I removed amarok ($ pacman -R amarok-base), then used Arch Linux's ABS system to cleanly install it (with trivial modifications to the PKGBUILD file, since I didn't need extras like libvisual or libgpod support). A hearty 'good luck' to you if you run into this problem.