calamares selected wrong timezone

Bug #1904974 reported by Chris Guiver
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
calamares (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Lubuntu hirsute daily install on dc7700 with internet

https://ipapi.co/json reports
---

ip "58.7.111.61"
version "IPv4"
city "Melbourne"
region "Victoria"
region_code "VIC"
country "AU"
country_name "Australia"
country_code "AU"
country_code_iso3 "AUS"
country_capital "Canberra"
country_tld ".au"
continent_code "OC"
in_eu false
postal "3004"
latitude -37.8411
longitude 144.9799
timezone "Australia/Melbourne"
utc_offset "+1100"
country_calling_code "+61"
currency "AUD"
currency_name "Dollar"
languages "en-AU"
country_area 7686850
country_population 24992369
asn "AS7545"
org "TPG Telecom Limited"
---

However calamares on screen is showing my location as Perth (west side of aussieland, not east side; 3hrs out)

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: calamares 3.2.32.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
.etc.calamares.modules.finished.conf:
 ---
 restartNowMode: user-checked
 restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.partition.conf:
 efiSystemPartition: "/boot/efi"
 enableLuksAutomatedPartitioning: true
 userSwapChoices: none
 drawNestedPartitions: true
 defaultFileSystemType: "ext4"
.etc.calamares.modules.shellprocess_logs.conf:
 ---
 dontChroot: true
 timeout: 30
 script:
     - calamares-logs-helper @@ROOT@@
.etc.calamares.modules.unpackfs.conf:
 ---
 unpack:
     - source: "/cdrom/casper/filesystem.squashfs"
         sourcefs: "squashfs"
         destination: ""
ApportVersion: 2.20.11-0ubuntu51
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.455
CurrentDesktop: LXQt
Date: Fri Nov 20 11:56:55 2020
LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201119)
RelatedPackageVersions:
 calamares-settings-ubuntu-common 1:20.10.11
 calamares-settings-lubuntu 1:20.10.11
 xfsprogs 5.6.0-1ubuntu4
 btrfs-progs 5.9-1
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Chris Guiver (guiverc) wrote :
Revision history for this message
Chris Guiver (guiverc) wrote :

session.log at completion of install

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

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/1904974

tags: added: iso-testing
Revision history for this message
Chris Guiver (guiverc) wrote :

Another QA-test install on different box (d755-8) and same issue.
Web search reported me in Melbourne, but calamares on screen said Perth

Identical IP address (dynamic); but my ISP's head office is Subiaco (Perth) WA which is where it reports, and occasionally my GeoIPlocation reports me at that location.. so I wouldn't rule out an ISP issue.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in calamares (Ubuntu):
status: New → Confirmed
Revision history for this message
Leó Kolbeinsson (leok) wrote :

QA test Focal daily Lubuntu 07.12.2020 http://cdimage.ubuntu.com/lubuntu/focal/daily-live/20201207/focal-desktop-amd64.iso

Machine tested Lenovo V14 ILL

Calamares incorrectly selecting New York as location - correct location is Reykjavik,Iceland

Revision history for this message
Leó Kolbeinsson (leok) wrote :

Attached the apport file comment "6 above

Revision history for this message
Leó Kolbeinsson (leok) wrote :

Ran test on another box this time in a VM with same result.

InWin BL641 i5-10400 - QA test Focal daily Lubuntu 07.12.2020 http://cdimage.ubuntu.com/lubuntu/focal/daily-live/20201207/focal-desktop-amd64.iso

Calamares incorrectly selects New York as location.

Revision history for this message
Leó Kolbeinsson (leok) wrote :

QA test Focal daily Lubuntu 09.12.2020 http://cdimage.ubuntu.com/lubuntu/focal/daily-live/20201209/focal-desktop-amd64.iso

Tested 2 machines : http://iso.qa.ubuntu.com/qatracker/milestones/408/builds/223949/testcases/1701/results

1. InWin BL641 i5-10400 - (running in VirtualBox)
2. Lenovo V14 IIL i3-1005G1

In both tests Calamares incorrectly selects New York as location.

Revision history for this message
Chris Guiver (guiverc) wrote :

Recent installs I've had it select the correct timezone, but calamares is reporting me in different cities.

Once today it reported me in Melbourne AU, I exited calamares as I had a mounted drive preventing full-disk install, on re-entry of calamares my location had changed to Sydney (same timezone, but different city).

Reboot & re-install (another test) & it's reporting me in Sydney again, but ask firefox my GeoIP location and it reports Melbourne as my primary box does.

Reporting the correct TIMEZONE but wrong city is minor, but may worry end-users, esp. those not good with geography. (last qa-test install before today had me in Hobart, still correct timezone but wrong island).

Revision history for this message
Chris Guiver (guiverc) wrote :

Three ~identical QA-test installs on same box today with same type of install (replace partition) exploration of different issue
- dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)

Locations reported by Calamares during each installs

- Sydney AU
- Melbourne AU
- Sydney AU

Both are in same time zone, internet the same on each, and my main box hasn't shown any disconnections to freenode (ie. my dynamic IP address hasn't changed).

Max 5 mins between each install (time required to close up QA-test on iso.qa.ubuntu.com & document findings on featherpad on unrelated reason for these installs)

Revision history for this message
Dan Simmons (kc2bez) wrote :

The release notes for Focal have been updated regarding this issue. For the record, it is possible to select the correct timezone manually during the install even if the automatic detection fails.

To post a comment you must log in.