So, in the case of an incorrect APN, it's my assumption that the APN Editor will *always* notify NM after adding a new custom Internet context ( ie. because fixing isn't yet allowed ). We should verify this with the System Settings team.
I *think* you should be able to re-create the first scenario by adding a test hook env variable that causes a failure to be returned to a SETUP_DATA_CALL. Then clear the variable and reboot. I'll give this a try. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1349273 Title: NM does not retry opening mobile data on reboot Status in “network-manager” package in Ubuntu: New Bug description: In case NM has failed to open any mobile data context, it will not re- try when rebooting the phone. This happened with a pre-paid SIM with no credit: opening a data context for it obviously failed. After adding credit to the SIM, I followed the instructions from the operator to reboot the phone to get data. However, after rebooting I had no mobile data. Taking a look to system settings, cellular data was set to "Off" and I was able to revert the situation marking the "2G/3G/4G" option. Make NM retry the list of contexts in case no context was ever active on previous boot would make life easier for the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1349273/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
