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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528886 Title: Checking for updates never finishes To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
