regression of Media Devices fix

[Jeff Mitchell]

UGH.  I won't have time to look at this anytime soon...I'll have a ton  
to catch up on when I get back to work in two days.  Feel free to try  
to figure it out if you can...

--Jeff

Quoting Andrew Turner <andrewturner512 at googlemail.com>:

> Jeff,
>
> This reminded me:
> I noticed recently that the fix for non-KDE users using Media Devices
> has regressed again. Nothing shows up for me again in the Media
> Devices configuration screen, even after pressing Autodetect Devices.
>
> Sorry for the hijack.
>
> Andrew
>
> On 17/09/06, Jeff Mitchell <kde-dev at emailgoeshere.com> wrote:
>> Max--
>>
>> I ran into this problem when dealing with media devices.  I'd look at
>> MediaBrowser and DeviceManager code (and other related code, like
>> possibly MediumPluginManager) for what was done to fix it.
>> Essentially, it iterates through the list of mediums returned by the
>> DCOP call and called mediumAdded normally.  You have to be careful
>> though because there needs to be a delay for people not running KDE as
>> their desktop (4 seconds or so should be enough) to get kdeinit and
>> dcop up and running.  You may want to put code to fix it in the same
>> place as the code that helps DeviceManager.
>>
>> --Jeff
>>
>>
>> Quoting Maximilian Kossick <maximilian.kossick at googlemail.com>:
>>
>> > Hi
>> > 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:
>> > http://bugs.kde.org/show_bug.cgi?id=134153
>> >
>> > 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.
>> >
>> > Cheers,
>> > Max
>> >
>> >
>> > 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
>> >> 3.5.5...
>> >>
>> >> Cheers,
>> >> Sebastian
>> >>
>> >> 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
>> >>
>> > _______________________________________________
>> > Amarok mailing list
>> > Amarok at kde.org
>> > https://mail.kde.org/mailman/listinfo/amarok
>> >
>>
>>
>> _______________________________________________
>> Amarok mailing list
>> Amarok at kde.org
>> https://mail.kde.org/mailman/listinfo/amarok
>>
> _______________________________________________
> Amarok mailing list
> Amarok at kde.org
> https://mail.kde.org/mailman/listinfo/amarok
>