![]() |
2010-05-26
, 10:36
|
|
Posts: 1,038 |
Thanked: 1,408 times |
Joined on Feb 2010
@ London
|
#2
|
![]() |
2010-05-26
, 10:38
|
|
Posts: 194 |
Thanked: 207 times |
Joined on Dec 2009
@ Bristol, UK
|
#3
|
![]() |
2010-05-26
, 11:41
|
Posts: 51 |
Thanked: 23 times |
Joined on Apr 2010
@ Zagreb, Croatia
|
#4
|
![]() |
2010-05-26
, 11:47
|
Posts: 278 |
Thanked: 303 times |
Joined on Feb 2010
@ Norwich, UK
|
#5
|
It should be GMT. Daylight savings should change time, not the time zone. I'll report it as a bug.
![]() |
2010-05-26
, 12:28
|
|
Posts: 466 |
Thanked: 180 times |
Joined on Feb 2010
|
#6
|
![]() |
2010-05-29
, 06:10
|
Posts: 143 |
Thanked: 57 times |
Joined on Jan 2010
@ Stockholm, Sweden
|
#7
|
![]() |
2010-06-15
, 06:21
|
|
Posts: 266 |
Thanked: 89 times |
Joined on Jan 2010
@ Norway
|
#8
|
UK is GMT +1 instead of GMT, Europe is GMT +2 instead of GMT +1, etc...
This lead to synchronization problems with remote servers, Exchange, etc. and if synchronized alarms go off one hour in advance.
Workaround is to disable automatic Date and time update and select time zone one hour closer to GMT.
Did anyone else notice this problem?