Version: 4.4.10 (using KDE 4.6.2) OS: Linux I'm in Chile and the goverment extended the daylight saving time for a couple of months (until May 7). I have the latest tzdata package (version 2011e-1) which contains the updated rules for Chile. KOrganizer is using the correct time zone when saving events but displays the wrong time after restarting the application. Reproducible: Always Steps to Reproduce: 1. Make sure you have the 2011e-1 version of tzdata, your system is configured to use the Chile/Continental time zone and your system date is set before May 7, 2011 (and after April 7). 2. Create an event with date and time associated (before May 7) in KOrganizer Calendar and save it (for example: April 8 at 10:00 AM). 3. Restart KOrganizer (this is when the bug occurs). 4. Double click the event to edit. 5. Click save. Actual Results: After step 3 the event is shifted 1 hour later (April 8 at 11:00 AM) in the calendar. After step 4 the event displays the correct time in the edit dialog (April 8 at 10:00 AM). After step 5 the event displays the correct time in the calendar. Expected Results: After step 3 the event should not change from when it was last saved (should be at Friday 8 ar 10:00 AM). It looks as if KOrganizer is using an outdated time zone database for some operations and the updated system database for others.
What linux distro are you using, and with which options did you/distro compile libical ?
I am using Arch Linux, with official packages. http://www.archlinux.org/packages/extra/i686/libical/ Here is the configure command, according to http://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/libical ./configure --prefix=/usr \ --enable-shared \ --disable-static
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.