This is really odd. Digging into this, it appears that something in the system other than QtBearer backend is causing this.
Attached is a dbus-monitor log. The connection never gets fully activated, which goes along with the log: Nov 7 16:45:37 ubuntu-phablet NetworkManager[1333]: <warn> DNS: plugin dnsmasq update failed Nov 7 16:45:37 ubuntu-phablet NetworkManager[1333]: <info> Removing DNS information from /sbin/resolvconf There is nothing in the backend that activates or deactivates the connection by itself. Although if I remove the plugin, the connection stabilizes. This makes be believe that there is something else behaving badly since this plugin is now working more like it should (it works fine and passes Qt's auto tests on desktop with wifi and cable ethernet) Since I am not totally sure either way about this, I will continue to look at this plugin. ** Attachment added: "nm-dbus-monitor.log" https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1357321/+attachment/4255587/+files/nm-dbus-monitor.log -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
