Version: 4.4.0 (HEAD) (using KDE 3.1.93 (CVS >= 20031028), SuSE) Compiler: gcc version 3.3 20030226 (prerelease) (SuSE Linux) OS: Linux (i686) release 2.4.20-4GB When syncronizing an event created in Kontact/KOrganizer with start time set to e.g. 14:00 CET the event shows up in DateBook with the start time as 13:00. When syncronizing an event created in DateBook with start time set to e.g. 13:00 CET the event shows up in Kontact/KOrganizer with the start time as 14:00. PDA: PalmIII, PalmOS 3.0 Time zone is set to Copenhagen/Europe (CET)
> Time zone is set to Copenhagen/Europe (CET) On the laptop I mean... And I have tried both with and without the time sync conduit.
Actually it sounds a bit like bug #37289 but it is shown as resolved.
I have this problem too. My timezone is set to Vienna/Europe, and I noticed that the .ics files themselves use GMT for storing the time of events. Somehow these times copy over to my Visor, but without the timezone information... My version of KDE: 3.2 beta 2 on Gentoo. Adrian
Hmm, now I am confused. I tried a sync today, but instead of specifiying the calendar file in the conduit's settings pane, I used the "standard calendar" option. I got the right times onto my visor :) Adrian
I have the same problem, noticed it just today. Synced my appointments over: they have the right time in Korganizer. After sync, they are more than 4 hours transposed, which is more than the timezone offset (I live in the CET timezone). However, when I set an alarm for an appointment, it also sets off 4 hours too late... Has anyone observed that as well?
I'm EST and have a -5 offset in Korganizer, when I switch the conduit location to standard and resync from HHtoPC, it's correct (though the log says it did it to my non-standard ICS file anyway!?!)
i've been having the same problem (from time-shifted entries to synch not producing any entries at all) i solved it (or worked around the bugs :p), at least for now ;) this is what i did: 1 backupped and removed all *.ics (iCalendar) files in /home/adriaan/.kde/share/apps/korganizer/ 2 configured a vCalendar resource (in kde resource config --> /home/adriaan/.kde/share/apps/korganizer/std.vcs) 3 merged my old std.ics with the new std.vcs using korganizer 4 completely removed the sections in kpilotrc that configured the conduits they now read: [todoOptions] ConduitVersion=10 NextSyncAction=0 [vcalOptions] NextSyncAction=0 5 restarted kpilot, selected calendar/todo conduits (leaving the default values) 6 hit synch 7 grinned liked an idiot and went out to grab lunch/buy textbooks :)
*** Bug 79083 has been marked as a duplicate of this bug. ***
The workaround above didn't work for me - merging new vcal with old icd worked, editing the kpilotrc as well, but the sync once more left the wrong times in the calender app on the palm :-/
*** Bug 74199 has been marked as a duplicate of this bug. ***
*** Bug 74221 has been marked as a duplicate of this bug. ***
I'm still seeing this problem in KDE 3.2.2 on Mandrake.
changing from a given calendar-file to the standard calendar resolved this problem for me. Time in korganizer and on palm is now in sync.
Upped priority, etc. Still no closer to actually working on it though.
*** Bug 82772 has been marked as a duplicate of this bug. ***
*** Bug 83466 has been marked as a duplicate of this bug. ***
*** Bug 84539 has been marked as a duplicate of this bug. ***
Warning: Changing to Standard Calendar file causes a core dump. Simply changing to vcs still doesn't work. I'm running KPilot 4.4.1 in KDE 3.2.3. My TZ is UTC+8 (Asia/Taipei). An 8pm appointment on Wednesday becomes a 4am appointment on Thursday. How you *really* work around this problem: 1. Open Korganizer. 2. Click Settings > Configure Korganizer. 3. Select "Time & Date" from the group selections on the left. 4. Select "[No selection]" from the Timezone: setting on the right. This has nothing to do with the system Timezone. It's a KDE-internal issue. Have fun!
Jeff Pitman's solution didn't work for me. (Was I suppose to start over with a fresh file?)
*** Bug 92262 has been marked as a duplicate of this bug. ***
Hm. Has anyone tried: - updating to the latest kpilot (4.5) and re-testing this, with the latest KDE (3.4)? - using an ics-file in korganizer and pointing the kpilot conduit to that file (as opposed to "standard resource")? I have the above setup and definitely do not see this.
It looks like there's been no update on this for 8 months now. It also looks like there are resolutions outside of kpilot that fix this problem? Is it okay to close this bug?
Jason 'vanRijn' Kasper schrieb: > It also looks like there are resolutions outside of kpilot that fix this problem? Hmm? I didn't notice, but OK, I didn't look so far because other things have been more important to me. > Is it okay to close this bug? It seems you have seen some solutions, so I guess it should be OK if you think it was. Friedemann
There have been major bug fixes in the korganizer conduit, in the libkcal libraries, and in korganizer that all can affect this bug. Since I can't reproduce this, I'm asking for help one last time from everyone who thinks that this is still a bug. Can you please update to the latest versions of kde and kpilot, etc. and try to reproduce this problem? It seemed that at one point, whether one used a vcf or ics file made a difference, but nobody has been able to narrow it down to that. I'm going to mark this as fixed. If anyone can reproduce this on the latest versions of software, _please_ re-open this and provide attachments/logs/screenshots/movies/music/something that can help us track this down. =:) Thanks.