External media handling

[Jeff Mitchell]

Okay, I'm going to need some help from you guys with this one.

Mark, I know you're using Ubuntu.  Do you happen to be using Gnome as 
your desktop?  Dave, what about you?

I took a device I'd never plugged in to my laptop before and popped it 
in my laptop.  Set the collection to scan the folder with its music as 
well as one on my hard drive.  Rescanned, saw all the files.  Closed 
Amarok, unmounted it, opened Amarok again.  Tracks were gone.  Closed 
Amarok, mounted it again, opened Amarok again.  Tracks were right back 
where they should be in the Collection.  So over on my end, my first 
brush with Dynamic Collection was totally cool as opposed to the totally 
uncool experience you guys are having.

So here is my current thought as to what is going on:

The code that detects various mounts uses the same method of finding 
them as the media devices, which means it uses kded's MediaManager 
module.  The most likely explanation that I have right now is that for 
you guys, the module isn't running (or is returning rubbish).

Log in normally, open up Amarok as you normally would, then go to a 
console and type the following:

dcop kded mediamanager fullList

You should get a long printout of mounts of various types.  Please send 
that to me (you can omit copying the list if you don't want to).  In 
addition, please send the contents of your "devices" table in your 
database (if you're using sqlite run the following commands (sqlite3 may 
just be sqlite depending on your distro): "sqlite3 
~/.kde/share/apps/amarok/collection.db", "select * from devices"...if 
you're using mysql log into it, use the amarok database, and run "select 
* from devices"), and the contents of your amarokrc (at 
~/.kde/share/config/amarokrc).

If you don't get a long list of mounts when typing that dcop command, 
open up kcontrol, go to KDE Components, then Service Manager.  Make sure 
that KDED Media Manager is checked and started.  If it wasn't, you'll 
have to start it (and make it start at boot or login or when KDE starts 
or however it's handled...if you're running Gnome I'm not sure how you'd 
do that).  And then, if the dcop command works, start futzing around 
with your mount points and Amarok (mount, open Amarok, close Amarok, 
unmount, etc.)...the code that I saw has some "self-healing" to it, so 
it should see the new/most recent mount points for the UDIs and 
automatically fix them...keep an eye on the devices table in your 
database (although it will require running a full rescan on your 
files).  A device ID of -1 is bad, anything positive is good.

--Jeff