[Bug 310826] Amarok startup hangs for 5 seconds in KSystemTimeZonesPrivate::instance() - race condition with Telepathy Integration kded4 Module

[Matěj Laitl]

https://bugs.kde.org/show_bug.cgi?id=310826

Matěj Laitl <matej at laitl.cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amarok-bugs-dist at kde.org,
                   |                            |kde-telepathy-bugs at kde.org
            Summary|Amarok startup hangs for 5  |Amarok startup hangs for 5
                   |seconds in                  |seconds in
                   |KSystemTimeZonesPrivate::in |KSystemTimeZonesPrivate::in
                   |stance()                    |stance() - race condition
                   |                            |with Telepathy Integration
                   |                            |kded4 Module

--- Comment #3 from Matěj Laitl <matej at laitl.cz> ---
Okay, it's definitely caused by Telepathy Integration kded4 Module, when I
start a new session without it running, I'm unable to reproduce the bug. When I
add KTP Presence applet to Plasma Desktop, which triggers Telepathy Integration
kded4 Modul load, the bug appears on next Amarok startup.

One may wonder what Telepathy could do with MPRIS. I've used "Now Listening to"
idle message functionality in KDE Telepathy in past, so that may be the use.

The question is now how to solve this. A simple work-around could be to pospone
publishing the MPRIS interface in Amarok a few seconds, but this seems hacky. A
"proper" solution IMO would be if both KSystemTimeZonesPrivate::instance() and
TelepathyMPRIS::detectPlayers() used *async* DBUS methods, if possible.

Should this bug be reassigned to KDE Telepathy? The
KSystemTimeZonesPrivate::instance() situation looks suboptimal to me.

-- 
You are receiving this mail because:
You are on the CC list for the bug.