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. -- 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: [TOPBLOCKER] 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
