Version: (using KDE KDE 3.5.3) Installed from: Slackware Packages OS: Linux this behaviour is exposed by recent versions of amarok, which depend on media manager daemon to provide dynamic collection support. this happens with fstab backend, no hal/dbus. whenever a device is manually mounted or unmounted (with or without an entry in fstab), all the devices are removed in amarok. restarting media manager daemon and amarok brings them back. the devices disappear also when amarok is not running and a manual mount/umount is performed.
They disappear from amarok? or from media:/? or both?
they disappear from amarok, but stay in media:/
Ok, reassigning there then. It's likely to be an amarok bug.
additional info, based mo max's question ;) actually devices stay in media:/, but they appear as unmounted (whereas they appear as mounted before performing manual mount/umount). sorry for missing that fact.
No, it's not an Amarok bug. Running dcop kded mediamanager fullList after mounting/unmounting a device shows that the mount status of all other devices is set to unmounted, although they are actually still mounted. Mediamanager emits the DCOP signal mediumChanged for every device. Forcing mediamanager to reload its backends restores the correct state of the mountpoints, but only till the next manual mount/umount
Sending back the report, then.
if anybody else stumbles upon this before it's fixed - as an alternative to opening services window & starting/stopping media device service there, you can try executing `dcop kded mediamanager reloadBackends`
for the record : just mounted & unmounted usb flash - and only the correct device was added/removed in amarok, also media:/ still shows all the correct devices as mounted. i have upgraded to kde 3.5.4, so this might be fixed in there - but it would be nice of other could thest this, too. even better would be a particular commit so that we know this indeed is fixed ;)
I can confirm the same behaviour. It's probaly related to latest S. Kulow patch fixing bug nr. 132281 (https://bugs.kde.org/show_bug.cgi?id=132281#c10)
I can confirm the same behaviour.
kio media doesn't exist on KDE4.