Hi Grandpa Norizan! 😄
Ahhh... this is actually a very interesting Linux mystery!
If the date changes correctly but the time refuses to stay at what you set, then in a Zorin OS 18 Live DVD/USB session, the most common culprit is:
1. systemd-timesyncd or NTP is immediately correcting the clock
When you run:
Linux sets the time.
But a few seconds later, the network time synchronization service may contact an Internet time server and say:
"Nope! That's not the correct time!" 😄
Then it automatically adjusts the clock again.
Check:
You may see something like:
If NTP is active, try:
Then:
Finally verify:
2. Time Zone is incorrect
I have seen this happen many times.
The time may actually be correct in UTC, but the timezone is wrong.
Check:
Look for something like:
Since you are in Malaysia, it should normally be:
If it shows:
or
then the displayed time can be several hours off even when the date is correct.
To fix:
3. Live DVD mode sometimes behaves differently
Remember, Grandpa Norizan, you're not running a normal installed Zorin OS.
You're running:
A Live system may:
- detect hardware differently
- ignore some BIOS clock settings
- re-sync time during boot
- start network synchronization automatically
while your installed Debian 13 may already be configured exactly how you like it.
4. Hardware Clock (RTC) may be set differently
Check:
Look for:
and
Sometimes Linux interprets the motherboard clock as UTC while Windows interprets it as Local Time.
This can create strange offsets.
My strongest suspicion 🕵️
Because you said:
✅ Date changes correctly
❌ Time does not remain correct
and
✅ The same command works perfectly in Debian 13
I would bet a cup of Malaysian Teh Tarik ☕ that NTP synchronization is active in Zorin 18 Live mode and is immediately overriding your manually-set time.
Try these commands and show me the output:
and
immediately after you execute:
The output of timedatectl will probably reveal the culprit very quickly! 😄🔍
No comments:
Post a Comment