Every time I boot my laptop it sets the time an hour ahead of what it actually is. I rebooted and checked to see what the computer itself thinks the time is and that has it correct in the BIOS. However, every single piggin’ time I boot up, I have to right click on the clock and set it an hour back. Please don’t suggest NTP, because I don’t have Internet while on site on this laptop (it’s my laptop and I cannot connect to the company network).
I’m running 12.3 with KDE in case that’s relevant. Anyone know why it refuses to remember the time on shutdown, why it refuses to take the computer’s time from hardware and what I can do to fix this please?
It’s set to UK/London which is correct. I set that in the clock settings when right clicking on the clock. One thing that is ticked is hardware clock set to UTC. AFAIK, UTC is a new fangled term for GMT, so I suppose if it thinks the clock is set to GMT, but we’re actually in British summertime which is an hour ahead, maybe that’s why the OS is setting it.
It’s poor that right clicking in that clock icon doesn’t have that check box or it’s poor that both YAST and the clock control it. It should either be both control it, but right clicking on the clock gives all options, or only YAST should control it.
Thanks for the tip on YAST. I bet deselecting that box that fixes it.
On 2013-07-24 12:16, DiBosco wrote:
>
> It’s set to UK/London which is correct. I set that in the clock settings
> when right clicking on the clock. One thing that is ticked is hardware
> clock set to UTC. AFAIK, UTC is a new fangled term for GMT, so I suppose
> if it thinks the clock is set to GMT, but we’re actually in British
> summertime which is an hour ahead, maybe that’s why the OS is setting
> it.
Related.
Please run these commands in a terminal, and paste here:
su -
date --utc
date --rfc-3339=seconds
hwclock --debug
cat /etc/sysconfig/clock | egrep -v "^:space:]]*$|^#"
Now, notice that “system” time is shown by the above commands; whatever
KDE displays can be wrong and unrelated to the above.
So, first, let us make sure that the system clock is correct, then
we’ll think about KDE. My guess is that you also need to configure KDE
time (do not set time using KDE, at least till you really understand
what it does).
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
that you missed that step in install means you then may or may not
get confused–depending on which desktop environment you select, and
how it intends you to set the clock.
> or it’s poor that both YAST -and- the clock control it.
the problem is that openSUSE (and SuSE before it) well tended to the
clock, using YaST–long before KDE was born…so, now along comes KDE
and builds in a way for the user of openSUSE, and Red Hat, and
Debian, and 300 others to set the clock without using pre-existing,
distribution provided ways…
if openSUSE stripped that out of KDE then the user just in from
Mandrivia, KDE, Kbuntu etc etc etc couldn’t figure out how to set the
clock (without reading the provided documentation, of course)…
and, if openSUSE does not strip out KDE’s redundant way to set the
clock then folks come in and say it is ‘poor’ that there are two ways!
> date
Wed Jul 24 09:20:08 CDT 2013
> TZ=GMT date
Wed Jul 24 14:20:17 GMT 2013
> TZ=UK/London date
Wed Jul 24 14:20:27 2013
My computer is giving the same time for GMT and for UK/London. It also gives the same time for UTC (not shown in the above output). Yet you say that there is a one hour difference.
