| Summary: | Creation of KIO-slaves hangs if Coherence is not available via dbus | ||
|---|---|---|---|
| Product: | [Unmaintained] kio | Reporter: | Michael G. Hansen <mike> |
| Component: | kioslave | Assignee: | Michael Kreitzer <mrgrim> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Sorry, wrong product, I only searched for "UPNP". Mike I tested this again in KDE 4.6 and don't observe this problem any more, therefore closing this bug report. Michael |
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