Comment 11 for bug 1413269

I re-tested with Qt 5.4.0 (from the ppa) and a custom build of unity-scopes-api (with switch-to-netcpp branch reverted) and I couldn't reproduce the networking issues of smartscopesproxy anymore. It looks like Qt 5.4.0 did fix that particular instance of the qt networking issue for us.

I cannot comment on the other issue that Thomas mentioned in this bug report - there is no clear scenario for reproducing seldom failures where shell plugin thinks that network is not available (because it's told so be Qt's network access manager) and passes network=false flag down to scopes with search.