@Kyle: If no network is available, the network indicator should show it, I would think?
@Tony: I get the impression that treating "unknown" as "inaccessible" is not the right thing to do. From what I can glean, it appears that QNAM starts out in the "unknown" state and, once the first request has been made, settles into "accessible" or "inaccessible" accordingly. If that is the way it actually works, treating "unknown" as "inaccessible" would be exactly the *wrong* thing to do. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
