Version: 3.5 (using KDE 3.5.1 Level "a" , SUSE 9.3 UNSUPPORTED) Compiler: gcc version 3.3.5 20050117 (prerelease) (SUSE Linux) OS: Linux (x86_64) release 2.6.11.4-21.10-smp The bug looks like like bug 86837 which is declared to be resolved. However, I see the same kind of bug now with the "Calendar" function in the "Kontact" Application (Korganizer) (KDE 3.5.1 on a SUSE 9.3 client system). I exchange my appointments with a OpenExchange server based on SLES 9 an OX5. Both systems have exactly the same time zone settings and synchronize time via NTP. Whenever I save a new (!) appointment with "calendar" the present time line shifts by two hours back (i.e. to GMT). Only the time line (red indicator of present the time) is affected. All previously saved appointments do not change their timestamp. After the next synchronization with the OX server the time line is OK again. I do not see why the time line indicator should change its value.
Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list.
I want to confirm the "bug" that R. Kainhofer reported. I have KDE 3.5.7 on a SUSE 10.2. I, too, use KMAIL connected to a SLES 9 Server with OX5 (latest SP3 installed). Connection is done via WebDav. When I open the calendar the (red) time line for the present time has the correct value. However, as soon as I save some new calendar appointments the present time line changes by 2 hours and remains there. In addition to what R. Kainhofer I see this behaviour also whenever I change an already existing appointment and submit the changes to the OX5. In my opinion there is no real bug in the SLES oder KDE components. I think there is a bug in the webdav answer from the OX5. See for comparison the discussion in the Mozilla forum for Sunbird. The Mozilla people there have analyzed a comparable problem and found that the OX5 does not send a correct time value back to the client. See https://bugzilla.mozilla.org/show_bug.cgi?id=339960 I checked the time settings for the server and the client system and the time settings for the OX5 components. Everything there is consistent. I in addition checked for changes when setting the clock time of the server to UTC or Local Time -> no changes of the described behaviour. Could somebody of the KDE developers have a word with the OX5 people ?
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.