Time not updated when daylight savings switch made

[grkravi]

Binary package hint: tzdata

March 11, 2007, edgy did not update my clock.
I had installed the edgy updates and i do find Adept Manager listing the tzdata_2007b_0ubuntu0.6.10_all.deb as been installed on 03/07/2007.

I am using Dell Inspiron 5160, dual booting with XP.

$ sudo dpkg -s tzdata
Package: tzdata
Status: install ok installed
Priority: required
Section: libs
Installed-Size: 5728
Maintainer: Ubuntu Core Developers <email address hidden>
Architecture: all
Version: 2007b-0ubuntu0.6.10
Replaces: libc0.1, libc0.3, libc6, libc6.1, locales
Description: Time Zone and Daylight Saving Time Data
 This package contains data that represent the history of local time for many
 representative locations around the globe. It is updated periodically to
 reflect changes made by political bodies to time zone boundaries, UTC offsets,
 and daylight-saving rules
Original-Maintainer: GNU Libc Maintainers <email address hidden>

$ sudo zdump -v /etc/localtime | grep 2007
/etc/localtime Sun Mar 11 06:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 EST isdst=0 gmtoff=-18000
/etc/localtime Sun Mar 11 07:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 EDT isdst=1 gmtoff=-14400
/etc/localtime Sun Nov 4 05:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 EDT isdst=1 gmtoff=-14400
/etc/localtime Sun Nov 4 06:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 EST isdst=0 gmtoff=-18000
$

[ofb (cottlestonpie)]

6.10 has not applied DST.

AMD desktop running a generic & updated Ubuntu. Dual boots w98, but w98 has not been booted recently.

Ubuntu Forums has several similar reports, but no pattern has emerged: some machines applied DST, some didn't.

$ sudo dpkg -s tzdata
Password:
Package: tzdata
Status: install ok installed
Priority: required
Section: libs
Installed-Size: 5728
Maintainer: Ubuntu Core Developers <email address hidden>
Architecture: all
Version: 2007b-0ubuntu0.6.10
Replaces: libc0.1, libc0.3, libc6, libc6.1, locales
Description: Time Zone and Daylight Saving Time Data
 This package contains data that represent the history of local time for many
 representative locations around the globe. It is updated periodically to
 reflect changes made by political bodies to time zone boundaries, UTC offsets,
 and daylight-saving rules
Original-Maintainer: GNU Libc Maintainers <email address hidden>

$ sudo zdump -v /etc/localtime | grep 2007
/etc/localtime Sun Mar 11 09:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 PST isdst=0 gmtoff=-28800
/etc/localtime Sun Mar 11 10:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 PDT isdst=1 gmtoff=-25200
/etc/localtime Sun Nov 4 08:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 PDT isdst=1 gmtoff=-25200
/etc/localtime Sun Nov 4 09:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 PST isdst=0 gmtoff=-28800

[WW (wweckesser)]

It is not just Edgy--some dapper systems failed to make the change to DST. See the forum thread: http://ubuntuforums.org/showthread.php?t=381707

Since dapper doesn't have the package tzdata, the problem is not necessarily tied to this package.

[helpdeskdan (helpdeskdan)]

3 computers. I believe one was on. None of them updated - edgy and dapper.

dan@dan-desktop:~$ sudo dpkg -s tzdata
Password:
Package: tzdata
Status: install ok installed
Priority: required
Section: libs
Installed-Size: 5728
Maintainer: Ubuntu Core Developers <email address hidden>
Architecture: all
Version: 2007b-0ubuntu0.6.10
Replaces: libc0.1, libc0.3, libc6, libc6.1, locales

dan@dan-desktop:~$ sudo zdump -v /etc/localtime | grep 2007
/etc/localtime Sun Mar 11 06:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 EST isdst=0 gmtoff=-18000
/etc/localtime Sun Mar 11 07:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 EDT isdst=1 gmtoff=-14400
/etc/localtime Sun Nov 4 05:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 EDT isdst=1 gmtoff=-14400
/etc/localtime Sun Nov 4 06:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 EST isdst=0 gmtoff=-18000

What an embarrassment - even windows worked!

Speaking of which, all of us are dual-booters, even though I haven't booted windows in a few weeks. Coincidence? Can't see how that would effect anything.

[mannheim (kronheim)]

My machine running edgy did not cope correctly with daylight-savings time. But the system thinks that it has switched to daylight-savings.

I am in EST time-zone, and local time is EDT since this Sunday. My system clock is supposed to be set to local time (UTC=no in /etc/defaults/rcS). At 7:13 am local time this morning, I ran "date" and got

Tue Mar 13 06:13:32 EDT 2007

Note that it says "EDT". But the EDT time is actually 07:13, not 06:13 as reported.

I am running ntpd on this machine, and the servers are (from ntp.conf):

server 0.us.pool.ntp.org
server 1.us.pool.ntp.org
server 2.us.pool.ntp.org

[Mary Gardiner (puzzlement)]

My computer (Feisty beta) also did not apply the Australian East Coast EDT -> EST last night. It is currently 2228UTC and 0828EST, but:

$ date
Sun Mar 25 09:28:31 EST 2007

$ sudo zdump -v /etc/localtime | grep 2007
/etc/localtime Sat Mar 24 15:59:59 2007 UTC = Sun Mar 25 02:59:59 2007 EST isdst=1 gmtoff=39600
/etc/localtime Sat Mar 24 16:00:00 2007 UTC = Sun Mar 25 02:00:00 2007 EST isdst=0 gmtoff=36000
/etc/localtime Sat Oct 27 15:59:59 2007 UTC = Sun Oct 28 01:59:59 2007 EST isdst=0 gmtoff=36000
/etc/localtime Sat Oct 27 16:00:00 2007 UTC = Sun Oct 28 03:00:00 2007 EST isdst=1 gmtoff=39600

Relevant info:
 1. the computer has its hardware clock set to local time (dual boot with Windows)
 2. the computer was suspended at 1600UTC when the timezone switch took place

I have a second computer running Edgy as released which has the hardware clock set to UTC and which was on at the time of the timezone switch; it made the switch successfully.

[Mary Gardiner (puzzlement)]

On my system, ntpdate is able to correct the time when run as: "sudo /usr/sbin/ntpdate ntp.ubuntu.com"

Neither of these worked:
$ sudo /usr/sbin/ntpdate-debian
$ sudo /usr/sbin/ntpdate-debian -b

which probably explains why /etc/network/if-up.d/ntpdate didn't reset the time when I resumed from suspend.

[Andrew Bennetts (spiv)]

In case it helps, my laptop running Feisty *did* update correctly, but unlike Mary's my laptop was running overnight. Like Mary's it is a dual-boot with the hardware clock set to local time rather than UTC (although I haven't booted Windows for months).

So it appears the daylight savings transition works ok if the laptop is running while the transition happens, but not if the laptop is suspended, hibernated or powered off?

[Andrew Bennetts (spiv)]

However, later when I did a suspend/resume the time got incorrectly reset forward one hour (i.e. as if daylight savings hadn't ended).

I *think* this is because the current time in the software clock is not getting written to the hardware clock on suspend, so when the system resumes it resets the system (software) clock from the hardware clock, which still has the old time.

If so, I think this can be fixed by adding "hwclock" to the STOP_SERVICES line of /etc/default/acpi-support, e.g.:

    STOP_SERVICES="mysql hwclock "

Possibly it would be good for the system clock to be saved to the hardware clock explicitly whenever there's a DST transition (and the hardware clock is storing local time rather than UTC), so the fact of the transition can't be forgotten by suspend/hibernate/power-off/system-crash/etc.

I'd expect systems that store UTC time in the hardware clock to be immune to this problem. If only WIndows understood this!

[Mary Gardiner (puzzlement)]

The most recent comment by Andrew Bennetts is actually an occurence of bug 36815.

As for everyone else: can you remember if your computer was shutdown, on or suspended/hibernated at the actual moment of the daylight savings transition? If it was suspended or hibernated, then your problem is bug 95900 and this is a duplicate. If it was either fully shutdown, or actually on at the time, then this is yet a third problem separate from bug 36815 and bug 95900.

[grkravi (grkravi)]

My edgy laptop was shutdown. And i manually reset the clock when i found that the time didnt get updated automatically.

[Mary Gardiner (puzzlement)]

It sounds like this is definitely a different bug from bug 36815 and
bug 95900 then.

For what it's worth, to make it stick you can:
 1. manually reset the clock (if you have network access,
    "sudo /usr/sbin/ntpdate ntp.ubuntu.com" is the most reliable way to
    do it, assuming that it at least has the timezone right)
 2. immediately run "sudo hwclock --systohc"

Although it probably sticks on the next shutdown anyway.

[Cruncher (ubuntu-wkresse)]

Today I had the same phenomenon as reported by "mannheim": The timezone changed from "CEST" to "CET", but the time itself did not change. The result was an incorrect time +1h in the future.

The system (7.04) was shutdown during the transition point (no suspend, no hibernate).
I have ntp, ntpdate and tzdata installed, and ntpd is launched at startup, using:
server ntp.ubuntu.com minpoll 12 maxpoll 17

$ zdump -v /etc/localtime | grep 2007
/etc/localtime Sun Mar 25 00:59:59 2007 UTC = Sun Mar 25 01:59:59 2007 CET isdst=0 gmtoff=3600
/etc/localtime Sun Mar 25 01:00:00 2007 UTC = Sun Mar 25 03:00:00 2007 CEST isdst=1 gmtoff=7200
/etc/localtime Sun Oct 28 00:59:59 2007 UTC = Sun Oct 28 02:59:59 2007 CEST isdst=1 gmtoff=7200
/etc/localtime Sun Oct 28 01:00:00 2007 UTC = Sun Oct 28 02:00:00 2007 CET isdst=0 gmtoff=3600
$ dpkg -l|grep ntp
ii ntp 4.2.2.p4+dfsg-1ubuntu3 Network Time Protocol daemon and utility pro
ii ntp-simple 4.2.2.p4+dfsg-1ubuntu3 transition package
ii ntpdate 4.2.2.p4+dfsg-1ubuntu3 client for setting system time from NTP serv
$ dpkg -l|grep tz
ii tzdata 2007f-0ubuntu0.7.4 Time Zone and Daylight Saving Time Data
$ date
Sun Oct 28 19:20:25 CET 2007
$ sudo /etc/init.d/ntp stop
 * Stopping NTP server ntpd [ OK ]
$ sudo /usr/sbin/ntpdate ntp.ubuntu.com
28 Oct 18:20:53 ntpdate[7169]: step time server 91.189.94.4 offset -3609.986278 sec
$ date
Sun Oct 28 18:20:56 CET 2007

On a friend's machine, also running 7.04, the transition worked fine. However, there are at least two differences:
- His machine is running 24/7
- ntpd is not running, ntp is not installed. ntpdate and tzdata are installed.

[Mike (bild85)]

This is pretty lame. We're in the March 2008 cycle and this is still broken. I'm in EST and we just 'sprung forward', but my OS still thinks we're an hour behind:

$ uname -a
Linux ###### 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux

$ sudo dpkg -s tzdata
Package: tzdata
Status: install ok installed
Priority: required
Section: libs
Installed-Size: 6136
Maintainer: Martin Pitt <email address hidden>
Architecture: all
Version: 2007k-0ubuntu0.7.10.1
Replaces: libc0.1, libc0.3, libc6, libc6.1, locales
Depends: debconf | debconf-2.0
Description: time zone and daylight-saving time data
 This package contains data required for the implementation of
 standard local time for many representative locations around the
 globe. It is updated periodically to reflect changes made by
 political bodies to time zone boundaries, UTC offsets, and
 daylight-saving rules.
Original-Maintainer: GNU Libc Maintainers <email address hidden>

$ zdump -v /etc/localtime | grep 2008
/etc/localtime Sun Mar 9 06:59:59 2008 UTC = Sun Mar 9 01:59:59 2008 EST isdst=0 gmtoff=-18000
/etc/localtime Sun Mar 9 07:00:00 2008 UTC = Sun Mar 9 03:00:00 2008 EDT isdst=1 gmtoff=-14400
/etc/localtime Sun Nov 2 05:59:59 2008 UTC = Sun Nov 2 01:59:59 2008 EDT isdst=1 gmtoff=-14400
/etc/localtime Sun Nov 2 06:00:00 2008 UTC = Sun Nov 2 01:00:00 2008 EST isdst=0 gmtoff=-18000

[matt0001 (formicary)]

Spring 2008:

My desktop changed time with no problems. My laptop has not. Both are using 7.10 fully updated. The laptop is a Dell 1505N--one of the Dell's with Ubuntu pre-installed.

matt@dell:~$ sudo dpkg -s tzdata
Package: tzdata
Status: install ok installed
Priority: required
Section: libs
Installed-Size: 6136
Maintainer: Martin Pitt <email address hidden>
Architecture: all
Version: 2007k-0ubuntu0.7.10.1
Replaces: libc0.1, libc0.3, libc6, libc6.1, locales
Depends: debconf | debconf-2.0
Description: time zone and daylight-saving time data
 This package contains data required for the implementation of
 standard local time for many representative locations around the
 globe. It is updated periodically to reflect changes made by
 political bodies to time zone boundaries, UTC offsets, and
 daylight-saving rules.
Original-Maintainer: GNU Libc Maintainers <email address hidden>
matt@dell:~$ zdump -v /etc/localtime | grep 2008
/etc/localtime Sun Mar 9 09:59:59 2008 UTC = Sun Mar 9 01:59:59 2008 PST isdst=0 gmtoff=-28800
/etc/localtime Sun Mar 9 10:00:00 2008 UTC = Sun Mar 9 03:00:00 2008 PDT isdst=1 gmtoff=-25200
/etc/localtime Sun Nov 2 08:59:59 2008 UTC = Sun Nov 2 01:59:59 2008 PDT isdst=1 gmtoff=-25200
/etc/localtime Sun Nov 2 09:00:00 2008 UTC = Sun Nov 2 01:00:00 2008 PST isdst=0 gmtoff=-28800

[matt0001 (formicary)]

and just to add to the above post: The desktop, a homebuilt mongrel, was on during the time change and changed succesfuly. The laptop was fully shut-down.

[Cruncher (ubuntu-wkresse)]

bug #158664 is probably a duplicate, or at least closely related. Neither one of the bugs got much attention, it seems :-/
After getting completely annouyed by this ridiculous bug, I have been using the following workaround for some time now:
- disable/deinstall ntpd
- add a new startscript to /etc/init.d/rc2.d/S88ntpworkaround containing the single line "ntpdate ntp.ubuntu.com" (or whatever ntp server you prefer)

ntpdate should take care of the upcoming German daylight saving change on March 30th - I hope.

[Cruncher (ubuntu-wkresse)]

Sorry, I meant /etc/rc2.d/S88ntpworkaround of course.

[matt0001 (formicary)]

Update. Booted the laptop a second time today, now time is correct.

[Martin Pitt (pitti)]

On the affected laptop, can you please check whether the file /etc/timezone has the correct timezone for you? Can you please attach /etc/init.d/rc2.d/S88ntpworkaround, this is not a standard Ubuntu file, but something that Dell added.

[Martin Pitt (pitti)]

Dell Team, can you please describe what /etc/init.d/rc2.d/S88ntpworkaround is? Thank you!

[Cruncher (ubuntu-wkresse)]

Umh, sorry for the confusion, but please read my posts again, starting here: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/91418/comments/16

$ cat /etc/rc2.d/S88ntpworkaround
ntpdate ntp.ubuntu.com

[Martin Pitt (pitti)]

(Dell team, please unsubscribe again, this was just a confusion.)

Ah, I see. Well, ntpdate wouldn't help you if your computer has the wrong timezone configured. So what does /etc/timezone contain for you?

[Cruncher (ubuntu-wkresse)]

ntpdate *does* help, hence the workaround ;-)

$ cat /etc/timezone
Europe/Berlin
$ zdump -v /etc/localtime | grep 2008
/etc/localtime Sun Mar 30 00:59:59 2008 UTC = Sun Mar 30 01:59:59 2008 CET isdst=0 gmtoff=3600
/etc/localtime Sun Mar 30 01:00:00 2008 UTC = Sun Mar 30 03:00:00 2008 CEST isdst=1 gmtoff=7200
/etc/localtime Sun Oct 26 00:59:59 2008 UTC = Sun Oct 26 02:59:59 2008 CEST isdst=1 gmtoff=7200
/etc/localtime Sun Oct 26 01:00:00 2008 UTC = Sun Oct 26 02:00:00 2008 CET isdst=0 gmtoff=3600

[Mike (bild85)]

update - later that afternoon my PC updated correctly. It was turned off at the time of the change as well. (this seems to be the common denominator)

[Connor Imes (ckimes)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[Mike (bild85)]

I'm not sure how to test this again, but I don't see a solution in this thread that has been pushed upstream. I expect DST to throw off my time again this fall, and again next spring. Sorry for not contributing much to the solution.

[Connor Imes (ckimes)]

OK, why don't you post back in a month when the clocks change and let us know how it goes. Thanks.

[Nicolás Alvarez (nicolas-alvarez)]

Isn't it too late by then?

[Mike (bild85)]

Yes Nicolás, it will be too late by then. But with a free operating system, I guess we can't complain too much. :-p

I think it is related to the dual-boot setup. Ubuntu is careful to not throw off the system time for Windows when it detects it. I don't dual-boot anymore, so I don't think this one will affect me.

[Connor Imes (ckimes)]

Hey guys,
Did your clocks change correctly in Intrepid for Daylight Savings Time?

[Cruncher (ubuntu-wkresse)]

It worked fine for me, although unfortunately the machine was running at the time, so it is not an identical situation compared to last year.

[Marquis (markyb)]

Hey gang - just letting you know that on Hardy (8.04) 64-bit (dual boot with Vista 64-bit), my clock did not change with the arrival of non-summer time on Sunday night (3 days ago) here in Canberra. I am set to sync with Australian time servers, but nothing so far.

[Martin Meyer (elreydetodo)]

Here's something bad: my Karmic system says the time right now is 12:45AM EST. It's actually 11:45AM EST. It never adjusted for DST yesterday. NTP says I'm perfectly in sync with my nearest time server.

This was a fresh install from one of the Karmic beta releases about a month old. Are there any known remaining issues with DST adjustment?

FYI my timezone is set to Americas/New_York.

[machrider (machrider)]

This bug is pretty old, but I think I just saw it myself. In the US, daylight savings time began this morning. My jaunty box that was running at the time switched without a problem. My karmic laptop, which was off at the time (not hibernating), did not update when I booted it up today. I had to manually use the ntpdate command to fix the clock.

My timezone is also set to America/New_York.

[rusivi2 (rusivi2-deactivatedaccount)]

Thank you for reporting this issue.

Does this occur in Lucid?

[Bryan Cain (plombo)]

Daylight Savings Time in the US is over as of today, but the system clock on my Maverick install has not updated the time accordingly.

[Mike (bild85)]

My Mac laptop with Snow Leopard, Win7(*), and 10.10 was booted into the Ubuntu side during the switch, but it was in sleep mode. When i opened the lid and it came-to after DST ended, the time displayed correctly.

On a separate machine, 10.04.1 LTS Server edition was powered off during the switchover, and when I powered it on to check the time it was also displayed correctly.

(*) I enabled a registry key in Windows to force it to use UTC for the system clock, so now all three OSes use a common base-time:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]
"RealTimeIsUniversal"=dword:00000001

Bryan, is your system dual-boot? Was it powered on or sleeping 2 AM Sunday morning?

[Bryan Cain (plombo)]

It's a Wubi install on top of Windows Vista. However, Windows hasn't
been run on this computer for more than a week. At 2 AM Sunday morning,
it was completely powered off, although it was still on and in use at 1 AM.

On 11/07/2010 11:11 PM, itismike wrote:
> My Mac laptop with Snow Leopard, Win7(*), and 10.10 was booted into the
> Ubuntu side during the switch, but it was in sleep mode. When i opened
> the lid and it came-to after DST ended, the time displayed correctly.
>
> On a separate machine, 10.04.1 LTS Server edition was powered off during
> the switchover, and when I powered it on to check the time it was also
> displayed correctly.
>
> (*) I enabled a registry key in Windows to force it to use UTC for the system clock, so now all three OSes use a common base-time:
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]
> "RealTimeIsUniversal"=dword:00000001
>
> Bryan, is your system dual-boot? Was it powered on or sleeping 2 AM
> Sunday morning?
>

[dg1727 (dg1727)]

This issue still seems to exist on Natty (11.04), as of the fall 2011 change from Daylight Time to Standard Time. My scenario was similar to comments 4, 7, 18.
Desktop computer on which _no_ time-related customizations have been made, neither in Windows nor in Xubuntu (the only two OSes on this machine). Except, of course, that the time zone was specified during OS installation. The computer was powered off during the Daylight Savings Time transition.

[Anirban Ghosh (anirban-ninja)]

Facing the same issue in Ubuntu 13.10.
I live in Milwaukee, USA. Time did not
change automatically in Spring.

[cybernet (cybernet2u)]

7 years is not enough for a bug to be analyzed & fixed ?

[Anirban Ghosh (anirban-ninja)]

Still facing the same issue in Ubuntu 14.10.
I live in Milwaukee, USA. Time did not
change automatically in Spring.

[Greg Grossmeier (greg.grossmeier)]

job (jeppekdahl) : Please don't assign tickets to yourself unless you are actively working on a patch to fix the issue.

[Benjamin Drung (bdrung)]

The bug is not about tzdata itself (that package contains only the information about the timezones). Instead it is about the part of the system that takes care of changing the local time when the daylight saving switch is done. A solution/workaround is to change the system clock to be in UTC. Then the hardware clock does not need to be changed.

Is someone still affected by this bug?

[Launchpad Janitor (janitor)]

[Expired for Ubuntu because there has been no activity for 60 days.]