meta-release really doesn't change often; so caching behind captive portals is a real issue.
NM can already differentiate between a captive portal and the real internet (provided the feature is enabled and configured, but we're working on that too). Update-manager probably should be a little more careful about exactly what state we track and consider to be online, rather than taking any NM_STATE_CONNECTED_* as valid; some of these may mean we're behind a captive portal and in that case should be ignored... but this needs careful validation to account for local enterprise mirrors too. Upgrading to "High"; captive portals are pretty common, and we want to be proactive about how we deal with those, given users doing upgrades, especially since we should soon have captive portal detection enabled. ** Changed in: update-manager (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/807259 Title: MetaRelease.download() Issue after Captive Portal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/807259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
