Confusing whonix check error

[ray242012]

***************************************************************
This email was sent via http://www.AnonymousSpeech.com,
the worlds leading <a href=http://www.anonymousspeech.com>anonymous email</a> provider.
Report Abuse: http://www.anonymousspeech.com/contact.aspx
Stop receiving emails from AnonymousSpeech.com: http://www.anonymousspeech.com/bannedemail.aspx?email=qubes...@googlegroups.com
***************************************************************



Hello,

I am new to Qubes, and so far it's been... an experience.

When I perform a whonix check on any of the whonix VMs, I get an error window that is quite confusing, because it doesn't actually state what it is complaining about. The message says:
[code]
ERROR: systemd Clock Check Result:
Unexpected results by timedatectl
[/code]
It then goes on to list the Local time, which is correct, and Universal time, which is again correct, and both Local and Universal are the same. In other words, there is no error, because both times are actually correct, and the system is set to UTC.

So what is the error? Stating something is unexpected without actually listing what that something is does not facilitate troubleshooting in any way.

BTW, I'd attach a screenshot, but the error window pops up in the Dom0 desktop and there doesn't seem to be any way to share it with the anon-whonix VM where I am composing this email. I tried qvm-copy in a Dom0 console but got a command not found message. I searched the Qubes-OS site for instructions on how to share a screenshot between Dom0 (or any file for that matter), but to no avail. So if it is possible it is not very obvious as to how.

Thanks for any information regarding this apparent non-error, and/or how to supply the screenshot.

R

[Patrick Schleizer]

ray242012:
> Unexpected results by timedatectl

- Please enter error messages into search engines

"Unexpected results by timedatectl"

Then often find already existing discussions.

https://github.com/QubesOS/qubes-issues/issues/3469

- Upgrade to Whonix 14 - fixed there.

Cheers,
Patrick