After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 251361 - TZ environment variable (partially) ignored
TZ environment variable (partially) ignored
Status: RESOLVED DUPLICATE of bug 381132
Product: evolution
Classification: Applications
Component: Calendar
pre-1.5 (obsolete)
Other All
: Normal enhancement
: Future
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-11-24 23:39 UTC by Hein Roehrig
Modified: 2010-09-30 09:05 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Hein Roehrig 2003-11-24 23:39:51 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:

My computer has default time zone Europe/Amsterdam but currently I am using
America/New_York. Calendar displays the current day and notifications based
on the default time zone. 

Steps to reproduce the problem:
0. use tzconfig to set the default time zone to Europe/Amsterdam
1. export TZ=America/New_York in .bash_profile or similar
2. run evolution
3. go at 6:30pm EST to the Calendar view
4. set an appointment at 7pm

Actual Results:
3. the next day is marked as current (because it is already the 
   next day in Europe)
4. wait forever... because 7pm in Europe has already passed...

Expected Results:

How often does this happen? 

always

Additional Information:

I checked the environment of all evolution-related processes via
/proc/$PID/env and they all have the TZ variable set correctly.

I see that this can be fixed via Tools->Settings...->Calendar and
Tasks->General->Time but this is nonstandard and nonuniform behavior (the
mail component works fine with TZ...

Therefore it would be great if the TZ override for Calendar would be
optional (e.g., a checkbox whether the time zone is to be set explicitly)

Thanks,
Hein
Comment 1 Milan Crha 2010-09-30 09:05:38 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 381132 ***