Looks to me like QNetworkAccessManager doesn't support roaming, either
because it was built without it being enabled or it's disabled because
it's not detected as being supported; but I can see
QNetworkConfigurationManager doesn't report roaming to be supported as
per the QNetworkAccessManager documentation, and that seems to be why it
fails to notice the connection states changed.
One way to counter this would be to make sure there is proper error
checking when trying to retrieve data; it appears to me as it should be
reasonably easy to notice, from the error returned and the fact that
HTTP headers are empty, for example, that a request has failed.
The other option is to make it so that roaming is properly supported,
and that may improve the behavior of QNetworkAccessManager.
I've written a small test program that shows the issue; see lp:~mathieu-
tl/+junk/networktest.
** Changed in: qtubuntu (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => Michael Zanetti
(mzanetti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Title:
QNetworkAccessManager doesn't support roaming on Ubuntu
To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
