desktop-packages team mailing list archive

[Lorn Potter <lorn.potter@xxxxxxxxxxxxx>]

I did more testing of the generic plugin, and it's not as bad as I
thought, in that it does signal when interfaces become the default
route.

But my comment still stands that without these patches (in the least,
the patch to QNAM itself is especially needed) the defaultConfiguration
internal to QNAM will not switch, which _will_ cause people to wonder
why their mobile data is being used while the indicator shows that they
are connected to wifi, and _will_ cause people to use up their expensive
mobile data.

I question the removal of this from TOPBLOCKER's and rtm.

QtBearer is not just about starting and stopping the connections, QNAM
uses it internally for every get()  request.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1357321

Title:
  QNetworkAccessManager doesn't support roaming on Ubuntu

Status in Platform API:
  Invalid
Status in The Savilerow project:
  New
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “ofono” package in Ubuntu:
  Invalid
Status in “qtbase-opensource-src” package in Ubuntu:
  In Progress
Status in “qtbase-opensource-src” package in Ubuntu RTM:
  New

Bug description:
  scope images load fine in wifi, but not on hsdpa even when there is
  good connectivity and browsing works well. Results are return, but
  images do not load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions