Bug 170897 - wrong event displayed in kontact overview
Summary: wrong event displayed in kontact overview
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: calendar (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-12 08:32 UTC by Anders Lund
Modified: 2017-01-07 22:30 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Anders Lund 2008-09-12 08:32:47 UTC 
Version:           4.1.0 (using 4.1.1 (KDE 4.1.1), Kubuntu packages)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.24-16-generic

I have a repeated event, which i at some point changed for all future instances, so that the start and end time was changed.

Now in the calendar views the correct instance is displayed, but in the overview the wrong one displayed, leading to confusion and error.
Comment 1 Adrien Cordonnier 2009-03-26 13:08:08 UTC 
I have a similar bug for not repeating tasks.

Task time are correctly displayed in the calendar view with the correct timezone (Europe/Paris). In Kontact overview, event times are one hour late.

This bug is likely to be related with bug 170380 and many similar bugs recently reported (usually about timezone settings in Kalendar and Kcontrol). On my computer, every timezone settings in Kalendar and Systemsettings are correctly set to Europe/Paris and are not changing.
Comment 2 Denis Kurz 2016-09-24 19:25:02 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 3 Denis Kurz 2017-01-07 22:30:08 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.