@Michi
I guess I look at this from NetworkManager's point of view. Your either
"connected" or you're not... The network indicator reflects this, it
shows the mobile data technology if connected to the mobile operator.
If WiFi is enabled, it works like the desktop. You can easily see the
state of both WiFi and the mobile data connection by running the command
'nmcli d'.
Yea, the QNetworkAccessManager documentation isn't super clear. It also
looks like there's a lot of control provided over network configuration,
which may not actually work correctly on our platform.
With that said, it looks to me like "unknown" is the default accessible
state, until the first request is created. From the thread you posted
on qtcentre.org in comment #7, it appears that the accessible state can
be primed:
"QNetworkAccessManager::networkAccessible is not explicitly set when the
QNetworkAccessManager is created. It is only set after the network
session is initialized. The session is initialized automatically when
you make a network request or you can initialize it before hand with
QNetworkAccessManager::setConfiguration() or the
QNetworkConfigurationManager::NetworkSessionRequired flag is set."
It also includes sample code to do this:
QNetworkAccessManager* mNetworkAccessManager = new QNetworkAccessManager();
QNetworkConfigurationManager manager;
mNetworkAccessManager->setConfiguration(manager.defaultConfiguration());
--
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
