desktop-packages team mailing list archive

[Lorn Potter <lorn.potter@xxxxxxxxxxxxx>]

Has that network-manager fix hit ubuntu-rtm/devel yet? Because without
these qtbearer/qnam patches, I'm still seeing images loading issues.

The problem is not manually disabling the AP, but when moving (roaming)
from one to another, i.e. moving from wlan coverage to 3g coverage, or
from 3g to wlan

If you set up a Wlan AP, connect the phone to it, and then pull the
power plug on it so that AP disappears (or walk outside), the 3g
connection will become default, but  the old non patched QNAM is still
holding on to the now non invalid wlan configuration. Refreshing to
scopes will result in nothing being downloaded. The generic plugin does
not know when something is actually connected or just the interface is
'up'. It does not generate the needed signals for QNAM to continue
functioning without tearing down the QNAM object.

Even worse, if you bootup with 3g connected, walk into wlan coverage,
the QNAM get() request will be going through the still connected 3g
connection.

The tests mentioned at
https://wiki.ubuntu.com/Process/Merges/TestPlans/Qt#Testing_networking_code_in_Qt_base
do not cover "roaming" from one connected technology to another.

-- 
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