Bug 179075 - same event appears on two consecutive days
Summary: same event appears on two consecutive days
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 4.1
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-29 20:27 UTC by Richard Birnie
Modified: 2017-01-07 22:51 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Birnie 2008-12-29 20:27:09 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

This was originally reported at https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/310127

Steps to reproduce:
1) Set time zone to Europe/London (effectively UTC)
2) Create an event that runs from 2300 on day 1 to 0100 on day 2
3) The event is displayed correctly. In fact it displays as two parts labelled 1/2 and 2/2 at the correct times, which seems sensible to me.
4) Change timezone to America/Los Angeles. Settings > Configure KOrganiser > Time and Date
5) When presented with the dialog 'Keep Absolute Times' choose keep times
6) The result is that the same event now appears as two duplicate events on consecutive days.

The original reporter suggests that it is sufficient to create the events in a non-UTC timezone. I just happen to be in a UTC timezone so these are the steps I took. I'm not even completely sure if this is a bug but the current way of displaying this seems counter intuitive at least.
Comment 1 Denis Kurz 2016-09-24 18:47:51 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 korganizer (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:51:11 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.