Not all distros use "ntp" service, please fix this.
xxxxxxx@kali:~/# timedatectl status
Local time: Tue 2017-12-19 14:14:17 PST
Universal time: Tue 2017-12-19 22:14:17 UTC
RTC time: Tue 2017-12-19 22:14:18
Time zone: America/Tijuana (PST, -0800)
System clock synchronized: yes
systemd-timesyncd.service active: yes
RTC in local TZ: no
Hi @pingram3541,
Mist has to perform this check so that Geth doesn't "silently fail" when the clock is not adjusted (it's their requirement). We've created a temporary flag to run on systems that do not rely on NTP.
Run mist with --skiptimesynccheckto bypass the check.
In light of trying to keep things positive here, thank you for the "temporary" flag and I understand why the check is there, just not so much with the how.
The fact of the matter is, my system's clock is not out of sync, it already uses a form of ntp service to sync and and I don't have this problem with any other wallets. Maybe this should be revisited, just saying.
This issue is similar to https://github.com/ethereum/mist/issues/583. I'm experiencing the same thing when I try to run mist on Arch.
I've submitted a PR to update the os-timesync node module that mist uses to detect whether the time is synced.
CC @alexvandesande @luclu
@jacksenechal thanks for the contribution there. I'm following it and will update it asap on Mist.
Thanks for your contribution @jacksenechal. It'll be in the next Mist version.
It is now live! please update :)