Again Ubuntu Not keeping Correct date and Time WILL NOT MANUALLY RESET

Asked by Snooper on 2020-02-24

Again Ubuntu Not keeping Correct date and Time WILL NOT MANUALLY RESET:
>System Settings>Date and time -Refuses to correctly Reset to correctly input date and time (especially the seconds), but Insists on retaining the old INCORRECT values. THIS IS AN UBUNTU ISSUE.


Question information

English Edit question
Ubuntu ubuntu-docs Edit question
No assignee Edit question
Last query:
Last reply:

Please close as a duplicate of

You have a question about this already. Why make a new one?

Manfred Hampl (m-hampl) said : #2

We need to see the output of the commands

uname -a
lsb_release -crid
timedatectl status
sudo hwclock --set --date="`LANG=C date`"
timedatectl status
systemctl status vboxadd-service

Why don't you provide that information?

Bernard Stafford (bernard010) said : #3

On question
Do you still have the same configuration of: Windows 10 as Host - Virtual Box & Ubuntu 16.04 as Guest inside Virtual Box.
Please answer @Manfred Hampl - Simple Question

Bernard Stafford (bernard010) said : #4

Set the Host Clock to UTC (24 Hour Time) Then the guest will have the current time.
The Hardware clock must be in 24 hour time for Virtual Box to identify the time correctly.

Can you please close this off as one of the many duplicates or close the other questions as duplicates of this question. You have a lot of questions about the same thing. I don't know why you keep making duplicates but it does nothing but dilute your own support experience.

Colin Watson (cjwatson) said : #6

@Snooper, this is approaching the level of being unacceptable use of Launchpad. If you keep on in this fashion then we'll have to ban your account in order to avoid wasting the time of the people who contribute to this answers section. I'd rather not have to do this; instead, please stop filing repeated questions about the same thing, and instead engage constructively with the people who are trying to help you.

I'd also suggest that if you think you have identified a legitimate bug in Ubuntu, then you'd be much better off filing a bug report against the correct package (which I would think would be virtualbox, not ubuntu-docs or whatever). When you do, please restrain yourself and don't shout at other contributors.

Can you help with this problem?

Provide an answer of your own, or ask Snooper for more information if necessary.

To post a message you must log in.