Re: [qubes-users] Wrong timezone in VMs: where the value for qubesdb-read /qubes-timezone comes from? (Take two)
Hello Ivan, El mar., 1 may. 2018 01:13, Ivan Mitev escribió: > Hi, > > On 05/01/2018 03:18 AM, Pablo Di Noto wrote: > > Hello all, > > > > I asked this question when Qubes R3.2 was out, and solved with help from > Andrew in a somewhat weird way (running local scripts on each AppVM). > > > > Now that we are at R4.0, I am again having this issue: > > > > After install, dom0 gets proper timezone: > > > > |[root@dom0 Desktop]# timedatectl > > | Local time: Mon 2018-04-30 21:12:20 -03 > > | Universal time: Tue 2018-05-01 00:12:20 UTC > > |RTC time: Tue 2018-05-01 00:12:20 > > | Time zone: America/Argentina/Cordoba (-03, -0300) > > | Network time on: no > > |NTP synchronized: no > > | RTC in local TZ: no > > > > but for some reason, all AppVM get the wrong timezone on their > configuration script: > > > > |user@p-vault:~/p-vault$ ls -l /etc/localtime > > |lrwxrwxrwx 1 root root 39 Apr 30 23:32 /etc/localtime -> > ../usr/share/zoneinfo/Argentina/Cordoba > > > > which of course does not exists, so all AppVM end up in GMT. > > > > So my original question is back: Where does that value come from? > /usr/lib/qubes/init/qubes-early-vm-config.sh > Yes, I see it. That is why I was after the source of the "Argentina/Cordoba" as answer to "qubesdb-read /qubes-timezone" on any AppVM. For some reason, despite dom0 has proper "America/Argentina/Cordoba" timezone after a clean install, AppVMs get "Argentina/Cordoba" when they ask dom0. Will check qubesdb code to see if there is some hardcoded regexp that is asuming timezones are only "" or "/" break when it is three item "//" Regards, ///Pablo > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAOJFbN8BQ-_sdO-tcjGDO1v%3D7xV55Q8sBjFWU8YP5LXsipxVeA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Wrong timezone in VMs: where the value for qubesdb-read /qubes-timezone comes from? (Take two)
Hi, On 05/01/2018 03:18 AM, Pablo Di Noto wrote: > Hello all, > > I asked this question when Qubes R3.2 was out, and solved with help from > Andrew in a somewhat weird way (running local scripts on each AppVM). > > Now that we are at R4.0, I am again having this issue: > > After install, dom0 gets proper timezone: > > |[root@dom0 Desktop]# timedatectl > | Local time: Mon 2018-04-30 21:12:20 -03 > | Universal time: Tue 2018-05-01 00:12:20 UTC > |RTC time: Tue 2018-05-01 00:12:20 > | Time zone: America/Argentina/Cordoba (-03, -0300) > | Network time on: no > |NTP synchronized: no > | RTC in local TZ: no > > but for some reason, all AppVM get the wrong timezone on their configuration > script: > > |user@p-vault:~/p-vault$ ls -l /etc/localtime > |lrwxrwxrwx 1 root root 39 Apr 30 23:32 /etc/localtime -> > ../usr/share/zoneinfo/Argentina/Cordoba > > which of course does not exists, so all AppVM end up in GMT. > > So my original question is back: Where does that value come from? /usr/lib/qubes/init/qubes-early-vm-config.sh the script gets the timezone from dom0 with `qubesdb-read /qubes-timezone` and sets it early during a VM's boot. see this post/thread for more details: https://www.mail-archive.com/qubes-users@googlegroups.com/msg21693.html > And the obvious next one: How can I change it to a proper > "America/Argentina/Cordoba"? I tried to set a different timezone in dom0 but qubesdb-read would return the old value in VMs ; I don't know how the db is updated (a reboot would probably do but it seems overkill and I have too much stuff open to test). But if you're rebooted already and you still get the wrong string in VMs, maybe it's a bug in how qubesdb-read reads the timezone (interestingly, that's the first time I see 3 fields like 'X/Y/Z' - I always thought a timezone would be 'X/Y'). > > Thanks! > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/29748e05-37a9-48eb-dfc6-674cd81c83c2%40maa.bz. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Wrong timezone in VMs: where the value for qubesdb-read /qubes-timezone comes from? (Take two)
Hello all, I asked this question when Qubes R3.2 was out, and solved with help from Andrew in a somewhat weird way (running local scripts on each AppVM). Now that we are at R4.0, I am again having this issue: After install, dom0 gets proper timezone: |[root@dom0 Desktop]# timedatectl | Local time: Mon 2018-04-30 21:12:20 -03 | Universal time: Tue 2018-05-01 00:12:20 UTC |RTC time: Tue 2018-05-01 00:12:20 | Time zone: America/Argentina/Cordoba (-03, -0300) | Network time on: no |NTP synchronized: no | RTC in local TZ: no but for some reason, all AppVM get the wrong timezone on their configuration script: |user@p-vault:~/p-vault$ ls -l /etc/localtime |lrwxrwxrwx 1 root root 39 Apr 30 23:32 /etc/localtime -> ../usr/share/zoneinfo/Argentina/Cordoba which of course does not exists, so all AppVM end up in GMT. So my original question is back: Where does that value come from? And the obvious next one: How can I change it to a proper "America/Argentina/Cordoba"? Thanks! -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/698c13f7-532a-4d23-8d08-034e19785b8f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Wrong timezone in VMs: where the value for qubesdb-read /qubes-timezone comes from?
El miércoles, 31 de agosto de 2016, 13:02:06 (UTC), Andrew David Wong escribió: > > On 2016-08-31 05:42, Pablo Di Noto wrote: > > El miércoles, 31 de agosto de 2016, 12:26:42 (UTC), Andrew David Wong > > escribió: > > > >> On 2016-08-31 04:48, Pablo Di Noto wrote: > >>> Hello, > >>> > >>> Somewhere along the update from 3.1 to 3.2rc1 I started to have all my > >>> VMs take UTC as their timezone. > >>> > >>> dom0 has the correct "America/Argentina/Cordoba" timezone, but all VMs > >>> get incorrectly set to "Argentina/Cordoba", which does not exists thus > >>> leaving them at UTC. > >>> > >>> I know may have manually set somehow the wrong timezone (without the > >>> required "America/" prefix) at install or update. Now all my templates > >>> get set to "Argentina/Cordoba", which is the value they get from > >>> "qubesdb-read /qubes-timezone" at every boot by qubes-sysinit.sh > >>> script. > >>> > >>> I cannot figure out where that values comes from and how to fix it. > >>> > >>> Thanks in advance, ///Pablo > >>> > >> > >> It might be worth trying to set the locale in your TemplateVM(s). For > >> example, these commands should work on fedora-23 (and some other > >> distros): > >> > >> To display your currently set locale: > >> > >> $ locale > >> > >> To set a locale: > >> > >> # localectl set-locale > >> > >> For a list of available locales: > >> > >> $ localectl list-locales > >> > > > > Thanks for the suggestion. In fact, something similar is what I use as > > workaround into the browsing VMs. > > > > The drawback is that I have to set the correct timezone for each VM upon > > booting, each time, as the setting will be overriden at next boot by the > > init script. > > > > Regards, ///Pablo > > > > Two options: > > 1. Change the locale in the TemplateVM instead of the AppVM so that the > overriding value is the desired one. There is no difference setting it at the TemplateVM, as it is also overridden by the script there. > 2. Add the command to change to the desired locale to /rw/config/rc.local (in > the AppVM), then make that file executable (chmod +x). Every command in that > file is executed as root each time the AppVM is started. Thanks Andrew! This works, but still makes you reset the timezone on each TemplateVM when traveling. Not a big deal. I will keep trying to find the root cause of this, albeit to understand the mechanics behind the scenes. Regards, ///Pablo -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/57658dc1-7e46-48ca-a988-c9e57c92e280%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Wrong timezone in VMs: where the value for qubesdb-read /qubes-timezone comes from?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-08-31 05:42, Pablo Di Noto wrote: > El miércoles, 31 de agosto de 2016, 12:26:42 (UTC), Andrew David Wong > escribió: > >> On 2016-08-31 04:48, Pablo Di Noto wrote: >>> Hello, >>> >>> Somewhere along the update from 3.1 to 3.2rc1 I started to have all my >>> VMs take UTC as their timezone. >>> >>> dom0 has the correct "America/Argentina/Cordoba" timezone, but all VMs >>> get incorrectly set to "Argentina/Cordoba", which does not exists thus >>> leaving them at UTC. >>> >>> I know may have manually set somehow the wrong timezone (without the >>> required "America/" prefix) at install or update. Now all my templates >>> get set to "Argentina/Cordoba", which is the value they get from >>> "qubesdb-read /qubes-timezone" at every boot by qubes-sysinit.sh >>> script. >>> >>> I cannot figure out where that values comes from and how to fix it. >>> >>> Thanks in advance, ///Pablo >>> >> >> It might be worth trying to set the locale in your TemplateVM(s). For >> example, these commands should work on fedora-23 (and some other >> distros): >> >> To display your currently set locale: >> >> $ locale >> >> To set a locale: >> >> # localectl set-locale >> >> For a list of available locales: >> >> $ localectl list-locales >> > > Thanks for the suggestion. In fact, something similar is what I use as > workaround into the browsing VMs. > > The drawback is that I have to set the correct timezone for each VM upon > booting, each time, as the setting will be overriden at next boot by the > init script. > > Regards, ///Pablo > Two options: 1. Change the locale in the TemplateVM instead of the AppVM so that the overriding value is the desired one. 2. Add the command to change to the desired locale to /rw/config/rc.local (in the AppVM), then make that file executable (chmod +x). Every command in that file is executed as root each time the AppVM is started. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXxtU4AAoJENtN07w5UDAws1cP/ijJ6FvWPhyxYlHpmFCrc+5m U8ZsZnvUz9Al5xzmeQsZPmTkQDEVZpisaoL6QTS40iaCOZMS4Mq9E6eofZj6mPb3 gk+tfvIYfdS0ND0N0cfW7blyt63k/L2FoLjjplzFGDcYQrYKjhARoi9QjcuCFVx3 QoCbJFibXG8WFs9ad22pUatVTrs0hyH2dFPXPXDkcjubxMJ6fAz2liN05bkrSbBN Fe/SfZTbK8RZqomH4wlnmY8dG+ADMpFX2zYdq7VWY0qkrcZ35W8fCezAYc046aGx wo8kHnaFixwh20myYXVPXIXB2E1nTTv12TqI80xcuRiyyONLRQsbgmSiHIAW92e6 Kp6KBjPcb3QGOZHPKFZUzb+PK/GBkvOcRqxCDM5YySS21Kd1LRCcSQR8zHgc8oXn tb6dCUjn7llSdjDLVydVyeckk4lR/Idcq5Vf/91OQyc+mNX/PfrS+5q+aawTA/98 s7J0TkDXuR8S+d5pnCs2vzl50W5pAwvf8KVBv2SSMulmt0xfW9t3KnbLhW4uw69/ xejPoYK2t9CTSQGuM7a4mV98FZqK2Q6cioiTSAanv15tmGB1FN4Y5A/qrn1OaL3Z YBmdYUn10mIY6wiMj4cMW2AEmuwRF8Ui1BxMDhluCD6HRxMSwSGerMBVgk3ZyxRt Kn1y+HL0uN7qH4TR9E2g =rAVS -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/210fc1d5-2976-b3fc-f93a-1567c3bfe6ba%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Wrong timezone in VMs: where the value for qubesdb-read /qubes-timezone comes from?
El miércoles, 31 de agosto de 2016, 12:26:42 (UTC), Andrew David Wong escribió: > On 2016-08-31 04:48, Pablo Di Noto wrote: > > Hello, > > > > Somewhere along the update from 3.1 to 3.2rc1 I started to have all my VMs > > take UTC as their timezone. > > > > dom0 has the correct "America/Argentina/Cordoba" timezone, but all VMs get > > incorrectly set to "Argentina/Cordoba", which does not exists thus leaving > > them at UTC. > > > > I know may have manually set somehow the wrong timezone (without the > > required "America/" prefix) at install or update. Now all my templates get > > set to "Argentina/Cordoba", which is the value they get from "qubesdb-read > > /qubes-timezone" at every boot by qubes-sysinit.sh script. > > > > I cannot figure out where that values comes from and how to fix it. > > > > Thanks in advance, ///Pablo > > > > It might be worth trying to set the locale in your TemplateVM(s). For example, > these commands should work on fedora-23 (and some other distros): > > To display your currently set locale: > > $ locale > > To set a locale: > > # localectl set-locale > > For a list of available locales: > > $ localectl list-locales > Thanks for the suggestion. In fact, something similar is what I use as workaround into the browsing VMs. The drawback is that I have to set the correct timezone for each VM upon booting, each time, as the setting will be overriden at next boot by the init script. Regards, ///Pablo -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4511f00d-5f08-4fba-a3cb-976c8af854f6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Wrong timezone in VMs: where the value for qubesdb-read /qubes-timezone comes from?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-08-31 04:48, Pablo Di Noto wrote: > Hello, > > Somewhere along the update from 3.1 to 3.2rc1 I started to have all my VMs > take UTC as their timezone. > > dom0 has the correct "America/Argentina/Cordoba" timezone, but all VMs get > incorrectly set to "Argentina/Cordoba", which does not exists thus leaving > them at UTC. > > I know may have manually set somehow the wrong timezone (without the > required "America/" prefix) at install or update. Now all my templates get > set to "Argentina/Cordoba", which is the value they get from "qubesdb-read > /qubes-timezone" at every boot by qubes-sysinit.sh script. > > I cannot figure out where that values comes from and how to fix it. > > Thanks in advance, ///Pablo > It might be worth trying to set the locale in your TemplateVM(s). For example, these commands should work on fedora-23 (and some other distros): To display your currently set locale: $ locale To set a locale: # localectl set-locale For a list of available locales: $ localectl list-locales - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXxst9AAoJENtN07w5UDAw+0cP/RTPei1sTPFIryrOIfzn8HKE rgi13ApkCAwD/Am7qfvrv39RHuNm1R5n/WA4qZzjgxGNV/vMaKbjgIQZeS5iqG76 WKIHy/1T66a0bvBs0A6IJ29dWtLzFguDeJTio7c/4pCrMdRFK5aMI0BlTJHssn/3 tsAGg/d4zlvTsCt9MoEeRjpIqp7EV9GTZV6+F1id1F8MEzNtYJ/Fk/LL9wyMF384 YWJxqvm/2HrzaIiMDnPepcD4BAPO6krPjfe8iFzJtfyPrKhS3wtXMqwJZ6Ed+keE 8qgtd9p4MWz4J7I+xXw/FCaB/aIWBUomSbtrKGYicGIC5o/Ghw7uzoopl7+TUvgy 6w1dBHpwYWEDqgmqxPCWKDl6KHyyV8pyM3KZ8ni5PtEcvbQxTAewun1WWvRNm+8u 9LRZYOqATWbJFkwlQ63OjRFgmYtlEZYvoY98pg2ul105FCsnmlFGyIbEJhyZOY/R /AUJgJPU5bKMmYV6/mEolKYQcMsdzt+4WLpX1Q05iPHI/V8H357x0wA5gOxD/A6J 3DgCfl3auVbEWlCl5piWTON9D2gcETyNZQfDKSfflLXrBblIWwYe2WVrbfeRNEd3 LUWp0qmr792lvbezdUWf2Qk3gNZ4IRKBVtEyOjXFEqlHXOueu0WnOTqYQ2D4SBAp LQEsDV4u3WwIliPdsrPT =T+WS -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7ba970ef-9d9c-29a7-9ddd-edd626575302%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Wrong timezone in VMs: where the value for qubesdb-read /qubes-timezone comes from?
Hello, Somewhere along the update from 3.1 to 3.2rc1 I started to have all my VMs take UTC as their timezone. dom0 has the correct "America/Argentina/Cordoba" timezone, but all VMs get incorrectly set to "Argentina/Cordoba", which does not exists thus leaving them at UTC. I know may have manually set somehow the wrong timezone (without the required "America/" prefix) at install or update. Now all my templates get set to "Argentina/Cordoba", which is the value they get from "qubesdb-read /qubes-timezone" at every boot by qubes-sysinit.sh script. I cannot figure out where that values comes from and how to fix it. Thanks in advance, ///Pablo -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ee713b0a-2c91-4829-b733-4bf36014612b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
