Attached ofonod log when this happens, from just before disconnect through the reconnect.
I think the new bearer backend is exposing a bug elsewhere, as this happens even when there no QNetworkSession opened (which calls to activate whatever configuration). Whether it is in NetworkManager, ofonod, rild, or even elsewhere will take more digging and perhaps other eyes. _something_ is trying to activate the 3g context (not QtBearer), even if it is already activated (or appears to be from nm) which causes ofonod to deactivate it, which then gets re-activated by the autoconnect. ** Attachment added: "ofonod log" https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1357321/+attachment/4257000/+files/ofonod.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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
