DBus deadlock with mpris player

[Martin Klapetek]

On Wed, Aug 1, 2012 at 9:53 AM, George Kiagiadakis <
kiagiadakis.george at gmail.com> wrote:

> > I'm not sure where to point the blame here.. applications or ktp.. but
> maybe
> > the kded module could sleep a few seconds after detecting a new mpris
> player
> > before it starts probing it??
>
> No, this is not a solution to a deadlock situation. The real problem
> is that both applications use QtDBus synchronously to talk to each
> other. This is *wrong*. It may become a little bit trickier because
> the QtDBus API is not optimized for asynchronous operations, but it
> should really be used asynchronously. This way, no application would
> block and wait for the other to answer and there would be no deadlock.
>

Ah, hm. I had no idea. I'll investigate how to fix it then.


> Therefore, this is a bug in both ktp and your application.
>

Therefore I retract my previous conclusion about the blame not being on us.

--
Martin Klapetek | KDE Developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-telepathy/attachments/20120801/6211ae7d/attachment.html>