https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #19 from David Faure <fa...@kde.org> --- The last bt is very informative: * the main thread is in a BlockingQueuedConnection signal emission, the signal is signalNeedsConnecting(), and it's handled by the dbus thread. * the dbus thread is in QDBusConnectionPrivate::handleObjectCall, waiting for the main thread using a semaphore after posting an event. So this deadlocks, because the main thread will only get to that posted event once it's done with the current call it's doing. This is unrelated to the messageFilter() stuff I was involved with, in kded. It's a bug in QtDBus in 5.6 AFAICS. I have no idea what the fix would be, because it seems like a severe design issue to me, to use both A waits for B and B waits for A. -- You are receiving this mail because: You are watching all bug changes.
