Version: 1.4.3 (using KDE KDE 3.5.4) Installed from: Gentoo Packages As I'm currently testing the new K3B-1.0_preX release I found a problem in Amarok. Because of a bug in kdelibs, K3B stops the KDED Mediamanager and Medianotifier before burning/ripping/copying a CD/DVD/.. As soon as this daemons are stopped, the collection view of Amarok gets totally empty. Although K3B restarts this daemons after doing it's job, the collection view stays empty, only restarting Amarok helps.
Just did some testing... it happens, when the KDED Mediamanager is stopped... Medianotifier doesn't affect this.
As a workaround, you can add DynamicCollection=false to the [Collection] section of your amarokrc. This will disable Amarok's Dynamic Collection feature. Is there a bug report for K3B's problem? This isn't really an Amarok bug, but I might be able to add some code to recover to some extent.
K3B 1.0 turns off the mediamangager since it querying the CD drives can interfer with burns. So I guess the mediamanager disappearing while amarok is running is something we have to deal with...
I think it's possible to recover by polling MediaManager and updating Amarok's list of available devices as soon as MediaManager is available again. The only problem left is that the collection will be empty as long as MediaManager is not available (there are some corner cases where the collection will not vanish but those are not relevant). The only option to solve this problem that I see is to implement a compatibility mode in both Amarok and K3b...K3b will have to emit a DCOP signal when it is about to deactivate MediaManager, and Amarok will listen to that signal. If we are doing that K3b can emit another signal after activating the KDED MediaManager so we won't have to poll. I haven't talked to the K3b dev(s) yet, but will do that as soon as I get some feedback on this problem from the other Amarok devs.
Sebastian Trueg knows about this problem. See bug#134158 (issue 4.)
Seems not to happen anymore using k3b-1.0 and Amarok-1.4.5. If 2 or 3 people would confirm this we can close the bug.
Yes, this WFM with k3b-1.0 and Amarok-1.4.5.
This problem never occured here. Nobody else complained, so I think it's o.k. closing this bug as RESOLVED.