Repeating a bug I found.
The pupClockSet was erratic with the correct time for me.
I was using the GMT- timezone which produced this error.
Switching to America/Los Angeles solved the problem.
Repeating a bug I found.
The pupClockSet was erratic with the correct time for me.
I was using the GMT- timezone which produced this error.
Switching to America/Los Angeles solved the problem.
My time was always wrong. And I found an old solution.
I found the answer from long ago. It still is not a fix yet. (I am Using an Acer).
The solution was that for US timezones
the "GMT-" timezones are in error
and switching to America/Los Angeles solved the problem.
I am an older in the days of 8k 6502 processors. But I agree. I hope once I relearn/gather info on linux I can be a usefull connection.
Amazed at my handle being available.