We couldn't reproduce the problem here using Ubuntu.
We have checked here the situation by trying different cases:
- server is running with the system settings, web client too
- server is running with TZ='AEST-10AEDT-11,M10.5.0,M3.5.0', web client left as-is
- server and web client are running with TZ='AEST-10AEDT-11,M10.5.0,M3.5.0'
In all cases, both the GTK client and the Browser show the correct values.
Keep in mind that using something like TZ='AEST-10AEDT-11,M10.5.0,M3.5.0' is just for testing purpose: the server stores date and time in its current timezone.
The previous comment (#9) was about the server. Probably the GTK client installer still doesn't correctly include the zoneinfo data.
We couldn't reproduce the problem here using Ubuntu.
We have checked here the situation by trying different cases:
- server is running with the system settings, web client too 10AEDT- 11,M10. 5.0,M3. 5.0', web client left as-is 10AEDT- 11,M10. 5.0,M3. 5.0'
- server is running with TZ='AEST-
- server and web client are running with TZ='AEST-
In all cases, both the GTK client and the Browser show the correct values.
Keep in mind that using something like TZ='AEST- 10AEDT- 11,M10. 5.0,M3. 5.0' is just for testing purpose: the server stores date and time in its current timezone.
The previous comment (#9) was about the server. Probably the GTK client installer still doesn't correctly include the zoneinfo data.