is this time issue ever going to be properly fixed?

[Jon deps]

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

[awokd]

Jon deps wrote on 4/4/19 4:30 PM:

>
> 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 ?
>

> 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

Yes, going back to fedora-28 or debian-9 should fix it. It's possible
the issue re-occurred in fedora-29. Try the same manual fix there.

Think Qubes' policy is only the current version of Debian is supported,
so if you choose to upgrade to 10 it's entirely possible you'll break
things. If I remember right, there will be an announcement once 10 is
supported and available for download as a template.

[Jon deps]

appreciate the reply.

ya, iirc, the templates being there sometimes precedes the
announcements, so I went on ahead.

guess my thinking was that once it was fixed it would stay fixed then
afterwards, but guess I can run one template just for sys-net .... if
I must

fwiw, setting it manually with timedatectl and not even rebooting, and
it ( the taskbar clock and what I think whonix wants ) seems to have
reverted to UTC or some random hour actually .......

as long as I know I can fix it, I'll sort it out I guess :/

[Jon deps]

On 4/5/19 6:21 PM, 'awokd' via qubes-users wrote:

PS: is it a bad idea to upgrade (which I've done successfully to
debian-10) if the templates are not available, guess I was thinking
the fact that I was able to upgrade means there were templates there ...

[awokd]

Jon deps wrote on 4/5/19 10:21 AM:

It's not a bad idea per se, just unsupported. That means there's a
higher chance of you running into problems with Qubes related utilities,
and any fixes or workarounds from the Qubes OS team will be low priority
compared to versions they actively support. However, if you are able to
contribute by testing out new versions and possibly developing fixes,
that can save them time!

[unman]

Also, lets not forget that Debian10 is "testing" - it's liable to break,
and doesnt get security updates like stable.
There are issues with some Qubes packages in buster - fixing them hasnt
been a high priority until the buster freeze.