Comment 74 for bug 1357321
Revision history for this message
| Lorn Potter (lorn-potter) wrote Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu | #74 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Ok, I think I see the light now. This is an odd one.
There seems to be two connection settings (within networkmanager) for the same connection context (even in mako), one being the nm settings configuration that is actually connected (settings/2), and the other that is not flagged as active (settings/0) (both with different UUID). It is this non-active configuration that SmartScopes is holding on to and trying to connect to, which then causes nm to disconnect the other configuration.
I can work around this by faking that the Settings/0 is flagged as Active in QtBearer when there is a connection context somewhere with the same context id that is actually active.