maximilian.kossick at googlemail.com
Sun Sep 17 13:30:53 UTC 2006
Ian forwarded me your e-mail conversation because i'm the main
developer of the code which is affected.
The problem in Amarok is described in this bug report:
Amarok's new Dynamic Collection feature uses MediaManager to keep
track of mounted partitions and network shares. The problem is that
MediaManager emits the mediumRemoved DCOp signal for each medium when
it is removed. On the other hand, it does not emit mediumAdded when it
is started. What happens is that Amarok hides (usually) the complete
collection because it thinks that no mediums are mounted anymore, and
does not unhide them when MediaManager is started again.
Fixing MediaManager is obviously the best solution. Do you already
have a patch, or is there already a bug report? Alternatively, we
could implement a workaround as outlined in the above bug report.
On 9/17/06, Ian Monroe <ian at monroe.nu> wrote:
> ---------- Forwarded message ----------
> From: Sebastian Trüg <trueg at k3b.org>
> Date: Sep 11, 2006 6:51 AM
> Subject: Re: stopping mediamanager?
> To: Ian Monroe <ian at monroe.nu>
> it does. because the mediamanager pings each drive from time to time which may
> break especially DVD+RW burning. Amarok is not the only one having problems
> with this. There are at least two more problems in KDE (one of which is fixed
> in svn):
> 1. the medianotifier is not properly unconnected which results in two new
> media dialogs after a k3b run
> 2. each media mounted by the mediamanager is unmounted when it is shut down
> (imagine you want to burn stuff from a cd or dvd)
> What exactly is the problem in amarok? Maybe we can convince the mediamanager
> maintainer to accept a patch for a disable or blockDevice dcop call for KDE
> On Monday 11 September 2006 01:31, you wrote:
> > There is a rumor that K3B stops the mediamanager service. Is this
> > true? This would seriously screw things up for us with Amarok.
> > Thanks,
> > Ian Monroe
> > Amarok Developer
More information about the Amarok