1) QNAM was only being signalled when the online state of nm changed. Since mobile data remains online when wifi connects, the online state never changes when the default route moves to wifi. Thus QNAM/QNetworkRequest was not following the correct configuration/session. The session would never signal the connected state (because it was already connected and didn't change) This means that the request would never migrate/resume to new connection, and would wait for proper session state to actually start the operation, which would never come.
Haven't looked into why it would not timeout in a reasonable amount of time. 2) Sometimes QNAM would get confused by #1 and set itself to NotAccessible, thus blocking the request and issuing error 99 (UnknownNetworkError) -- 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/1528886 Title: Checking for updates never finishes Status in Canonical System Image: Confirmed Status in connectivity-api package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu RTM: Confirmed Bug description: Tested on krillin with SIM and data enabled OTA 8.5 stable channel Also Arale on proposed 201 Ensure phone has latest updates installed Check for update on Wifi and it reports software is up to date Turn off wifi and go to updates panel again Note that the indicator shows and active 3G data connection Checking for updates ... is shown and I see one of 3 results In all cases the log reports: 2015-12-23 15:34:19,394 - WARNING - void UpdatePlugin::Network::checkForNewVersions(QHash<QString, UpdatePlugin::Update*>&) 2015-12-23 15:44:56,007 - WARNING - Reply is not valid. In some instances I see this but not all, this is logged when the phone locks and resumes 2015-12-23 15:36:18,625 - WARNING - QObject::killTimer: Timers cannot be stopped from another thread 2015-12-23 15:36:18,625 - WARNING - QObject::startTimer: Timers cannot be started from another thread One time I saw Connect to the Internet ... In anther case it displayed this after around 5 mins when I did not allow the phone to turn off: Software is up to date In all other cases Checking for updates never finished To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528886/+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
