Re: [qubes-users] Wrong timezone in VMs: where the value for qubesdb-read /qubes-timezone comes from? (Take two)

2018-05-01 Thread Pablo Di Noto
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

Re: [qubes-users] Wrong timezone in VMs: where the value for qubesdb-read /qubes-timezone comes from? (Take two)

2018-04-30 Thread Ivan Mitev
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

[qubes-users] Wrong timezone in VMs: where the value for qubesdb-read /qubes-timezone comes from? (Take two)

2018-04-30 Thread Pablo Di Noto
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 |

Re: [qubes-users] Wrong timezone in VMs: where the value for qubesdb-read /qubes-timezone comes from?

2016-08-31 Thread Pablo Di Noto
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, > >>> > >>>

Re: [qubes-users] Wrong timezone in VMs: where the value for qubesdb-read /qubes-timezone comes from?

2016-08-31 Thread Andrew David Wong
-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 >