Comment 22 for bug 1528886

There's the old silo 032 still which I just updated before the holidays to be up-to-date. With the recent network manager bearer OTA 8.5 fix it's no longer obviously blocked (bug #1508945 got fixed as a side effect), but it's still not a patch set I'm comfortable considering landing before it's more widely tested because it obviously did used to cause regressions in our case, even though via the route of apparmor blocking DBus Network Manager calls.

Included network related patches (or Lorn's from upstream):
  * debian/patches/Make-sure-to-report-correct-NetworkAccessibility.patch
  * debian/patches/Make-sure-networkAccessibilityChanged-is-emitted.patch
  * debian/patches/Fix-hang-in-qnam-when-disconnecting.patch
  * debian/patches/Make-UnknownAccessibility-not-block-requests.patch

(plus changing the generic plugin skipping to be done via env var as merged in upstream)

The other bugs I've figured might be related are bug #1507769 and bug #1506015.

If there's any doubt, switching to the connectivity-api bearer might be better to do first.