On Sunday, January 20, 2019 at 7:02:34 PM UTC+1, john s. wrote: > On 1/20/19 12:06 AM, Andrew David Wong wrote: > > On 19/01/2019 5.08 PM, John S.Recdep wrote: > >> On 1/14/19 9:55 PM, John S.Recdep wrote: > >>> On 1/14/19 10:10 AM, John S.Recdep wrote: > >>>> Hello, > >>>> > >>>> I believe my Bios time is UTC > >>>> > >>>> qubes-prefs shows my clockvm as sys-net > >>>> > >>>> I have been trying to use sudo date --set <"localtime TZ"> to > >>>> get my dom0 correct. Which it does but within 30-60 it is > >>>> changing to another TZ I don't recognize > >>>> > >>>> I have also tried qvm-sync-clock , and tried a qubes group > >>>> search as I remember fighting this out many times with whonix > >>>> issues , however > >>>> > >>>> I am at a loss what to do further to problem-solve fix this , > >>>> appreciate your help > >>>> > >>>> > >>>> maybe I can switch the template for sys-net back to fedora-28 > >>>> instead of -29 ..... ? > >>>> > >>> > >>> 1-14-19 > >>> > >>> changing the clockvm to fed-28 and rerunning qvm-sync-clock did > >>> nothing BUT* changing sys-net to debian-9 and qvm-sync-clock > >>> fixed it sigh > >>> > >>> case anyone else gets this issue again ; prolly will fix > >>> whonixcheck complaints if any as well > >>> > >>> 'solved' > >>> > > > >> Must be related to this > >> https://github.com/QubesOS/qubes-issues/issues/3983 > > > >> for myself it's not the minimal fedora-29 its the regular one ; > >> and it appears if fedora-29 is having time issues that that may > >> be why my thunderbird appvm based on it, is also timestamping the > >> messages wrong ? > > > > > > Try the workaround mentioned in the comments on that issue, if you > > haven't already. It's worked for me so far. > > > > > > > well if you mean: > > in the Fedora-29 template doing > > sudo chmod 700 /var/lib/private > > > [user@fedora-29 ~]$ sudo ls -l /var/lib/private/ > total 4 this looks inside the private dir, but what you want is to look at the dir itself, here's two ways: [user@sys-firewall ~]$ stat /var/lib/private/ File: /var/lib/private/ Size: 4096 Blocks: 8 IO Block: 4096 directory Device: ca03h/51715d Inode: 397353 Links: 3 Access: (0700/drwx------) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2018-05-24 01:13:40.232000000 +0200 Modify: 2018-05-24 01:13:40.232000000 +0200 Change: 2018-12-20 03:21:32.447000000 +0100 Birth: -
[user@sys-firewall ~]$ ls -la /var/lib/|grep private drwx------ 3 root root 4096 May 24 2018 private > drwxr-xr-x 2 root root 4096 Dec 9 15:37 systemd > [user@fedora-29 ~]$ sudo chmod 700 /var/lib/private/ now that you've already run this, it should be fixed already :) > [user@fedora-29 ~]$ sudo ls -l /var/lib/private/ > total 4 > drwxr-xr-x 2 root root 4096 Dec 9 15:37 systemd > > > doesn't seem to change any permissions on the systemd directory so > ..... doesn't seem like that is going to fix anything ? maybe I'm > missing something basic? -- 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/44e5d8af-9bf4-42c0-adea-cd90869af086%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
