Bug 210920 - Kontact displays events at wrong time when working w/ multiple time zones
Summary: Kontact displays events at wrong time when working w/ multiple time zones
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: calendar (other bugs)
Version First Reported In: 4.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-18 00:12 UTC by ben chang
Modified: 2017-01-07 22:42 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ben chang 2009-10-18 00:12:27 UTC
Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    Ubuntu Packages

If you schedule events in the Calendar in a time zone which is different from the machine's local time zone, the Calendar will only display them relative to the machine's local time and cannot display them in the correct time.

For example: I live in one time zone (Indiana, in the  US Eastern time zone), and work in another (Chicago, in the US Central time zone, which is -1 hour).

At home, I schedule an event to take place at 10:00 AM, Central time, in Chicago.  But, when I view my calendar, it always appears at 11:00 AM, because the machine is currently physically in Indiana.

It may be that Kontact believes I'm going to teleconference and so I want to know what time the event is relative to Eastern time.  This is incorrect if the user is not going to teleconference but takes a train to the meeting instead.  

I have some images illustrating the problem in this thread:

http://forum.kde.org/viewtopic.php?f=20&t=77107#p123907
Comment 1 Denis Kurz 2016-09-24 19:22:55 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:42:37 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.