[6.0,trunk] pytz zoneinfo missing from windows packaging - timezone conversion not working
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo GTK Client (MOVED TO GITHUB) |
In Progress
|
Medium
|
OpenERP Publisher's Warranty Team | ||
Odoo Web Client |
Incomplete
|
Medium
|
OpenERP Publisher's Warranty Team |
Bug Description
OpenERP server and web client 6.0.1 running on Ubuntu server (32-bit) 10.10
Postgres 8.4
Windows GTK client and web browser (Google Chrome) on WIndows 7 (64-bit)
(Server and web client were set up as per http://
Problem is that the times shown in the GTK client are shown at GMT (unless the server's TZ environment variable is set), i.e. they ignore the user's Timezone preference.
However, the web client works correctly.
More details:
Ubuntu server's time is correctly set to GMT. For example, if the time in London is 1am, the server's time also shows 1am (by doing a "date" on the command line, and the TZ environment variable is not set to anything).
Both openerp-server and openerp-web processes are running without any TZ setting.
Then log into OpenERP using a web browser; set the User's preference to Australia/Sydney; create a new Phone Call, Outbound; the time correctly shows 12 noon (GMT + 11 hours, Sydney currently being on summer time).
Do the same in the GTK client; the time shows 1am - wrong; it should be 12 noon.
---------
More information:
So try to work around the problem: in the .bashrc file of the openerp user that runs the openerp-server process, set the TZ, viz:
TZ='AEST-
export TZ
Restart the service; log into the GTK client; create a new phone call; the time now shows correctly (for the wrong reasons, admittedly).
Go to the web browser and do the same thing; the time now shows 19 hours ahead of what it should be (on the next day!). Wrong.
So it looks like the web client is taking timezone time into account, in addition to whatever the openerp-server is doing, and it should be the other way around: the openerp-server should be calculating the correct time, and the web server should just be presenting it.
Changed in openobject-server: | |
status: | Incomplete → Triaged |
Changed in openobject-client: | |
assignee: | OpenERP's Framework R&D (openerp-dev-framework) → OpenERP Publisher's Warranty Team (openerp-opw) |
Changed in openobject-client-web: | |
assignee: | OpenERP's Framework R&D (openerp-dev-framework) → OpenERP Publisher's Warranty Team (openerp-opw) |
Changed in openobject-client-web: | |
milestone: | 6.0.2 → 6.0.3 |
Changed in openobject-client: | |
status: | Fix Released → Incomplete |
status: | Incomplete → In Progress |
Changed in openobject-client-web: | |
status: | Invalid → Confirmed |
status: | Confirmed → Incomplete |
This is NOT a duplicate of bug #701407 because:
- there IS a full list of timezones in the User's preferences.
- I also installed the latest version of pytz-2010o; this does not affect the problem.
The server DOES observe the TZ environment variable and DOES calculate the time, but the problem is that the web-client ALSO calculates time, but using the time from the server, so that if you are 10 hours ahead of GMT, your web client is 20 hours ahead!