Version: 4.4.0 (HEAD) (using KDE 3.2.0, (3.0)) Compiler: gcc version 2.95.4 20011002 (Debian prerelease) OS: Linux (i686) release 2.4.24 Syncing sony clie T615C using IR kernel 2.4.24, pilot-link 0.11.7 Worked fine til I upgrade to kde3.2 and got new version of kpilot (among other things!). After upgrade, when I do a "copy from handheld" sync with Korganizer via the vcal conduit, the event times are all 5 hours too early. For example, a 5pm event on my clie gets added to Korganizer calendar as a noon event. This feels like a timezone issue. I start with an empty Korganizer calendar (I create a new one, then save as ..., then make that the target in the vcal conduit under kpilot settings > configure conduits. In KDE Control Center, Preferences > System > Date & Time, my current time zone is EST. On my clie, my timezone is USA (Eastern). Where exactly does kpilot get its notion of timezone? I'm quite stuck on this. It makes kpilot -> korganizer essentially useless. Thanks.
I think the problem is that korganizer 3.2 now makes an attempt to store times in UTC. So, if my timezone is America/New_York, and I add a 1pm event, it gets stored in the .ics file not as 1300 but as 1800. The vcal conduit for kpilot takes a 1pm event from the handheld and adds it to the .ics file with a time of 1300. The workaround is to, within korganizer, select Settings > Configure Korganizer > click Time & Date > select [No selection] as the timezone.
I have a similar problem, except the difference is not always the 5 hours that my time zone would create, sometimes less, sometimes more. The given workaround, however, displays the appointments in the (assumedly) UTC times, shifting the display in KOrganizer to what had previously been synced to the palm pilot. (If it makes a difference, I copied an old korganizer file for use with the new version) This is a pretty disastrous bug in terms of the usefulness of this program, as already voiced by the poster.
Nevermind, the old calendar file was part of the problem, your fix works, and this shouldn't be too bad to implement in the conduit.
I've got one obvious guess where the problem lies - but I need someone with the problem to give the modified code a whirl. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAQ8v7dqzuAf6io/4RAixlAKCNxd3ozTgGFhgv7XRDeYAspIN3hQCfTj4k LAK4vwz2UmkvKvUvyQ64eUk= =ngyK -----END PGP SIGNATURE-----
Where's the patch? I could give it a go
I would also be happy to test out a patch for this problem.
On Saturday 20 March 2004 22:20, Andy Neitzke wrote: > ------- I would also be happy to test out a patch for this problem. OK, Lutz has a fix to libical (the underlying library that we use to store the calendar entries), but that's pretty complicated to drag in: it will probably require you to update at least someof your PIM applications to HEAD (not a bad thing, really, since PIM 3.3 is nearing). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAXLzHdqzuAf6io/4RAgTqAKCdXqJ13yHtfFLBR+HCPcNnGxsA3wCgowic N6w7ordnrd9U08yE+l9vD8Y= =yY90 -----END PGP SIGNATURE-----
Ok, I just commited my fix to 3_2 and to HEAD. This bug may be fixed. I did not get it to reproduce the bug with my Palm IIIc and SuSE 9.0 There are several ways the timezone settings are managed from the operating system itself (KDE-unrelated). It seems to be that my fix of the timezone problem is only relevant for systems using the environment variable TZ to store the timezone info. E.g. SuSE 9.0 does not. To all, who had problems with the timezone: Please open a shell and type there $TZ<return> and let us know what the output is. ( If there is any ). Lutz
That's "echo $TZ", there, Lutz. For people affected by this bug: since the fix is also in BRANCH, you can update just your copy of libical (kdepim/libical), remove any workaround, and see what happens.
Ok, "echo $TZ" is the better solution :-) libical is a static lib and is linked to libkcal. So you have to update your copy of libkcal.
I have an affected system (Mandrake Cooker) -- after I do a "copy to handheld" all times appear too late on the Pilot. Not all events are shifted by the same amount of time; the shift is either 4 or 5 hours (it seems like this could be related to daylight savings somehow, but curiously, there doesn't seem to be any obvious correlation between the shift and the date of the event.) My local time is US Eastern. On this system "echo $TZ" just prints a blank line. I haven't tried the fix yet.
I've updated to the latest Mandrake Cooker packages, which according to the changelog were sync'd with KDE_3_2_BRANCH around April 2, but I still have this problem. Is there anything I can do to help isolate it?
On Friday 16 April 2004 21:40, Andy Neitzke wrote: > ------- I've updated to the latest Mandrake Cooker packages, which > according to the changelog were sync'd with KDE_3_2_BRANCH around April 2, > but I still have this problem. Is there anything I can do to help isolate > it? The BRANCH doesn't get updated, unfortunately. To help isolate this, I'd suggest you either run KPilot's CVS HEAD (it's more stable than BRANCH, since that's where the bugs get fixed), or one of the tarballs from the KPilot site. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAgEoqdqzuAf6io/4RAsfIAJ0XyVnrq5pdHRESmdoBea3YO8e9DACePmDG 924FF9SQc+9UfOU0t+Zs/HU= =ZkPs -----END PGP SIGNATURE-----
Consolidating dupes, that's all. If Lutz' fix made it into KDE 3.2.2, then this one should be solved now. *** This bug has been marked as a duplicate of 67321 ***
I'm using KDE3.2.2 from Debian Unstable, and, well, if this fix went in it isn't working. Got bitten by it just now.
On 6 May 2004, Jan De Luyck wrote: > I'm using KDE3.2.2 from Debian Unstable, and, well, if this fix went in > it isn't working. Got bitten by it just now. I'm sorry, I just don't know. I've never been able to reproduce this problem, and the history of what went where in which version of (libs,pim,kpilot) is just too confusing to keep track of. As with lots of bugs, this one needs someone who (a) can reproduce it (b) cares enough to fix it.
I'm using KDEPIM 3.2.2 from Debian unstable as well, and I just found your workaround to be working with it. I'm using a Palm 105, and now that I unset the timezone on the korganizer, there's no more difference between original and PDA event times. $TZ is not used on my system.