Hello, i am running openSUSE 11.1 with KDE 4.2.1. I just turn my laptop on and noted that there was no jump in time shown by the clock as a result of day light saving time starting to day.
Any ideas as to why?
Thanks!
Is your clock set to UTC or localtime?
cat /etc/sysconfig/clock
DST should work for UTC.
Which clock, the BIOS clock or the system time?
Do you dual boot or do you only have Linux? If you dual boot you should be using local time for the BIOS clock. If you only have Linux you should be using UTC.
If you dual boot with Windows, then you need to boot once in Windows to correct the BIOS clock, which is set to local time, and then Linux will follow. Or fix it in the BIOS setup. The local time setting in Linux is based on the assumption that the BIOS clock is set to local time, whether that happens in normal or DST.
If you have only Linux, and your timezone is set correctly, then your BIOS clock will not change, but the time display in Linux will show DST. In the rare situation where your timezone has changed the DST rules recently, you may need to update to the latest version of the tzdata package.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Not that it helps much but my wife’s 11.1 system and my own SLED 11 system
both changed times properly. As ken yap said, though, our timezone’s DST
stuff hasn’t changed recently and if you life somewhere that it has then
that could easily be part of the issue.
Good luck.
ken yap wrote:
> Which clock, the BIOS clock or the system time?
>
> Do you dual boot or do you only have Linux? If you dual boot you should
> be using local time for the BIOS clock. If you only have Linux you
> should be using UTC.
>
> If you dual boot with Windows, then you need to boot once in Windows to
> correct the BIOS clock, which is set to local time, and then Linux will
> follow. Or fix it in the BIOS setup. The local time setting in Linux is
> based on the assumption that the BIOS clock is set to local time,
> whether that happens in normal or DST.
>
> If you have only Linux, and your timezone is set correctly, then your
> BIOS clock will not change, but the time display in Linux will show DST.
> In the rare situation where your timezone has changed the DST rules
> recently, you may need to update to the latest version of the tzdata
> package.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIcBAEBAgAGBQJJtGQaAAoJEF+XTK08PnB5Gv0P/2gxP3M8fIEFW37duVM6If37
SZerZlQaDKoCWDJhYmcpUq+jU+A3Xbho7ZS7BxSMM3UndIUqfGdLuGRE//p/G8sJ
pv9/iTkG5zoYVnX32G6rbdpbPlExyofgea99IGUlwHNdJIJRHrT0jjDjVxglQWiT
UrikhuWyst28JWxm6mYRI+YpvE38InJnGZef7Ab7w+SX/74qw0/iaObWh6Nge1xR
GRvlqKrboIlU2gduQ5Kx6zjw+shvTqxkkRuy3DIUC62w7mwQvjS5v9n64AxAgJWQ
+qKkHQzvdDONR+vStjf8X3WxRiL2aLkZqwbwMJByGlwCK5nfyKPn1SEfdxj9jfNm
zBX6fOHQWOW2m8AX1QUg/LnUUay+jbRGj8UiQvve37GBS85xrcWr/y77kBuObbR5
a9iDEC+1AXUPqhl0gbqlvxsYiyfLwiNjxEs2+YRiygONcydz+ISIDl8ZWT2VbIhf
OGkd/yGSUfk7uC2eee6+oVV54eqRUlqyvltCF8A3sTJMwBihuUJOdCXUEWaXj8Zt
8chI0djp5q1rUxwlDQ1F7mxEhXi8mCuaexujfBG5JxHFVZRdbATsIAaBDrpgTIJS
S0cqGZ/7UPaO1Vsvi9N9wOkvH7j8sQD0QAf8bsu3ZcTDU5bl5PGd6/33Dbv62Lbo
J701IeAOkmlzMih9MTo4
=NVI9
-----END PGP SIGNATURE-----
Thank you all for your suggestions!
i rebooted my laptop into windows and back to openSUSE and everything is fine now. The clock is set correct now.
Thanks.
Huh. I’ve got the same issue. Windows dual boot (it’s been months since I booted windoze), and OpenSuSE 11.1 and KDE 4.2.1. My clock didn’t change either. TZ is set at localtime.
My work laptop running winblows dual boot and Kubuntu 8.10 and KDE 4.2.1 is set to localtime, and it changed clock time at the daylight savinigs time correctly.
Why can’t OpenSuSE get it right? Don’t get me wrong - I love OpenSuse, I’m just confused why the clock being set to localtime causes opensuse issues, when the ubuntu guys and gals have gotten it right?
Well, you haven’t accounted for all the possible combinations. For example if you have Linux running NTP for time sync and powered on across a daylight saving time change, then when you shutdown, the corrected time should be written to the BIOS clock. There are lots of other combinations some of which work and some not so well. Basically localtime for a hardware clock is a broken concept and all Linux can do is try to cope as well as it can.
Hi,
we have now moved on for a couple of years and distributions. The problem still has not been solved (at least not in 12.3). Dit anyone get a change to take a look at the Ubuntu or OpenElec, or maybe Windows 
code to see how it should be implemented?
Hope that one day the nice openSUSE distribution will find a way to display the correct time. . . .
regards,
Stephan
Windows XP is dead.
Windows Vista and later can all handle setting the hardware clock to UTC (with a small registry change).
The sensible thing for linux is to set the hardware clock to UTC.
That is an interesting point with XP no longer supported the time files will get updated and this time thing is as much political as physical thus gets modified in different areas and different times LOL I had not thought of that.
On 2014-10-26 13:26, Stephan1001 wrote:
> Hi,
> we have now moved on for a couple of years and distributions. The
> problem still has not been solved (at least not in 12.3). Dit anyone get
> a change to take a look at the Ubuntu or OpenElec, or maybe Windows 
> code to see how it should be implemented?
> Hope that one day the nice openSUSE distribution will find a way to
> display the correct time. . . .
If you double boot, and have your CMOS clock set to “local”, time will
not be shifted in CMOS with the seasons. This is intentional, so it will
not be “solved”, as it is considered “solved”. >:-)
The handling is left to Windows in that case, if it can, or to you,
manually.
If you have NTP setup, it may happen automatically. I’m unsure.
The recommended setup is to use “UTC” for the CMOS aka BIOS clock, and
tell Windows to do the same. The procedure is documented.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 2014-10-26 20:18, Carlos E. R. wrote:
> On 2014-10-26 13:26, Stephan1001 wrote:
> The recommended setup is to use “UTC” for the CMOS aka BIOS clock, and
> tell Windows to do the same. The procedure is documented.
I just booted my laptop, which has been hibernated for a week or more,
and running Linux the hour was correct. Then I booted Windows 7, and the
time is also absolutely correct. So, no problem! There is no clock
issue.
(In fact, I booted it in order to check this)
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)