Qubes R4.0 rc4 System Time Errors

[0brand]

@mT8RQf

and since I don’t really other than to throw those commands at it, then I probably shouldn’t … does that makes sense?

This issue should not stop you from using Whonix. If this was serious anonymity risk the Whonix devs would inform us.

As far as skipping check_systemd_clock That is up to you. As a rule of thumb, if you don’t know what you’re doing, you probably should not do it.

@mT8RQf

please don’t point me to the search bar , like superuser website did/does, I quickly stopped using that site, as it was so annoying thanks

Its good practice to get into the habit of doing;

https://www.whonix.org/wiki/Support#Brief_Recommendations

https://www.whonix.org/wiki/Forum_Best_Practices#Bumping_old_Threads_is_Okay

Related:

@entr0py

It’s the moderator’s job to keep threads on topic and sufficiently focused. And to lock them when they become unproductive and run in circles. I’ve always erred on the side of free speech but that comes at a cost of time and aggravation. And most importantly, as Patrick said, leads to a buildup of FUD when the community gets exhausted by intentional or misinformed trolling. Speaking for myself, I’ll be more assertive going forward along with:

• adding per-forum stickied posts describing what type of posts are appropriate; and what information needs to be provided to get help. also include links to troubleshooting, faq, how to ask questions, unsupported, free support principle, free speech, etc.

• marking posts with stackexchange-like tags when appropriate (too vague, off-topic, opinion-based, etc) and linking back to stickied posts