New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 12579 link

Starred by 15 users

Issue metadata

Status: Fixed
Owner:
Closed: May 2010
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
M-3

Restricted
  • Only users with EditIssue permission may comment.



Sign in to add a comment

Google chrome wrong time zone in history for Warsaw

Reported by ivan.huz...@gmail.com, May 23 2009

Issue description

Chrome Version       : 2.0.172.28

Hello!

I use Google Chrome 2.0.172.28 and in history in listed wrong time.
I'm current in the Karlovac,Croatia time zone (GMT+2), however, Chrome 
history thinks my time zone is +1, but Firefox still reads it as +2. 
When I type: 
javascript:new%20Date().toString() 
in Chrome Omnibar, I get: 
Sat May 23 2009 15:34:49 GMT+0200 (Central European Daylight Time) 
Which is Correct. 
However, when I type that line into Firefox, I get: 
Sat May 23 2009 15:35:10 GMT+0200 (Central European Daylight Time) which is 
correct. 
But Google chrome history shows GMT+1 time.
How to fix that?
 
1) Please provide OS and 
2) what your OS time zone setting is (I am assuming GMT+1 and then you have the 
"automatically adjust clock for daylight saving changes" ticked?).

FWIW, I am also on CEST and I am not able to repro on Win XP.
Hello!

My OS:
Microsoft Windows XP
Professional
Version 2002
Service Pack 3

OS time zone: GMT+1 with ticked box where says:
"automatically adjust clock for daylight saving changes" 

My computer is now on GMT+2 time zone as we are now in summer.

Today at 16:40 CEST (GMT+2) and in attachment you can see that Google
Chrome History page sad that is 3:40 PM, so it shows wrong time.

google chrome history.jpg
48.5 KB View Download
This is really strange. 
I can not repro this behavior on Win XP SP2. 
Tried both version 2.0.181.1 and 2.0.172.28
Hello!

My OS:
Microsoft Windows XP
Professional
Version 2002
Service Pack 3

OS time zone: GMT+1 with ticked box where says:
"automatically adjust clock for daylight saving changes" 

My computer is now on GMT+2 time zone as we are now in summer.
You can see that in attachment in this message.

Now is 12:10 CEST (GMT+2)

When I open Google Chrome 2.0.172.28 and when I open history by pressing Ctrl+H I get 
time 11:10 AM, same as you can see in attachment in previous message.

When I type: 
javascript:new%20Date().toString() 
in Google Chrome 2.0.172.28 I get correct time, date and timezone info:
Tue May 26 2009 12:19:30 GMT+0200 (Central European Daylight Time)

image3.jpg
24.1 KB View Download
image1.jpg
24.5 KB View Download
image2.jpg
27.5 KB View Download

Comment 5 by xlyuan@chromium.org, May 28 2009

Labels: -Area-Misc Area-BrowserUI I18N
Status: Untriaged
hmm, I am able to reproduce this issue on my English XP with GMT+ 01:00 time zone:

Steps:
1. Set OS time zone as "(GMT+01:00)Sarajevo,Skopje,Warsaw,Zagreb"
   >>Make sure "Automatically adjust clock for daylight saving changes" is checked
2. Launch Chrome
3. Visit google.com
4. Hit Ctrl + h
5. Observe

You will see the time displayed in history page has one hour difference compared with 
OS current time.

This issue happens on all Chrome channels and Chromium trunk, checked on:
2.0.172.28 (Official Build )
3.0.183.0  (Developer Build 17021)



Time_Zone.jpg
208 KB View Download
Thanks for the additional info. I did not have the imagination needed to think that 
it would make a difference whether you select 
"(GMT+01:00)Sarajevo,Skopje,Warsaw,Zagreb" or, say, 
"(GMT+01:00)Brussels,Copenhagen,Madrid,Paris" since these are exactly the same time 
zone with the same daylight savings dates...

I can repro with "Sarajevo..." but not with "Brussels..." or any of the other 
European GMT+1 entries.

There seems to be something really fishy going on. Not clear if it is a Windows issue 
or something in our code that would treat the "Sarajevo..." selection differently. 
The former seems most likely to me though I have not been able to find any reports on 
this on the web.
So, you know this problem and next update of Google Chrome needs to fix this problem.
My time zone in Windows XP Pro SP3 is (GMT+01:00)Sarajevo,Skopje,Warsaw,Zagreb
Hello!
Today at 22:00 CET (GMT+2) I did update Google Chrome to the latest version 2.0.172.30 
and problem is not fixed.
Time displayed in history page has one hour difference compared with OS current time.
When this will be fixed??


+cc mal
Hello!
Today at 22:50 CET (GMT+2) I did update Google Chrome to the latest version 2.0.172.31 
and problem is not fixed.
Time displayed in history page has one hour difference compared with OS current time.
When this will be fixed??
 Issue 15304  has been merged into this issue.
Labels: Mstone-3 Fixit
Status: Available

Comment 13 Deleted

Hello!
I use Google Chrome latest version 2.0.172.33 and problem is not fixed.
Time displayed in history page has minus one hour difference compared with OS current 
time.
When this will be fixed??
Status: Started
I reproduced and implemented a local fix in wintz.c.  I suspect this is fixed upstream 
in a later revision of icu38, that's yet to be verified.  See:
  svn diff -r 24593:HEAD http://source.icu-
project.org/repos/icu/icu/trunk/source/common/wintz.c
Status: Fixed
Fixed in r20192.
DEPS updated in r20205, see http://codereview.chromium.org/155244.
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=20192 

------------------------------------------------------------------------
r20192 | cmp@google.com | 2009-07-08 14:47:39 -0700 (Wed, 08 Jul 2009) | 8 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu38/source/common/wintz.c?r1=20192&r2=20191

Fix typo in Europe/Warsaw time zone name.

BUG= 12579 
TEST=On WinXP, change tz to "Sarajevo." Shut down and
restart Chromium.  Browse to google.com, open history,
verify time on latest entry for google.com exactly
matches system clock.
Review URL: http://codereview.chromium.org/149352
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=20205 

------------------------------------------------------------------------
r20205 | cmp@google.com | 2009-07-08 16:16:02 -0700 (Wed, 08 Jul 2009) | 6 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/DEPS?r1=20205&r2=20204

Update icu38 dep with a time zone issue fix.

BUG= 12579 
TEST=none

Review URL: http://codereview.chromium.org/155244
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=20268 

------------------------------------------------------------------------
r20268 | laforge@chromium.org | 2009-07-09 10:02:21 -0700 (Thu, 09 Jul 2009) | 10 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/172/src/DEPS?r1=20268&r2=20267

Merge 20205 - Update icu38 dep with a time zone issue fix.

BUG= 12579 
TEST=none

Review URL: http://codereview.chromium.org/155244

TBR=cmp@google.com

Review URL: http://codereview.chromium.org/156002
------------------------------------------------------------------------

Status: Verified
Verified on stable channel build 2.0.172.37 and 2.0.172.38, fixed.
When this update will be available?? 
Ivan, the best place to look for updates is http://googlechromereleases.blogspot.com/
I have a similar issue as well.  When I use Google Chrome to check Gmail, it is off by 
six hours.  It shows the time in Thailand where my desktop was originally set up and 
installed the programs.  BUT when I use IE, the timestamp is displayed correctly.  IE 
had a problem before the daylight saving time was over.  Any advice would be 
appreciated.  Thanks.

Comment 26 by Deleted ...@, Feb 11 2010

I had the same problem but was able to fix it. This worked for me:
- On any Google search results page, select "more" from the bar across the top and 
then select "Calendar."
- On the left-side of the calendars there is an option that says "my calendars," 
select "settings"
- Under the Calendar settings, select the "general" tab. 
- On this screen, make sure that your Country, Time Zone, and Location entries are 
all consistent with where you are.

Hope that helps!
Google Time Fixer.jpg
133 KB View Download

Comment 27 by js...@chromium.org, Feb 11 2010

Could you file a new bug with more details and add a pointer to the new bug here?

 What you observed is different from what's dealt with here (Sarajebo timezone). 

Thanks
I use latest Google Chrome and everything is OK.
I have the same issue, and the google calendar tip didnt work for me. My time is Buenos 
Aires GMT -3 and the history in google chrome is one hour in the future. (if i take a 
look at history now, it would say 11:30am at this page, and its 10:30am here). In 
google calendar it display the time correctly.
Update to latest version of Google Chrome and everything will be OK.
I have the latest version of Chrome and the bug is still there. (4.0.249.89) 
Today, march 21, the bug disappeared. It seems like the bug was related to “summer 
time”. This summer my country did NOT use daylight-saving time. And it seems that 
Chrome synchronizes time with a server rather than the machine´s.
Chrome 5.0.342.7 beta on Ubuntu 9.10 kernel 2.6.31-20 set to "America/New_York" time 
zone.  History items appear with time stamp -1 hour off system time. 

Comment 34 by rkuz...@gmail.com, Mar 30 2010

bug is still there, or just have introduced again

5.0.365.0 (42923) 
Ubuntu 9.10 (2.6.31-20)

new Date().getTimezoneOffset() returns '-60'
while '300' is expected for US Central.

Comment 35 by Deleted ...@, Mar 30 2010

I also am seeing history off by -1 hour from system time in Chrome 5.0.342.7 beta, 
running Ubuntu 10.04 Beta.
Same problem in 5.0.356.2 dev on Ubuntu 9.10; history has been off by one hour ever 
since the time change on March 14th.
On the other hand, I'm running 5.0.342.7 beta on gentoo (linux 2.6.32.10) at work, and 
am NOT having this issue there.  So perhaps it's something specific to how 
Ubuntu/others handle daylight savings?
My email timestamps are 8 hours in the future. I restarted Chromium to no avail. I'm 
running version 5.0.365.0 on Ubuntu Karmic. The clock is right on the computer.

It's not a GMail thing. The problem happens even in a JavaScript console. If I type 
new Date() I get: Tue Apr 06 2010 17:15:27 GMT+0100 (PDT). Really? PDT is supposed to 
be GMT-7, not GMT+1!

Comment 39 by Deleted ...@, Apr 7 2010

new Date();
Wed Apr 07 2010 16:54:51 GMT+0100 (EDT)

Ubuntu 9.10, this is very irritating indeed.
5.0.365.0 (42923) Ubuntu
I also reproduce this bug:

chromium version 
6.0.401.0 (46909) Ubuntu

Ubuntu version
10.04 LTS

Timezone:
GMT +0200 (Madrid)

My history page is always two hours in the past, but if I type "javascript:new 
Date().toString()" in the console, the time and timezone is fine.

Can anyone reopen this bug, please?

Labels: -Mstone-3 Mstone-6
Status: Untriaged
Re-opening. I also see this on my Linux box on 5.0.375.38. 
In fact my history is one hour earlier than my CEST time - which I get from JS and on 
the system.

Comment 42 by js...@chromium.org, May 27 2010

Labels: -OS-All -Mstone-6 -Fixit OS-Windows Mstone-3
Summary: Google chrome wrong time zone in history for Warsaw
Filed this bug as fixed. This bug was very specific (Warsaw timezone incorrectly parsed on Windows). 

I'm filing a new bug ( bug 45176 )

Comment 43 by js...@chromium.org, May 27 2010

Status: Fixed
I am experiencing this Goobuntu. My Time zone is set to America/Los_Angeles. I am located in Mountain View, CA. I was interested in seeing when I accessed a page, but history claimed I accessed it at a time when I was not at my computer, which was disconcerting. Then I saw that the timestamp for the latest access was an hour earlier.
Hi, I'm having this problem, still on Chromium 5.0.375.99 (51029) on Ubuntu 10.04.

I'm in NYC and all my history items are an hour earlier.

Note: Has this bug officially been merged into this one?

http://code.google.com/p/chromium/issues/detail?id=45176

If so, it should be made clear at the top of this page.  And are you sure this problem is solved if others are having the same problem with different time zones?  Was there an identical bug that was specific to Warsaw? Sounds unlikely.
Okay, since none of the developers feel the need to actually "help" any non-developers figure out what's going on with this issue, here is a link to the current bug, which has been merged with another bug, which had yet another merged with it... oh... you get my point (this system is ridiculous and convoluted, btw):

http://code.google.com/p/chromium/issues/detail?id=38632

It LOOKS like it was fixed on Jun 29th, which means the changes will probably be present in one of the next beta builds (and is quite possibly now in the daily build).

Dear Developers:

Thank you so much for spending your time making Chromium happen.  All of us non-developers really appreciate it.  However, every now and then it would be nice if one of you stopped and actually typed out an explanation of what was going on.  It would only take a minute or two, and I know you're already putting your own, unpaid time into this, but it would make the open-source community better for everyone.

Thanks!
Labels: -I18N bulkmove Feature-I18N
Summary: Google chrome wrong time zone in history for Warsaw
Chrome Version       : 2.0.172.28

Hello!

I use Google Chrome 2.0.172.28 and in history in listed wrong time.
I'm current in the Karlovac,Croatia time zone (GMT+2), however, Chrome 
history thinks my time zone is +1, but Firefox still reads it as +2. 
When I type: 
javascript:new%20Date().toString() 
in Chrome Omnibar, I get: 
Sat May 23 2009 15:34:49 GMT+0200 (Central European Daylight Time) 
Which is Correct. 
However, when I type that line into Firefox, I get: 
Sat May 23 2009 15:35:10 GMT+0200 (Central European Daylight Time) which is 
correct. 
But Google chrome history shows GMT+1 time.
How to fix that?

Comment 48 by Deleted ...@, Apr 27 2012

Hi,
I run Debian Squeeze in time zone GMT+1 Berlin. The time within Google Chrome 18.0.1025.151 is 1 hour ahead.
Project Member

Comment 49 by bugdroid1@chromium.org, Oct 13 2012

Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Project Member

Comment 50 by bugdroid1@chromium.org, Mar 10 2013

Labels: -Mstone-3 -Feature-I18N Cr-UI-I18N M-3
Project Member

Comment 51 by bugdroid1@chromium.org, Mar 13 2013

Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue
Project Member

Comment 52 by bugdroid1@chromium.org, Mar 20 2013

Labels: -Cr-UI-I18N Cr-UI-Internationalization

Sign in to add a comment