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 336367 - Evolution calendar items do not display time of items correctly
Evolution calendar items do not display time of items correctly
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.6.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
evolution[interop]
Depends on:
Blocks:
 
 
Reported: 2006-03-28 16:16 UTC by Wendell MacKenzie
Modified: 2006-08-29 09:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Wendell MacKenzie 2006-03-28 16:16:02 UTC
Please describe the problem:
After receiving meeting invites from MS Exchange 2003 users, the time of those
items once selected and added to my Calendar (personal or the one I have in
Exchange) are listed in my calendar 3 hours earlier.

My timezone is correct, (America/Montreal), and my system time is correct.  The
user who sent me the meeting invite has the EST timezone set and her time is
correct also.

Steps to reproduce:
1. receive a meeting request from a MS-Exchange user
2. accept the meeting
3. meeting reported in Evo calendar 3 hours earlier


Actual results:
lists the meeting earlier than supposed to.

Expected results:
should show the meeting at the time as specified in the meeting invite.

Does this happen every time?
yes

Other information:
Comment 1 André Klapper 2006-03-29 00:44:58 UTC
could be related or the same as bug 332911
Comment 2 Wendell MacKenzie 2006-03-29 21:49:59 UTC
yes, you are correct, I applied the patch listed in 332911 and it now lists my appt's correctly.  The pop-ups when you hover over appts still report bogus times though...but this is minor.

Thx.
wendell
Comment 3 Chenthill P 2006-08-29 09:15:50 UTC
This has been fixed as part of the fix for bug 332911.