** Changed in: calamares
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898501
Title:
Calamares fails to parse GeoIP results correctly in JSON
To manage notif
** Changed in: geoip-database (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898501
Title:
Calamares fails to parse GeoIP results correctly in JSON
To manage
I imagine this fix was not SRU'ed to Focal and that is why you still see
it there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898501
Title:
Calamares fails to parse GeoIP results correctly in JS
** Also affects: geoip-database (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898501
Title:
Calamares fails to parse GeoIP results correctly in
This bug still ocurring on Focal daily ISO
http://cdimage.ubuntu.com/lubuntu/focal/daily-live/20201022/focal-
desktop-amd64.iso
Tested on 2 seperate installs/machines.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Looks like we were mistaken after all. Upstream discovered the issue was
apparently ipapi.co rate limiting requests from the default user agent,
which is why `curl`/Firefox never showed any issues where Calamares did.
I flipped locale.conf over to use https://geoip.kde.org/v1/calamares and
the time
** Changed in: calamares (Ubuntu)
Status: Confirmed => Triaged
** Bug watch added: Calamares Issues #1540
https://github.com/calamares/calamares/issues/1540
** Also affects: calamares via
https://github.com/calamares/calamares/issues/1540
Importance: Unknown
Status: Unknown