@kgunn: we have not yet landed anything to the archives since Lorn's patches are in the upstream 5.4 git, so yes it's still critical.
Test results with the 5.3 ubuntu-rtm/landing-022 PPA (backported patches from Lorn's commits) would be welcome by anyone capable of testing it. I've added three more Lorn's patches today and the build has finished: * debian/patches/Make-QtBearer-networkmanager-backend-respond-to-wire.patch * debian/patches/Support-dual-sim-in-QtBearer-s-networkmanager-backen.patch * debian/patches/make-qtbearer-networkmanager-defaultConfiguration-mo.patch Anything that improves the situation and does not regress would be welcome to be landed to the archives early next week. I've found it a bit hard to test the scopes so that results would be consistent (before/after) and without Unity 8 crashes, but there are recent improvements to the crash situation now on the latest image. Saviq now mentioned that "rm -rf ~/.cache/unity8-dash" in-between would be a good idea, to remove cached images and such. My suggestion of testing: 1. 3G only, wifi "disabled" 2. 3G only, wifi "enabled" but no known access points 3. compare to wifi enabled and connected I've tested the 1. in a way that I --bootstrap flash the device, and then without ever connecting to wifi, connect to 3G network and upgrade to the PPA over 3G. This is a potential real situation worth simulating. -- 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
