on rebooting my taskbar time is for some reason not persisting Again !
I can try explaining but there seem to be too many moving parts to ever get this to stop breaking on random reboots ?


clockvm is sys-net ; sys-net at the moment is debian-10 based, but using fedora-29 didn't seem to help when I changed it, and then did

qvm-sync clock  in  dom0

I went and peaked at the widget setup, which give a mouse-over that say leave blank to use local time for timezone , it HAD had my current TZ , so I emptied it , but no change at all

so I finally ended up using timedatectl   to set the date

however, sys-whonix-14 is still complaining that the time isn't good enough ......


so to me, something fundamentally remains wrong with Qubes 4.0 that I have to do all this ......


there is like a chain of breaks, and I don't like having to sort through something with no protocol and random problems.....


I know it was supposed to have been fixed at one point and I had been using a different template that wasn't broken, maybe I need to go find that manual fix and try it again though my debian-10 was just an upgrade not a new template , but maybe the upgrade broke ntp or something , doesn't explain why fedora-29 would be broken


sigh

--
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/32abd45b-a8bf-843b-4605-5fe88155025e%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Reply via email to