Hi,
Time change in Artix when i go from archs to debian systems. Windows is not installed. Date is o”k in debians.
When i run the command timedatectl it is responding that it do not exist ... How to set time here?.
I'm just traying to do something:
[[kaos keos]# LANG=C pacman -S tzdata
warning: tzdata-2017c-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) tzdata-2017c-1
Total Installed Size: 1.82 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [######################] 100%
(1/1) checking package integrity [######################] 100%
(1/1) loading package files [######################] 100%
(1/1) checking for file conflicts [######################] 100%
(1/1) checking available disk space [######################] 100%
:: Processing package changes...
(1/1) reinstalling tzdata [######################] 100%
[kaos keos]# LANG=C timedatectl set-timezone America/Newyork
bash: timedatectl: no se encontró la orden
[kaos keos]#
it is saying that this command do not exist./code]
Thanks.
I use "timeset-gui" from the AUR works well for me.
it works.
thank you very much!
The canonical way of setting the time zone in UNIX/LINUX is by symlinking /etc/localtime to the respective timezone info file.
# ln -sf /usr/share/zoneinfo/Europe/Athens /etc/localtime
I've had the same problem with arch and non-arch distros fighting the hw clock or misinterpreting it.
Ok, I set the tz as you said, next day I boot up and it is 2hrs off.
If I don't boot the other system it stays where it is. When I set it here and go to the other the other one is off.
I must try the same command on that one.
The 2-hour offset suggests the UTC-EET difference is applied on your localtime. Ergo, one of the two systems stores localtime in RTC instead of UTC.
Does not surprise me. If I remember correctly ubuntu and debian during install if they detect windows use rtc instead of utc.
Back again ... once i turn off the PC and change to Debian and comeback to Arch , the time is wrong again ...
i tray to install timedatectl-restorer but there are some problem with PGP 1D1F0DC78F173680
The result from option nano /etc/localtime is not given anything understandable:
GNU nano 2.9.1 /etc/localtime
TZif2^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^E^@^@^@^E^@^@^@^@^@^@^@�^@^@^@^E^@^@^$
@p��9`ˈ�p�#�p�`���u���@���U��� ���5���^@���^U���������p��e��މpݩ�` kp߉d`��Mp�iF`$
��`^K��p^L٢�
�gp^N���^O���^P�f�^Q�e�^RyH�^SiG�^TY*�^UI)�^V9^L�^W)^K�^X")`^Y^H��^Z^B^K`^Z�
p^[��`^\��p^]��`^^��p^_��` v^@�!��`"U��#j��$5��%J��&^U��'*s�'��p)
U�)ޥp*�7�+��p,�T`-�ip.�6`/~Kp0�^X`1gg�2r�`3GI�4R�`5'+�62�`7^G
�8^[��8���9���:���;۞�<��p=���>��p?�b�@o�pA�^?`BO�pCda`D/vpEDC`E���G-_�Gӊ�I
A�I�l�J�#�K��pL�@`M|kpN�"`O\MpP�^D`Q</pRu�`S^\^QpTU�`T��pV5�`V�^O�X^^��X���Y���$
xpeG/`e�Zpg'^Q`g�<pi^F�`i�^^pj��`k�:�l���mv^\�n���oU��p���q5��ro��s^U��tOy�t��p$
@p������9`����ˈ�p�����#�p�����`�������u�������@�������U������� �������5�������^$
��`^@^@^@^@^K��p^@^@^@^@^L٢�^@^@^@^@
�gp^@^@^@^@^N���^@^@^@^@^O���^@^@^@^@^P�f�^@^@^@^@^Q�e�^@^@^@^@^RyH�^@^@^@^@^Si$
p^@^@^@^@^[��`^@^@^@^@^\��p^@^@^@^@^]��`^@^@^@^@^^��p^@^@^@^@^_��`^@^@^@^@ v^@�$
U�^@^@^@^@)ޥp^@^@^@^@*�7�^@^@^@^@+��p^@^@^@^@,�T`^@^@^@^@-�ip^@^@^@^@.�6`^@^@^@$
�^@^@^@^@8^[��^@^@^@^@8���^@^@^@^@9���^@^@^@^@:���^@^@^@^@;۞�^@^@^@^@<��p^@^@^@$
A�^@^@^@^@I�l�^@^@^@^@J�#�^@^@^@^@K��p^@^@^@^@L�@`^@^@^@^@M|kp^@^@^@^@N�"`^@^@^$
xp^@^@^@^@eG/`^@^@^@^@e�Zp^@^@^@^@g'^Q`^@^@^@^@g�<p^@^@^@^@i^F�`^@^@^@^@i�^^p^@$
EST5EDT,M3.2.0,M11.1.0
finally i can install timedatectl-restorer but but i don't know what to do with:
[kaos keos]# LANG=C timedatectl-restorer
usage: timedatectl-restorer [-h] [-r] [-a s] timefile runfile
timedatectl-restorer: error: the following arguments are required: timefile, runfile
[kaos keos]#
timedatectl-restorer -h should tell you what -r and -a do and perhaps also s
I let ntpd set it
but hwclock works
[www3 ~]# hwclock
2017-12-27 10:22:47.327226-0500
tzselect - and yes I remember this not working correctly on the install. I'm trying to remember if I needed to change permisions with ntpd. I remember it was tangled. Time Zone itself, that selection software has changed over the last 2 years or so. And the time zone packages themselves had to be reworked after the changle to day light saving time dates. I had to fix it all post install.
or his HW Clock is set to the mountain time zone?
[kaos keos]# timedatectl-restorer -h
usage: timedatectl-restorer [-h] [-r] [-a s] timefile runfile
Restore system time across reboots when the internal clock is dead.
positional arguments:
timefile The file in which to save the clock time.
runfile The run file to use to prevent multiple restorations in a
single session.
optional arguments:
-h, --help show this help message and exit
-r, --restore Restore time from file. If not set, the current time will be
saved instead. If the run file exists or the time file does
not exist then no restoration will be performed.
-a s, --add s The number of seconds to add to the saved time. Default: 10
s.
[kaos keos]# timedatectl-restorer -r
usage: timedatectl-restorer [-h] [-r] [-a s] timefile runfile
timedatectl-restorer: error: the following arguments are required: timefile, runfile
[kaos keos]# timedatectl-restorer -a
usage: timedatectl-restorer [-h] [-r] [-a s] timefile runfile
timedatectl-restorer: error: argument -a/--add: expected one argument
[kaos keos]# timedatectl-restorer -s
usage: timedatectl-restorer [-h] [-r] [-a s] timefile runfile
timedatectl-restorer: error: the following arguments are required: timefile, runfile
[kaos keos]#
[kaos keos]# hwclock
2017-12-27 06:12:17.139733-0500
[kaos keos]# date
mié dic 27 11:12:28 EST 2017
[kaos keos]#
Just symlink your timezone info file to /etc/localtime. It's what tzselect and that abomination from systemd do anyway.
Debian needs to be setup to store time in UTC.
He's in south-eastern Europe.
but Linuxmint is in UTC, the Bios time is in UTC and it is eastern time.
And for some reason still saying timedate is not ...
[kaos keos]# timedatectl status
bash: timedatectl: no se encontró la orden
[kaos keos]#
GNU nano 2.9.1 /etc/localtime
TZif2^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^E^@^@^@^E^@^@^@^@^@^@^@�^@^@^@^E^@^@^$
@p��9`ˈ�p�#�p�`���u���@���U��� ���5���^@���^U���������p��e��މpݩ�`
xp^@^@^@^@eG/`^@^@^@^@e�Zp^@^@^@^@g'^Q`^@^@^@^@g�<p^@^@^@^@i^F�`^@^@^@^@i�^^p^@$
EST5EDT,M3.2.0,M11.1.0
That is what he has linked. \_o_/
GMT stands for Greenwich (village) Meridian Tima, so mountain time (Cheyenne Wyoming) is -2:00
I hope I've cleared the confusion
[kaos keos]# tzselect
Please identify a location so that time zone rules can be set correctly.
Please select a continent, ocean, "coord", or "TZ".
1) Africa
2) Americas
3) Antarctica
4) Asia
5) Atlantic Ocean
6) Australia
7) Europe
8) Indian Ocean
9) Pacific Ocean
10) coord - I want to use geographical coordinates.
11) TZ - I want to specify the time zone using the Posix TZ format.
#? 2
Please select a country whose clocks agree with yours.
1) Anguilla 19) Dominican Republic 37) Peru
2) Antigua & Barbuda 20) Ecuador 38) Puerto Rico
3) Argentina 21) El Salvador 39) St Barthelemy
4) Aruba 22) French Guiana 40) St Kitts & Nevis
5) Bahamas 23) Greenland 41) St Lucia
6) Barbados 24) Grenada 42) St Maarten (Dutch)
7) Belize 25) Guadeloupe 43) St Martin (French)
8) Bolivia 26) Guatemala 44) St Pierre & Miquelon
9) Brazil 27) Guyana 45) St Vincent
10) Canada 28) Haiti 46) Suriname
11) Caribbean NL 29) Honduras 47) Trinidad & Tobago
12) Cayman Islands 30) Jamaica 48) Turks & Caicos Is
13) Colombia 31) Martinique 49) United States
14) Costa Rica 32) Mexico 50) Uruguay
15) Cuba 33) Montserrat 51) Venezuela
16) Curaçao 34) Nicaragua 52) Virgin Islands (UK)
17) Chile 35) Panama 53) Virgin Islands (US)
18) Dominica 36) Paraguay
#? 49
Please select one of the following time zone regions.
1) Eastern (most areas) 16) Central - ND (Morton rural)
2) Eastern - MI (most areas) 17) Central - ND (Mercer)
3) Eastern - KY (Louisville area) 18) Mountain (most areas)
4) Eastern - KY (Wayne) 19) Mountain - ID (south); OR (east)
5) Eastern - IN (most areas) 20) MST - Arizona (except Navajo)
6) Eastern - IN (Da, Du, K, Mn) 21) Pacific
7) Eastern - IN (Pulaski) 22) Alaska (most areas)
8) Eastern - IN (Crawford) 23) Alaska - Juneau area
9) Eastern - IN (Pike) 24) Alaska - Sitka area
10) Eastern - IN (Switzerland) 25) Alaska - Annette Island
11) Central (most areas) 26) Alaska - Yakutat
12) Central - IN (Perry) 27) Alaska (west)
13) Central - IN (Starke) 28) Aleutian Islands
14) Central - MI (Wisconsin border) 29) Hawaii
15) Central - ND (Oliver)
#? 1
The following information has been given:
United States
Eastern (most areas)
Therefore TZ='America/New_York' will be used.
Selected time is now: jue dic 28 09:26:25 EST 2017.
Universal Time is now: jue dic 28 14:26:25 UTC 2017.
Is the above information OK?
1) Yes
2) No
#? 1
You can make this change permanent for yourself by appending the line
TZ='America/New_York'; export TZ
to the file '.profile' in your home directory; then log out and log in again.
Here is that TZ value again, this time on standard output so that you
can use the /usr/bin/tzselect command in shell scripts:
America/New_York
[kaos keos]#
This is what i did and when i'm going back to Debian and comeback ... wrong time again in arch.
i don't know how to do this ...
@keos You say your bios is in UTC and in Eastern (Europe) time?
I believe UTC is UTC (old GMT) and does not change. If you can adjust the time there to your "real" time it may help.
One is picking up bios time as real and one as UTC.
I've had the same problem and just gave up fiddling, after all Artix is my #1 work system. The rest are for studying and toying around. The only exception is Obarun which I have made so much to resemble Artix that I forget where I am at sometimes.
You can also install timeset or timeset-Gui from AUR makes it simple. Make sure you have the Ntp deamon enabled
The following information has been given:
United States
Eastern (most areas)
Therefore TZ='America/New_York' will be used.
Selected time is now: jue dic 28 09:26:25 EST 2017.
Universal Time is now: jue dic 28 14:26:25 UTC 2017.
Is the above information OK?
1) Yes
2) No
#? 1
You can make this change permanent for yourself by appending the line
TZ='America/New_York'; export TZ
to the file '.profile' in your home directory; then log out and log in again.
Here is that TZ value again, this time on standard output so that you
can use the /usr/bin/tzselect command in shell scripts:
America/New_York
[kaos keos]#
And when i change to Mint and comeback i found the time is wrong again. ah! and timeset-Gui from AUR is already installed and the Ntp deamon enabled but when i change to Mint and comeback again ...
And ... after "update" the time with timeset-gui, even when it is saying is ok is not ok:
[kaos keos]# date
vie dic 29 10:22:21 EST 2017
[kaos keos]# hwclock
2017-12-29 05:22:30.045500-0500
[kaos keos]#
This is to much for me i'm considering uninstall the system ... Thanks for your help.
More information:
[kaos keos]# hwclock --show
2017-12-29 05:34:00.280023-0500
[kaos keos]# hwclock --systohc
[kaos keos]# hwclock --show
2017-12-29 10:34:51.936293-0500
[kaos keos]#
And when comeback from Mint everything is wrong.
I'm not an expert but i think there is something wrong here with systemd ...
I wanting to try to get the new kernel to see what happen but after fix to the right time again ...
[[kaos keos]# hwclock
2017-12-29 07:51:32.927678-0500
[kaos keos]# hwclock --systohc
[kaos keos]# hwclock --show
2017-12-29 12:52:49.874007-0500/code]
nano /etc/pacman.conf and add the indication:
[code][repo-ck]
Server = http://repo-ck.com/$arch
and at root terminal:
pacman-key -r 5EE46C4C && pacman-key --lsign-key 5EE46C4C
but ...
[kaos keos]# LANG=C pacman-key -r 5EE46C4C && pacman-key --lsign-key 5EE46C4C
gpg: keyserver receive failed: Connection timed out
==> ERROR: Remote key not fetched correctly from keyserver.
[kaos keos]#
Did you try the command that nous gave you on Mint?
Probably mint has some systemd tz service going screwing everything up
Yes i did it ... i'm totally lost, now this is a mess, from LinuxMint Rosa:
[codekaos kaos # date
vie dic 29 19:19:19 UTC 2017
kaos kaos # hwclock
vie 29 dic 2017 14:19:26 UTC -0.221063 segundos
kaos kaos #]
i checked at the Bios too and time is ok .
And i tried this too ...
kaos kaos # hwclock --localtime --show
vie 29 dic 2017 14:47:47 UTC -0.297734 segundos
kaos kaos #
And this information (today) is for Archlabs:
root@kaos /home/keos # timedatectl status
Local time: Sat 2017-12-30 10:25:11 EST
Universal time: Sat 2017-12-30 15:25:11 UTC
RTC time: Sat 2017-12-30 15:25:11
Time zone: America/New_York (EST, -0500)
System clock synchronized: yes
systemd-timesyncd.service active: yes
RTC in local TZ: no
root@kaos /home/keos #
In mint:
sudo dpkg-reconfigure tzdata
Scroll to the bottom of the list of continents. Select Etc or None of the above. In the second list, select UTC time. This should fix mint.
Here is more info:
https://askubuntu.com/questions/138423/how-do-i-change-my-timezone-to-utc-gmt
Two many variables and your making yourself crazy. Set in the Bios the hardware clock to UTC time. Set in each OS the timezone accoding to the database. If mint is fucking everything up by reseting your hardware clock to real time without telling you then don't use it.
The Bios time is set at newyork/america, which is the right time for me, i don't see any other option in the Bios for UTC, it just say "time".
From Mint after apply again the command nous gave before ...
[codekaos@kaos ~ $ LANG=C hwclock --debug
hwclock from util-linux 2.20.1
hwclock: Open of /dev/rtc failed: Permission denied
No usable clock interface found.
hwclock: Cannot access the Hardware Clock via any known method.
kaos@kaos ~ $
]
and again after restart and turn off pc
kaos kaos # hwclock
mar 02 ene 2018 14:55:29 UTC -1.038452 segundos
kaos kaos # date
mar ene 2 14:55:41 UTC 2018
kaos kaos #
sorry i forgot this too:
kaos kaos # dpkg-reconfigure tzdata
Current default time zone: 'America/New_York'
Local time is now: Tue Jan 2 10:00:59 EST 2018.
Universal Time is now: Tue Jan 2 15:00:59 UTC 2018.
kaos kaos #
Nothing work
@keos One more time: have you symlinked your time zone to
/etc/localtime?
# ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
If yes and
date still shows wrong time, fix debian. Don't use
hwclock for reporting;
date and
date -u are much more readable.
From Artix:
[kaos keos]# date -u
mié ene 3 13:51:03 UTC 2018
[kaos keos]# hwclock
2018-01-03 08:51:19.225841-0500
[kaos keos]# LANG=C ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
ln: failed to create symbolic link '/etc/localtime': File exists
[kaos keos]#
From Debian:
kaos kaos # date -u
mié ene 3 14:02:53 UTC 2018
kaos kaos # hwclock
mié 03 ene 2018 09:03:15 EST -0.280624 segundos
kaos kaos # LANG=C ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
ln: failed to create symbolic link '/etc/localtime': File exists
kaos kaos #
i want to say -just in case - one more time ... that time in debian is o'k, (when i fix it) while still in debian, but once i change to Arch ... the same in arch, when i fix time, both arch works fine but when change to debian ...
Thanks.
sorry, from LinuxMint:
kaos kaos # date -u
mié ene 3 18:35:45 UTC 2018
kaos kaos # date
mié ene 3 13:35:51 EST 2018
kaos kaos #
kaos kaos # LANG=C ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
ln: failed to create symbolic link '/etc/localtime': File exists
kaos kaos #
and of course the file already exist:
GNU nano 2.2.6 Archivo: /etc/localtime
TZif2^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^D^@^@^@^D^@^@^@^@^@^@^@�^@^@^@^D^@^@^$
@p��9`ˈ�p҈#�p҈`��ӈu䈱�Ԉ@݈�ՈUƈ� �� 5��؈^@��و^U��و���ڈ��pۈ�e�܈މpݩ�` kp߉d`��MpቱiF`≱~$
��`^K��p^L٢
�gp^N���^O���^P�f�^Q�e�^RyH�^SiG�^TY*�^UI)�^V9^L�^W)^K�^X")`^Y^H��^Z^B^K`^Z�
p^[��`^\��p^]��`^^��p^_��` v^@�!��`"U��#j��$5��%J��&^U��'*s�'��p)
U�)ޥp* 7 +��p,ӥT`-�ip.�6`/~Kp0�^X`1gg�2r�`3GI�4Rܥ`5'+�62�`7^G
�8^[��8���9���:���;۞�<�p=���>�Оp?�b�@o�pA�^?`BO�pCda`D/vpEDC`E���G-_�Gӊ�I
A�I�l�J�#�K��pL�@`M|kpN�"`O\MpP�^D`Q</pRu�`S^\^QpTU�`T��pV5�`V�^O�X^^��X���Y���$
xpeG/`e�Zpg'^Q`g�<pi^F�`i�^^pj��`k�:�l���mv^\�n���oU��p���q5��ro��s^U��tOy�t��p$
@p������9`����ˈ�p����҈#�p����҈`������ӈu䈱�����Ԉ@݈�����ՈUƈ����� ������ 5������؈^@�$
��`^@^@^@^@^K��p^@^@^@^@^L٢ ^@^@^@^@
�gp^@^@^@^@^N���^@^@^@^@^O���^@^@^@^@^P�f�^@^@^@^@^Q�e�^@^@^@^@^RyH�^@^@^@^@^Si$
p^@^@^@^@^[��`^@^@^@^@^\��p^@^@^@^@^]��`^@^@^@^@^^��p^@^@^@^@^_��`^@^@^@^@ v^@�$
U�^@^@^@^@)ޥp^@^@^@^@* 7ॱ^@^@^@^@+��p^@^@^@^@,ӥT`^@^@^@^@-�ip^@^@^@^@.�6`^@^@^@$
�^@^@^@^@8^[��^@^@^@^@8���^@^@^@^@9���^@^@^@^@:���^@^@^@^@;۞�^@^@^@^@<�p^@^@^@^A�^@^@^@^@I�l�^@^@^@^@J�#�^@^@^@^@K��p^@^@^@^@L�@`^@^@^@^@M|kp^@^@^@^@N�"`^@^@^$
xp^@^@^@^@eG/`^@^@^@^@e�Zp^@^@^@^@g'^Q`^@^@^@^@g�<p^@^@^@^@i^F�`^@^@^@^@i�^^p^@$
EST5EDT,M3.2.0,M11.1.0
[ 18 líneas leídas (Convertidas desde formato Mac) ]
^G Ver ayuda ^O Guardar ^R Leer fich.^Y Pág. ant. ^K Cortar Tex^C Posición
^X Salir ^J Justificar^W Buscar ^V Pág. sig. ^U PegarTxt ^T Ortografía
what I'm I doing wrong?
# ln -sf /usr/share/zoneinfo/America/New_York /etc/localtime
from Mint after apply this new command modification and reboot...
kaos kaos # date
jue ene 4 13:23:44 EST 2018
kaos kaos # date -u
jue ene 4 18:23:51 UTC 2018
kaos kaos # hwclock
jue 04 ene 2018 08:24:08 EST -0.563136 segundos
kaos kaos #
Looks like solved.
No is not solved, as before, when i change to Arch the time is going wrong ...
This looks F@@@ed, it is adding 5 to UTC instead of subtracting 5 from UTC (London time).
Maybe the problem is in BIOS time. Why don't you switch BIOS time to UTC if it is on real time EST, or vice versa.
You seem to be on Pakistan time or is it W. Kazakhstan?
This is crazy, I've had a similar problem before but somehow it worked itself out after a couple of rounds of fixing.
Maybe you should lie to systemd on your whereabouts and make it think you are 5hrs ahead of UTC
You may have a Borat virus. :)
Hi,
The Bios here do not have any other option that: «system time», which is set at newyork time, EAST.
The last thing that have to think about it is a virus since everything is fine WHILE i do not change from debian to arch or from arch systems to debian ...
systemd? ... LinuxMint Rosa do not have systemd neither Artix or Archlabs, as far as i know.
The only thing that i never said here because i think it is irrelevant is that Windows was installed before in this pc (not anymore) and i had a similar problem between Linux and windows till i apply some commands in Mint that someone else recomeded (i forgot those orders) and the problem was fixed.
The last solution if nobody here can help will be to uninstall Linuxmint ... -- in the near future they are not going to support anymore Rosa without systemd.
Thanks!
So what you had done then was to make mint cope with MS craziness subtracting 5 hrs from machine to produce a UTC figure and then use that UTC to figure EST. With MS out of the way the machine time is pushed to UTC and stays that way only Mint is reading it and adding 5hrs to it and throwing it all off.
Maybe there is a package that feeds from an internet time server and overrides all this craziness.
[about Mint]
I thought all mint was based on debian and some ubuntu. Before you kill it, I don't know much about Rosa, it may be worth your while to switch the debian repositories to devuan, maybe ascii (https://sourceforge.net/projects/refracta/files/testing/) which is parallel to stretch (current Debian stable). Maybe I am thinking of LMDE, but still ubuntu is based on debian packaging plus some custom ubu stuff. Maybe Rosa was based on wheezy and its support is ending next year and this is why you have Mint without systemd. Which means your init system should be sysvinit/sysv-rc. Devuan uses the same and OpenRC is as simple as installing it and uninstalling sysv-rc. The whole thing boots up in a fraction of time than debian, almost as good as Artix, less than half the idling RAM on the desktop.
See if that holds together for you. If mint repositories are separate and in addition to debian/ubu then it may work. If mint incorporates those other repositories in its own then it will be impossible to clear out the way debian pkg works. Arch prioritizes repositories of preference, debian doesn't.
I never touched ubuntu or mint. I hate funky crowded desktops.
What package causes this problem in Mint? Try to use whatever you use for package management to search for installed packages relating to 'time' 'clock' or 'ntp'. If you don't get stopped by dependency issues, you might be able to identify which one causes the problem by removing them one by one and testing on reboots to see if the problem goes away. Then you could use an alternative or at least have a better idea where to look, the package might have man pages with suggestions too.
This is perhaps slightly risky in terms of breaking Mint so proceed with caution, but less drastic than deleting it.
In the simplest case it might just be set at early boot by sysvinit and could depend on what locale is set, don't uninstall sysvinit. The boot scripts might show what is happening a little.
" i apply some commands in Mint that someone else recomeded (i forgot those orders) and the problem was fixed."
You can 'purge' packages to remove existing config files, then reinstall them. Possibly you can reconfigure them to standard too, I can't remember offhand.
Those commands might be in here, depending how long this file was set up to be in the terminal settings in Mint:
$ cd ~/
$ nano .bash_history
Also if you installed any additional packages, there should be some sort of logs for apt somewhere, possibly /var/log/apt?
Sometimes the CMOS battery fails and the BIOS clock is unset on every boot, then it might get reset to the last known time cached on the HDD which can give odd effects, and some packages synchronize the time from an online source.
I am amazed that the op has the fortitude to continue trying to resolve this issue....kudos. Personally I would bite the bullet and choose which distro I want to run, and go with it.
Dual booting is problematic at the best of times....case in point.
I hope you can resolve this, one way or the other.
Best regards.
From here:
https://help.ubuntu.com/community/UbuntuTime#Make_Linux_use_.27Local.27_time
To tell your Ubuntu system that the hardware clock is set to 'local' time:
Pre-Ubuntu 15.04 systems (e.g. Ubuntu 14.04 LTS):
edit /etc/default/rcS
add or change the following section
# Set UTC=yes if your hardware clock is set to UTC (GMT)
UTC=no
Ubuntu 15.04 systems and above (e.g. Ubuntu 16.04 LTS):
open a terminal and execute the following command
timedatectl set-local-rtc 1
If the time zone is wrong, further up on that same page it says:
Using the command line, you can use sudo dpkg-reconfigure tzdata.
Open a terminal window by going to Applications>Accessories>Terminal
sudo dpkg-reconfigure tzdata
Follow the directions in the terminal.
The timezone info is saved in /etc/timezone - which can be edited or used below
I am guessing you have set Mint to use local time for the hardware / BIOS / CMOS clock, to work with Windows which also uses localtime by default. Mint probably has some time syncing thing installed like ntp or ntpd. (This might have it's own conf file too, if it still isn't fixed above, and there's also some Gnome desktop time thing that may or may not have an effect.) So it starts up, sets the OS clock initially from whatever the BIOS clock is set to. Then it checks to see if the OS clock is correct, also on local time, and resets the BIOS clock as well if it isn't where it thinks it should be.
Artix meanwhile uses UTC / GMT (unless that has been set to something different) because Linux uses this by default, and sets local time for the OS as an offset to what it wrongly believes is UTC (but is actually local time) on the BIOS clock.
Of my suggestions in the earlier post, I think now looking in .bash_history to find out what you did to configure the time on Mint is the most useful approach. If you have had that install for years it may not be in there, or you could have changed it using desktop settings menus. I think you must have done something clever to make it use local time for Windows though. ;D
I have on average between 6-8 distros running one a machine, sharing some partitions, home var tmp, half are devuan/ian based and half arch based. I have seen the problem before a few times, but can't remember each time what I did to adjust and it worked itself out.
So something that was done in Mint to correct the MS problem (probably the source of the problem) is still there causing the problem now. Instead of really fixing it then it somehow it was patched to cope with MS stupidity. It needs to get undone. Look above and you will see that in some places 5hrs are added to UTC and in some subtracted.
Set in the Bios the hardware clock to UTC time. Set in each OS the timezone accoding to the database. If mint is fucking everything up by reseting your hardware clock to real time without telling you then don't use it.
But the problem is that the Bios do not have any option to set time in UTC, as i said before, it just gives this option: 'system time'.
Yes, i think that it is better to uninstall Mint, but first i have to see how these arches are going to work in this hardware because is not my first time with arch, i was using Antergos and Manjaro and there were problems all the time. Any way thank you very much to all of you for the help!
Well, don't uninstall it, just don't boot it anymore :)
Ok, you can't set UTC on bios, but you must be able to set the time, right? So the time should be -5 EST. If it is 13:00 there now set it for 18:00.
Then see what Artix does.
If all is OK, then look at what Minty is doing.
Mint is evidently doing a hwclock set of whatever it thinks local time is...
No way ... when comeback to arch the time was wrong again. To me it's over.
Thanks!
We gave it a hell of a try, collectively.
It seems as tz is a very Keotic business in linux.
With microsoft you just let it allow the clock with ms server or nist, and who knows what other rights you are passing over to those servers, but your clock is ticking.
Let's say some server intentinally makes your clock 0.123456789 seconds ahead of the server. In a tor network you would stand out like a shore thumb because of your time deviation. Need I say more?
One last thing to check is your "services" on systemd list. Which ones are active and if one of them is a clock adjusting "service". Turn that bugger off. I haven't been around systemd so long that I don't remember much of it, but there was some gui panel in the settings menu that you can activate and deactivate services. Some were crucial to the system some were just the "hydra's" heads crawling all over your system.
why not just let ntpd set the time?
You mean in Artix? So it would automatically correct the time even if it was wrong - that would be a good idea I guess, and save finding what is wrong in Mint.
Mint Rosa is based on Ubuntu 14.04 which used Upstart not systemd. Anyone know anything about Upstart? :)
The clock is probably getting set in early boot before auditd starts, although it would still tell you that is is happening in early boot and not at any other time, but if there was something else setting it later you could find out exactly what it was with audit if that is available and working in Mint:
Install "audit" package
Put these files (should be included in the audit package somewhere) in config dir /etc/audit/rules.d
10-base-config.rules 30-stig.rules 99-finalize.rules
(you might want to uncomment or comment some stuff in these, see the explanations in the files, there are man pages for auditd etc.)
Run
# augenrules
Enable the auditd service (if that isn't already done)
Reboot
Print out logged time-change stuff
# ausearch --start this-week --key time-change
It will probably give some info about time change rules being loaded regardless, but if it finds anything setting the time it will say what and when.
mrbrklyn's idea might be simpler though :)
set it with ntp with both
I have been having similar problems now in one system and found this on the way to a solution
http://www.pool.ntp.org/en/use.html