Comment 13 for bug 709868

Tried with another data cd I found around. Same result.

Suppose that I start with a music cd in. If I:

1a) Take out the music CD by pressing the button on the cd drive rather than using the eject button on the device notifier
2a) Insert the data CD

Then the device notifier does not update and keeps telling "play audio cd with amarok" as the single option

If I:

1b) Take out the audio cd by pressing the eject button on the device notifier
2b) Insert the data CD

Then the device notifier recognizes the data CD, correctly printing the CD label and shows me 3 actions: download photos, copy with k3b, open in file manager. Now if I

3c) Click on "Open with file manager" or on the small "mount button" on the right "click to make this device accessible from other applications"

then the device notifier gives me an error "Could not mount the following device CDSTOMPER35"

I wonder if this may then be due to the fact that my computer has been upgraded since lucid, so my .kde folder may contain a lot of coming over information that confuses the system or what.

Any hint at how to debug this?

Specifically

a) Why does the kscmshell4 solid_actions try to save actions in .local/share/applications rather than .kde/share/apps/solid/actions? Is the saving location hardwired or made configurable somewhere?

b) Is there any place where one finds the commands that solid uses to mount devices? Or is it hardwired?

c) Is there something that one can modify to make solid log what it is doing?