"You computer's clock is not synced" pop-up dialog keep appearing on start up

[s101d1]

Version: `0.11.1`
OS & Version: Antergos Linux (arch linux)
Node version: `geth 1.8.13`

When starting Ethereum Wallet or Mist, the "You computer's clock is not synced" message dialog keeps showing up.

The message dialog said I need to install ntp, and I did, but the problem still persists.

[Brisse89]

Came here to report the same thing, and found this.

A bit of additional information: My distro (Debian Sid), and probably most up to date distros have deprecated NTP in favour of the systemd service timedatectl.

To show the status of the daemon:

$ timedatectl
               Local time: fre 2019-01-04 11:13:56 CET
           Universal time: fre 2019-01-04 10:13:56 UTC
                 RTC time: fre 2019-01-04 11:13:56
                Time zone: Europe/Stockholm (CET, +0100)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

If NTP service is not active, it can be enabled like this: $ timedatectl set-ntp true

@s101d1 I recommend you uninstall the NTP package and set up timedatectl according to the above.

Developers: Ethereum Wallet needs to query timedatectl on whether the clock is synchronized or not instead of just checking if NTP is installed. You can get the information in machine readable form using 'show' instead of 'status', like this:

$ timedatectl show
Timezone=Europe/Stockholm
LocalRTC=no
CanNTP=yes
NTP=yes
NTPSynchronized=yes
TimeUSec=Fri 2019-01-04 11:21:49 CET
RTCTimeUSec=Fri 2019-01-04 12:21:49 CET

[Enelar]

+1 guys timedatectl correctly tells that im synchronized, and still mist unable to recognize that.

timedatectl show
Timezone=Europe/Moscow
LocalRTC=no
CanNTP=yes
NTP=no
NTPSynchronized=yes
TimeUSec=Wed 2019-01-23 08:52:49 MSK
RTCTimeUSec=Wed 2019-01-23 08:52:49 MSK

ntptime
ntp_gettime() returns code 0 (OK)
  time dff280c6.919e5190  Wed, Jan 23 2019  8:57:26.568, (.568822786),
  maximum error 13283740 us, estimated error 11388 us, TAI offset 0
ntp_adjtime() returns code 0 (OK)
  modes 0x0 (),
  offset 0.000 us, frequency 5.910 ppm, interval 1 s,
  maximum error 13283740 us, estimated error 11388 us,
  status 0x2001 (PLL,NANO),
  time constant 6, precision 0.001 us, tolerance 500 ppm,

2019, three years of this issue https://github.com/ethereum/mist/issues/430#issuecomment-203528485 "Next release won't query NTP." @glesaint 30 Mar 2016 issue closed

There was a thread https://github.com/ethereum/mist/issues/583#issuecomment-242960066 https://github.com/ethereum/mist/issues/583#issuecomment-244140907 with the suggestion of using timedatectl, and again, closed without fix. Whats going on?

https://github.com/ethereum/mist/issues/583#issuecomment-243114812 @fjl

The reason was that the clock is not always synchronized even though NTP is enabled (i.e. the user has just turned on ntp and it's not done yet). There should be no popup in this case.

Duh, check for both values and show popup only when both say 'no' ? Let me break down this, if it wasn't clear:

NTP=yes
NTPSynchronized=yes

No popup

NTP=no
NTPSynchronized=yes

No popup

NTP=yes
NTPSynchronized=no

No popup

NTP=no
NTPSynchronized=no

popup

Im not sure about CanNTP=yes though, someone should read manuals.

[bryanapperson]

I am seeing the same issue.