Bug 235301 - Creation of KIO-slaves hangs if Coherence is not available via dbus
Summary: Creation of KIO-slaves hangs if Coherence is not available via dbus
Status: RESOLVED WORKSFORME
Alias: None
Product: kio
Classification: Unmaintained
Component: kioslave (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Michael Kreitzer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-24 22:45 UTC by Michael G. Hansen
Modified: 2011-02-09 20:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael G. Hansen 2010-04-24 22:45:50 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

I am running trunk in a chroot and do not have Coherence running. When starting any application that uses KIO-slaves, for example Kate, I get error messages while solid tries to connect to Coherence and the newly started application hangs until the connection attempt times out (about 30 seconds). This happens again as soon as I open a "File open" dialog.

Debug output:
Connecting to Coherence...
QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
Calling appendChild() on a null node does nothing.

I can resolve this issue by commenting out the code in DeviceBrowserPrivate::init(), in both kdelibs/solid/solid/backends/kupnp/lib/devicebrowser_p.cpp and kdebase/runtime/kioslave/network/kupnp/lib/devicebrowser_p.cpp.

I could not yet test what happens when Coherence is running.

Mike
Comment 1 Michael G. Hansen 2010-04-24 22:48:19 UTC
Sorry, wrong product, I only searched for "UPNP".

Mike
Comment 2 Michael G. Hansen 2011-02-09 20:39:18 UTC
I tested this again in KDE 4.6 and don't observe this problem any more, therefore closing this bug report.

Michael