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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1413269 Title: Qt network being unreliable establishing a connection Status in the base for Ubuntu mobile products: Confirmed Status in qtbase-opensource-src package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu RTM: New Bug description: Qt network manager is unreliable as it sometimes reports the device being not online when in fact it is. This manifest in bugs like bug #1409995 or some scopes querying online resources just being empty. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1413269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
