c2c-oerpscenario team mailing list archive

["Xavier \(Open ERP\)" <711084@xxxxxxxxxxxxxxxxxx>]

** Changed in: openobject-client-web
    Milestone: 6.0.2 => 6.0.3

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/711084

Title:
  [6.0,trunk] pytz zoneinfo missing from windows packaging - timezone
  conversion not working

Status in OpenERP GTK Client:
  Confirmed
Status in OpenERP Web Client:
  Confirmed

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://powerphil.wordpress.com/2011/01/28/how-to-install-and-
  configure-an-openerp-6-0-1-server-and-web-server-on-an-
  ubuntu-10-10-server/).

  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-10AEDT-11,M10.5.0,M3.5.0'
  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.