Ubiqutiy erroneously sees North Idaho in US Mountain Time

Bug #1895716 reported by Erich Eickmeyer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
geoip-database (Ubuntu)
New
Undecided
Unassigned
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

When installing Ubuntu on any machine connected to the internet in North Idaho (the panhandle north of the Salmon river), the time zone is erroneously detected as being in Mountain time.

I believe this bug stems from the idea that the entire state of Idaho, and indeed the most popular portion, is in Mountain time. However, the Northern panhandle is in Pacific time. The Salmon river is used to divide time zones in Idaho as it spans from the crest of the Bitterroot mountains at the Idaho/Montana border to the Snake River at the Idaho/Oregon border.

This includes all cities north of the Salmon river in Idaho such as Moscow (home to the University of Idaho), Lewiston, Orofino, Coeur d'Alene, Grangeville, Sandpoint, and Bonners Ferry.

I realize that the location is being detected via IP, so it shouldn't be too hard to implement this separation.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity (not installed)
Uname: Linux 5.8.8-surface x86_64
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 15 10:17:35 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
InstallationDate: Installed on 2020-09-15 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :
description: updated
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

A simple check with https://geoip.ubuntu.com/lookup turns up this issue for me:

<Response>
  <Ip>xxx.xxx.xxx.xxx</Ip> <!-- REDACTED -->
  <Status>OK</Status>
  <CountryCode>US</CountryCode>
  <CountryCode3>USA</CountryCode3>
  <CountryName>United States</CountryName>
  <RegionCode>ID</RegionCode>
  <RegionName>Idaho</RegionName>
  <City>Coeur D'alene</City>
  <ZipPostalCode>83815</ZipPostalCode>
  <Latitude>47.7248</Latitude>
  <Longitude>-116.7890</Longitude>
  <AreaCode>208</AreaCode>
  <TimeZone>America/Denver</TimeZone>
</Response>

Everything except the TimeZone field returns incorrect. Again, everything north of the Salmon River should return America/Los Angeles.

Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Correction: everything except the TimeZone field returns correct.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.