Bug 1057104 - Timezone Europe/Italy leads to wrong dates on DST change at 00:00:00
Summary: Timezone Europe/Italy leads to wrong dates on DST change at 00:00:00
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 20
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-23 13:09 UTC by Seby Carta
Modified: 2015-06-29 14:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 14:41:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Seby Carta 2014-01-23 13:09:03 UTC
Description of problem:
I opened this bug some time ago in opensuse bugzilla, with no luck. Now i want to repropose it here, the problem still persist on linux systems after many years.
Some web site checks the validity of the date provided in a form using JavaScript performing a "tmp =
new Date (form_year, form_month-1, form_day)" and then checking whether
"form_year = tmp.getYear()" and so on.

This induces a wrong answer for some dates where DST occurred (format:
dd/mm/yyyy): 22/05/1966, 28/05/1967, 01/06/1969, 31/05/1970, 23/05/1971,
28/05/1972, 03/06/1973, 26/05/1974, 01/06/1975, 30/05/1976, 22/05/1977,
28/05/1978, 17/05/1979.

For instance, a "new Date(1972, 4, 28)" returns "May 27 1972, 23:00:00 GMT+0100
(CET)" instead of the correct date "May 28 1972...".

The point in common for all these dates is that the DST change happened at
00:00:00.
However there are other dates where the DST change happened at 00:00:00 that do
not induce the above error: 04/06/1916, 01/04/1917, 10/03/1918, 02/03/1919,
21/03/1920, 15/06/1940, 16/03/1947, 26/05/1968.

For all remaining years, either there was no DST change or it happened at a
time different from 00:00:00 (usually 02:00:00).

I performed the above tests using the addon FireBug and adding a "new
Date(...)" watch.

This problem occurs in Firefox as well as Chrome but not in Opera and
Konqueror, accordingly to reports from forum users.
Moreover, the same happens for other distributions (Mandriva, Fedora, Ubuntu)
but not on Windows (with the same version of Firefox, for instance), so it
seems to be something independent from the browser and OS but dependent on an
element that is common for several Linux distributions, such as the timezone
package.

If I zdump the Europe/Rome timezone relative to years 1972 (where error occurs)
and 1968 (where error does not occur), the result is essentially the same:

orodruin:/home/ori # zdump -v Europe/Rome|grep 1968
Europe/Rome  Sat May 25 22:59:59 1968 UTC = Sat May 25 23:59:59 1968 CET
isdst=0
Europe/Rome  Sat May 25 23:00:00 1968 UTC = Sun May 26 01:00:00 1968 CEST
isdst=1
Europe/Rome  Sat Sep 21 21:59:59 1968 UTC = Sat Sep 21 23:59:59 1968 CEST
isdst=1
Europe/Rome  Sat Sep 21 22:00:00 1968 UTC = Sat Sep 21 23:00:00 1968 CET
isdst=0
orodruin:/home/ori # zdump -v Europe/Rome|grep 1972
Europe/Rome  Sat May 27 22:59:59 1972 UTC = Sat May 27 23:59:59 1972 CET
isdst=0
Europe/Rome  Sat May 27 23:00:00 1972 UTC = Sun May 28 01:00:00 1972 CEST
isdst=1
Europe/Rome  Sat Sep 30 21:59:59 1972 UTC = Sat Sep 30 23:59:59 1972 CEST
isdst=1
Europe/Rome  Sat Sep 30 22:00:00 1972 UTC = Sat Sep 30 23:00:00 1972 CET
isdst=0

so timezone seems to be innocent.

Version-Release number of selected component (if applicable):


How reproducible:
see above


Additional info:

happen on all linux distributions i have tried. This is very annoying bug , for example i cannot enter on my bank account with firefox or chrome because of the failed verification of my birth date. ABSURD! 
No problem on firefox for windows or with opera.

Comment 1 Fedora End Of Life 2015-05-29 10:38:17 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-06-29 14:41:25 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.