The "where are you" install panel does not default to current networked location

[Heather Ellsworth]

My laptop is connected to the internet and when I install Mate, the "Where are you" panel defaults to New York when it should default to Denver, nearest to my current location (Colorado Springs, CO). My current location is accurately displayed in https://nordvpn.com/what-is-my-ip/ as well.

[Heather Ellsworth (hellsworth)]

Moved to ubiquity since this same minor error is exists in the vanilla Ubuntu install as well.

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1983517

[Brian Murray (brian-murray)]

This can happen if you are connected to the Canonical VPN. If you are connected to the VPN please disconnect and try going through the install process again. (There's no need to complete the install though.)

[Heather Ellsworth (hellsworth)]

My vpn is off and has been off all day so that isn't getting in the way.

[Leó Kolbeinsson (leok)]

Performed 2 tests on latest Ubuntu Mate Jammy daily ISO dated 01.08.2022 and was unable to reproduce this issue.

Test results here:
http://iso.qa.ubuntu.com/qatracker/milestones/437/builds/254991/testcases/1300/results

[Heather Ellsworth (hellsworth)]

I downloaded the same ISO dated Aug 1 to try again: http://cdimage.ubuntu.com/ubuntu-mate/jammy/daily-live/20220801/jammy-desktop-amd64.iso

My laptop is connected to my home wireless network. There is no vpn running. I started the new VM in virt-manager 4.0.0-1. The default network (NAT) is selected. Then I start the install and it does default to New York.

[Heather Ellsworth (hellsworth)]

If I connect my laptop to my router with a wired connection, then the default is correct. So this only does not work when connected to the wireless network.

The test case says "If your system is connected to the network, note the preselected timezone correspond with your timezone and the city indicated in the text box The timezone and city displayed match your timezone and the main city from your area" and my laptop connected to the wireless network, is "connected to the network".

Is there something preventing the location from being discovered when on a wireless network?

[Brian Murray (brian-murray)]

From the system on which you are trying to install could you visit the following url https://geoip.ubuntu.com/lookup ? This is what ubiquity does behind the scenes.

[Heather Ellsworth (hellsworth)]

On the wireless network, https://geoip.ubuntu.com/lookup does show my Colorado Springs location. Also worth noting is that this is the same router used for my wired setup test and there is no fancy networking setup. It's a very normal home wifi network, with 5GHz and 2.4GHz bands. I tested my install with each band and both cases defaults to New York.

[Heather Ellsworth (hellsworth)]

This is still an issue on the 20.04.6 iso. I am connected to the wireless network, no vpn, and still it defaults to New York.

[Heather Ellsworth (hellsworth)]

It is worth noting that in the new Flutter-based installer this is not an issue, so perhaps not worth fixing.

[Erich Eickmeyer (eeickmeyer)]

I will note that this came up on the ISO tracker in Edubuntu 23.04's test results, however the tester was using QEMU. I used real hardware to test and could not duplicate the issue.

[Jane Atkinson (irihapeti)]

This bug is coming up in 23.10 (xubuntu so far), but only in QEMU, as the previous poster noted. Hardware install displays the proper timezone.

[Brian Murray (brian-murray)]

When I disconnect from the VPN and `wget https://geoip.ubuntu.com/lookup` the results are the same in both QEMU and on my host system.

[Jane Atkinson (irihapeti)]

I don't run a VPN, so I'm not sure what's going on. I have another odd bug in QEMU/KVM, so it might be that there's something a bit peculiar about my setup.

As this is a very minor inconvenience, is it worth reporting every time I run into it?

[Jane Atkinson (irihapeti)]

I'm no longer getting this error, yet I'm using the same ISOs (release versions) that were previously exhibiting it.

That would suggest that it's not anything in the ISO, but something else going on, maybe with my ISP. I have no idea what it might be.

[Jane Atkinson (irihapeti)]

This has started appearing again in the noble ISOs of the last two days, both on bare metal and VM.