Can't find "Montreal" when setting Time Zone
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
I can't find Montreal in the timezone search box, even though it is present in the /usr/share/zoneinfo database.
What I did:
Settings > Time & Date > Time Zone > Click in the search box and start typing Mont...
What I expected:
Autocompletion.
What happened:
No completion found.
$ lsb_release -rd
Description: Ubuntu 20.04 LTS
Release: 20.04
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-
ProcVersionSign
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 9 23:59:01 2020
ExecutablePath: /usr/bin/
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-control-
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in gnome-control-center (Ubuntu): | |
status: | New → Triaged |
summary: |
- Missing entry for timezone database when setting timezone via the text - search + Can't find "Montreal" when setting Time Zone |
Changed in gnome-control-center (Ubuntu): | |
importance: | Low → Medium |
I did a little bit more digging. Perhaps this comment would help explain why there is a problem: https:/ /github. com/eggert/ tz/commit/ 45dcf69b45087cf f50282d4da64b86 a7d705ddf3# commitcomment- 4602830
In release v2013e "America/Montreal" was removed from the zone.tab file, and incorrect programs may assume that zone.tab is the only authoritative list of valid TZs.
Quoting the aformentioned linked comment:
> The TZ setting 'America/Montreal' should work as it did before, for all time stamps after 1970.
> My guess is that PHP, or some other program that you're using, is looking at zone.tab directly, under the incorrect assumption that only the strings listed in zone.tab are valid TZ settings. You'd have a similar problem with 'Asia/Istanbul', 'Europe/Nicosia', 'Asia/Saigon', etc.; these are all valid TZ settings that are not in zone.tab. You need to track down which program is making this invalid assumption, and fixing it to either (1) not insist that the TZ setting be in zone.tab, or (2) not insist on using TZ settings like America/Montreal and Asia/Istanbul that work but are not in zone.tab."
I noticed that `timedatectl list-timezones` also fails to list a valid Montreal timezone, and it seems that this is a systemd util, pulling its data from I don't know where... So maybe the bug is upstream.