alarms are shown one hour later

[jernst]

I'm using a Sony Ericsson W810 with irmc and evo plugins. In OpenSync? 0.20 and 0.21, alarms which are supposed to be shown 30 minutes before an event (as set in evolution) are shown 30 minutes after the event on my phone. I guess it's a timezone problem as I'm in GMT+1 but I'm not sure. The event start/end time are always correct though.

[cstender]

Please provide trace files, see http://www.opensync.org/wiki/tracing for more information. Do not use the OSYNC_PRIVACY function. If you don't want to publish them, please send me an email.

[hn75]

Hi

I have the same effect using syncml-obex-client (Nokia 3230) and kdepim-sync.

• From kdepim -> syncml the shift is -1h
• From syncml -> kdepim the shift is +2h

I attached the logs from a test creating a new event on the the phone and syncing to kdepim. I removed my sensitive data form the log file (Thread3082049216-9685.log). Hopefully you can still use them.

The syncml-obex-client.conf gives

<config>
<username></username>
<password></password>
<type>2</type>
<bluetooth_address>00:13:70:1A:8F:83</bluetooth_address>
<bluetooth_channel>11</bluetooth_channel>
<interface>0</interface>
<version>0</version>
<identifier>hendrik-0</identifier>
<wbxml>1</wbxml>
<recvLimit>0</recvLimit>
<maxObjSize>0</maxObjSize>
<usestringtable>0</usestringtable>
<onlyreplace>0</onlyreplace>
<contact_db>addressbook</contact_db>
<calendar_db>calendar</calendar_db>
<note_db>notes</note_db>
</config>

If you need more information I would be happy to supply them.

Thanks

[cstender]

There are no ALARM attributes in your trace files, so there is nothing which I can debug. Please provide correct trace files.

[hn75]

I see.

It is not the alarm time, but the times (begin an end time) of the entire _event_ is shifted. Which is much more annoying than the alarm time shift.

Thanks for quick response

Hendrik

[cstender]

This looks fine for me.

Input vcard: SUMMARY:Test 4^{M DTSTART:20070301T090000^M DTEND:20070301T100000^M}

Output vcard: SUMMARY:Test 4^{M DTSTART:20070301T090000^M DTEND:20070301T100000^M}

Maybe your Korganizer has a wrong timezone. Anyways, this bug is not about wrong DTSTART und DTEND values. Please open a new bug and assign it to dgollub if you can reproduce this with 0.22 (which will be released soon). Thanks.

I'm still waiting for the original trace files which show the alarm timeshift.

[jernst]

Sorry I didn't get an email notification that this bug has been updated...

Here are the traces. This bug is not the same as the one reported by hn75.

Alarm is set one hour before the appointment. Time zone is the same in the phone and evolution

[jernst]

requested trace

[jernst]

The alarm was set one hour before and has been received one hour after the appointment (i.e. two hours after it was supposed). When I oppened the bug I had only one hour difference ; I guess I got a second hour since we are now in summer time...

[cstender]

I'll look at it after we released 0.30.

[cstender]

Milestone 0.31 deleted

[cstender]

fixed with commit r2502