touch-packages team mailing list archive

[Lorn Potter <lorn.potter@xxxxxxxxx>]

I agree, since nothing controls the connections through QtBearer (and
the platform doesn't want that), and AP lists are not allowed in
contained apps, it makes sense to simply remove them.

I've fixed up that patch in regards to d'tor disconnects, removed some
redundant code.

And since it was a small change, I fixed up the defaultConfiguration
code that would not correctly detect when the default route changed from
mobile to wifi, thus possibly allowing network requests to go through
expensive mobile data when wifi is available.




** Patch added: "net-beaerer-nm-disconnect-ap-signals3.patch"
   https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1480877/+attachment/4523931/+files/net-beaerer-nm-disconnect-ap-signals3.patch

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in buteo-syncfw package in Ubuntu RTM:
  New
Status in location-service package in Ubuntu RTM:
  In Progress
Status in maliit-framework package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in sync-monitor package in Ubuntu RTM:
  New

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions