I chose the right location, is there a synce button? Wondering if it is a bug, Solus did this until I update,d but this is updated, so???
To set the local time of the system clock directly:
timedatectl set-time "yyyy-MM-dd hh:mm:ss"
timedatectl set-time "2014-05-26 11:13:54"
sets the time to May 26th, year 2014, 11:13 and 54 seconds.
Please post the output of:
Whoops, not this
Also, see [HowTo] Provide System Information
I set it directly, but I did before, hope it stays. Is there a way to syce it daily?
Failed to query server: Unit dbus-org.freedesktop.timesync1.service not found.
Do you use the MATE Time & Date manager? I set it to NTP sync and had no issues with this.
Yes, indeed there is. Using:
To list timezones. Then:
timedatectl set-timezone <timezone>
<timezone> is the timezone identified in the previous step.
To set it to a NTP server.
Then enable, and start the sync service:
sudo systemctl enable --now systemd-timesyncd.service
And that, I hope, is as easy as that!
I set the timezone in GUI, so the last two comands should be enough right?
If your timezone is good, it should be fine. Check with:
$ timedatectl status Local time: Wed 2022-01-05 16:15:49 SAST Universal time: Wed 2022-01-05 14:15:49 UTC RTC time: Wed 2022-01-05 14:15:49 Time zone: Africa/Johannesburg (SAST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no
It is good.
Got Too few arguments. when I ```
Then you should be fine doing only the rest.
Ok, sorry for all this I have beem posting in support, mate.
No, it’s fine… I understand.
As long as you learn something!
See my instructions:
timedatectl set-ntp true
Ok, just changed it to the right time again & did that comand, hope it stays like it should.
One thing is forgoted
sudo systemctl enable ntpd
Don’t do that if you are running