Bug 147321 - Multiple timezone information systems in korganizer can lead to problems
Summary: Multiple timezone information systems in korganizer can lead to problems
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: timezones (show other bugs)
Version: unspecified
Platform: Compiled Sources Solaris
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-28 11:39 UTC by Martin Ostertag
Modified: 2017-01-07 22:28 UTC (History)
1 user (show)

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 Martin Ostertag 2007-06-28 11:39:05 UTC
Version:            (using KDE KDE 3.5.7)
Installed from:    Compiled From Sources
Compiler:          gcc 3.4.6 
OS:                Solaris

Currently Korganizer uses 2 different timezone information systems for processing the timezone information:
- libical uses its own timezone system for processing ical files/events
- the preferences dialog uses the KTimezones class from kdecore to display the available timezones, which uses the timezone information system from the operating system

This can lead to problems on some systems (e.g. Solaris), if the systems timezone information system contains timezones which are not available in the libical timezones or if there is a mismatch in the spelling.
Korganizer should only use one timezone information system for the preferences dialog and for the conversion of the events.
Comment 1 Sergio Martins 2011-11-04 22:47:25 UTC
workaround: libical has an option to ignore it's builtin database
Comment 2 Denis Kurz 2016-09-24 18:52:37 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 3 Denis Kurz 2017-01-07 22:28:26 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.