Page MenuHomeSolus

Time Zone
Open, NormalPublic

Description

I live in the Chicago time zone (UTC -0500). I just installed Solus on a laptop for someone who lives in the New York time zone (UTC -0400). During the installation process, I configured the machine for the New York time zone (UTC -0400).

I have since opened the Date & Time applet and configured it for:

  1. Automatic Date & Time
  2. Automatic Time Zone

When I type

Code: Select all

timedatectl status

the results indicate the following:
Local time is UTC -0400
Universal Time: is UTC
RTC Time: is set to UTC
Time Zone: America/New York (EDT, -0400)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
DST active: yes

So, my concern is that even though I have enabled the Automatic Time Zone option in the Date & Time applet, the time zone which was specified during the installation process seems to be sticky. Therefore, when this laptop travels across time zones, the clock will not automatically adjust. Case in point, the laptop is currently, physically in the Chicago time zone, but it still thinks that it is in the New York time zone.

Related Objects

RenHoek created this task.Jun 15 2017, 8:20 PM

The split auto-locator with time zone and clock setting can be activated. The automatic time setting can be set for the time zone according to the active position. There is a tzupdate software for this.

https://github.com/cdown/tzupdate

lots-of-stuff added a subscriber: lots-of-stuff.EditedMar 31 2018, 3:52 AM

@RenHoek For what it's worth, when I run timedatectl status I get a line that has systemd-timesyncd.service active: yes, which I don't see in your output. I believe this enables automatic time updating via NTP.

Sethox added a subscriber: Sethox.May 12 2018, 5:11 PM

Weird, I just did what @lots-of-stuff said and well..

asiq@phasedraco ~ $ timedatectl status
                      Local time: lör 2018-05-12 19:04:01 CEST
                  Universal time: lör 2018-05-12 17:04:01 UTC
                        RTC time: lör 2018-05-12 17:04:01
                       Time zone: Europe/Stockholm (CEST, +0200)
       System clock synchronized: yes
systemd-timesyncd.service active: no
                 RTC in local TZ: no


asiq@phasedraco ~ $ sudo systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2018-05-12 18:03:38 CEST; 1h 0min ago
     Docs: man:systemd-timesyncd.service(8)
 Main PID: 693 (systemd-timesyn)
   Status: "Synchronized to time server 216.239.35.8:123 (time3.google.com)."
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/systemd-timesyncd.service
           └─693 /usr/lib/systemd/systemd-timesyncd

maj 12 18:03:38 phasedraco systemd[1]: Started Network Time Synchronization.
maj 12 18:03:38 phasedraco systemd-timesyncd[693]: The system is configured to read the RTC time in the local time zone. This mode can not be fully supported. All system time to RTC updates are disabled.
maj 12 18:03:41 phasedraco systemd-timesyncd[693]: Network configuration changed, trying to establish connection.
maj 12 18:03:41 phasedraco systemd-timesyncd[693]: Network configuration changed, trying to establish connection.
maj 12 18:05:14 phasedraco systemd-timesyncd[693]: Synchronized to time server 216.239.35.8:123 (time3.google.com).

Seems like timedatectl status thinks that systemd-timesyncd.service is inactive even though going to systemctl to check the status it says it's running.

I can't reproduce this, is it still an issue?

DataDrake triaged this task as Needs More Info priority.Oct 8 2018, 11:26 AM
mramish added a subscriber: mramish.EditedOct 12 2018, 1:21 PM

Problem persists. Installed Budgie 64 bit with one of the new isos:

[weasel@citadel ~]$ timedatectl status
               Local time: Fr 2018-10-12 15:18:38 CEST
           Universal time: Fr 2018-10-12 13:18:38 UTC
                 RTC time: Fr 2018-10-12 13:18:38
                Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no
[weasel@citadel ~]$ sudo systemctl status systemd-timesyncd.service
Passwort: 
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2018-10-12 11:52:28 CEST; 3h 26min ago
     Docs: man:systemd-timesyncd.service(8)
 Main PID: 596 (systemd-timesyn)
   Status: "Synchronized to time server 216.239.35.8:123 (time3.google.com)."
    Tasks: 2 (limit: 4915)
   Memory: 1.9M
   CGroup: /system.slice/systemd-timesyncd.service
           └─596 /usr/lib/systemd/systemd-timesyncd

Okt 12 11:52:28 citadel systemd[1]: Started Network Time Synchronization.
Okt 12 11:52:28 citadel systemd-timesyncd[596]: request_name_destroy_callback n_ref=1
Okt 12 11:52:29 citadel systemd-timesyncd[596]: Network configuration changed, trying to establish connection.
Okt 12 11:52:29 citadel systemd-timesyncd[596]: Network configuration changed, trying to establish connection.
Okt 12 11:56:01 citadel systemd-timesyncd[596]: Synchronized to time server 216.239.35.8:123 (time3.google.com).

ATM iam in the Helsinki area so the timeszone is wrong.

This machine is no longer in my possession, nor can I conveniently pop over to the other side of the country to check it, so I thank @mramish for confirming that this is still an issue.

JoshStrobl raised the priority of this task from Needs More Info to Normal.Nov 4 2018, 12:16 PM
JoshStrobl moved this task from Backlog to System and Configuration Fixes on the Software board.