DBus deadlock with mpris player

[Simon Persson]

Hello!

I'm the author of BoomBox, a phonon based music player with an mpris2 
interface.

Lately it was taking ages to start my player, after several attempts at 
debugging this, only today did I find out that kde-telepathy (0.4.1) was 
causing this.

>From the commit to boombox I just did:

 	Kde telepathy has a mpris based "now playing" module running in the kded
    daemon, during boombox startup it detected a new player and started
    probing it. However, BoomBox was not ready to answer.. it was still
    going to do creation of other objects before going to the main loop.
    This creation (of  phonon mediaobject and kio objects) needed to talk to
    services in kded, but kded was waiting for boombox. deadlock.
    
    Resolve by creating mpris interface object last in startup phase.


So, I was able to fix this. Other programs may be trickier to reorganize 
(during debugging I observered that amarok has the same problem).

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??

Hope this helps,
Simon 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-telepathy/attachments/20120731/c837ed9b/attachment.html>