I agree with Kyle that "unknown" state is pretty useless, that said, as it's defined by QNetworkAccessManager, we can't really get rid of it without proposing a change to QNetworkAccessManager API. Thus I agree with Michi that for now scopes and/or the scopes framework should treat "unknown" the same as "disconnected".
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1502282 Title: "unknown" connectivity status problematic To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1502282/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
