So basically what I'm seeing is that system-settings doesn't recognize the change of networking technology, and eventually times out after 4-5m, at which point the "Connect to the Internet" message is displayed. I have yet to see the spinner go forever as Pat suggests. I did however hit a crash in system-settings after the fourth or fifth time I ran my test scenario. I'll paste the backtrace in a subsequent comment.
I tested using a US AT&T SIM, which means I'm limited to 2G only on my krillin. I also disabled automatic updates on both phones before testing.
Here's my exact scenario, which I ran 5 times on krillin ( OTA8 + OTA8.5 ), and arale ( OTA8.5 ):
1. Boot the phone w/WiFi enabled & a previously connected access point available; after booting, verify the phone is connected to WiFi.
2. Launch SystemSettings::Updates
( Note, unlike Pat... I didn't install all available updates. So for OTA8.5 testing run today, 4 click updates are shown as available. For OTA8, an Ubuntu update is visible, along with 8 click updates. )
3. Return to main settings page
4. Disable WiFi, and *wait* for the network indicator to change from WiFi to 'E' ( on Krillin ) or 'H' ( on arale ).
5. Re-open Updates
This scenario results in three different results, partially depending on the speed of my network connection:
* updates were shown promptly ( < 30s )
* the spinner appeared, and updates were eventually shown after some delay ( 30s - 4m ); sometimes when this happened, only the Ubuntu update would be shown ( ie. I didn't see the available click updates )
* the spinner appeared, and somewhere between 4-5m, the "Connect to Internet" message would be displayed
I basically saw little difference between OTA8 and OTA8.5 in my testing on krillin. With OTA8.5, I hit the "Connect..." scenario 3/5 tries. On OTA8, I hit it 2/5 times. On arale running OTA8.5, I hit it 2/5 as well.
Note, during each test I always verified that the network connection was good by running the following two commands:
$ nmcli d
$ ping ubuntu.com
From my point of view, Pat's original scenario doesn't seem to be a regression introduced by OTA8.5.
So basically what I'm seeing is that system-settings doesn't recognize the change of networking technology, and eventually times out after 4-5m, at which point the "Connect to the Internet" message is displayed. I have yet to see the spinner go forever as Pat suggests. I did however hit a crash in system-settings after the fourth or fifth time I ran my test scenario. I'll paste the backtrace in a subsequent comment.
I tested using a US AT&T SIM, which means I'm limited to 2G only on my krillin. I also disabled automatic updates on both phones before testing.
Here's my exact scenario, which I ran 5 times on krillin ( OTA8 + OTA8.5 ), and arale ( OTA8.5 ):
1. Boot the phone w/WiFi enabled & a previously connected access point available; after booting, verify the phone is connected to WiFi.
2. Launch SystemSettings: :Updates
( Note, unlike Pat... I didn't install all available updates. So for OTA8.5 testing run today, 4 click updates are shown as available. For OTA8, an Ubuntu update is visible, along with 8 click updates. )
3. Return to main settings page
4. Disable WiFi, and *wait* for the network indicator to change from WiFi to 'E' ( on Krillin ) or 'H' ( on arale ).
5. Re-open Updates
This scenario results in three different results, partially depending on the speed of my network connection:
* updates were shown promptly ( < 30s )
* the spinner appeared, and updates were eventually shown after some delay ( 30s - 4m ); sometimes when this happened, only the Ubuntu update would be shown ( ie. I didn't see the available click updates )
* the spinner appeared, and somewhere between 4-5m, the "Connect to Internet" message would be displayed
I basically saw little difference between OTA8 and OTA8.5 in my testing on krillin. With OTA8.5, I hit the "Connect..." scenario 3/5 tries. On OTA8, I hit it 2/5 times. On arale running OTA8.5, I hit it 2/5 as well.
Note, during each test I always verified that the network connection was good by running the following two commands:
$ nmcli d
$ ping ubuntu.com
From my point of view, Pat's original scenario doesn't seem to be a regression introduced by OTA8.5.