Summary: | vcalendar import of GMT not set to local daylight time | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | Jed Clear <clear> |
Component: | import/export | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | christophe |
Priority: | NOR | ||
Version: | 3.2.1 | ||
Target Milestone: | --- | ||
Platform: | FreeBSD Ports | ||
OS: | FreeBSD | ||
Latest Commit: | Version Fixed In: |
Description
Jed Clear
2004-04-27 02:29:46 UTC
The DTSTART and DTEND saved in std.ics for this event are identical to the .vcs input, so it's something with displaying the Z timed events, rather than vcalendar translation. thanks for the bug report. This issue seems to be fixed in the latest version of korganizer. Cheers, Reinhold Was this tested before the end of daylight savings time, or with a suitably altered system clock? This bug is back in 3.4. Exact same description as the original poster, I'm using Kontact (1.1) (slackware 10.1 packages of 3.4) and getting vCalendar data from an email. It's an hour off and we're all in the same timezone, synchronized to the same timeserver. DTSTART:20050526T203000Z DTEND:20050526T210000Z and it shows up as 3:30pm to 4:00pm, not 4:30pm to 5:00pm. Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list. 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. 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. |