Bug 67088 - event alarm not synchronized to android calendar
Summary: event alarm not synchronized to android calendar
Status: RESOLVED NOTOURBUG
Alias: None
Product: SyncEvolution
Classification: Unclassified
Component: KDE (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: SyncEvolution Community
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-19 13:27 UTC by promeneur
Modified: 2013-07-19 15:34 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
log of sync of a test eventwith alarm (1.76 MB, text/html)
2013-07-19 14:52 UTC, promeneur
Details

Description promeneur 2013-07-19 13:27:02 UTC
syncevolution-kde 1.3.99.4-2

i create an event, a rendez-vous with korganizer with 3 alarms : 1 day, 2 and 1 hour before
then
i synchronise the calendars
then
in android calendar the events is created but without any alarm .

same pb with one alarm

with akonadi console i can check the alarms are there :

BEGIN:VALARM
DESCRIPTION:
ACTION:DISPLAY
TRIGGER;VALUE=DURATION:-P1D
X-KDE-KCALCORE-ENABLED:TRUE
END:VALARM
BEGIN:VALARM
DESCRIPTION:
ACTION:DISPLAY
TRIGGER;VALUE=DURATION:-PT2H
X-KDE-KCALCORE-ENABLED:TRUE
END:VALARM
BEGIN:VALARM
DESCRIPTION:
ACTION:DISPLAY
TRIGGER;VALUE=DURATION:-PT1H
X-KDE-KCALCORE-ENABLED:TRUE
END:VALARM
Comment 1 Patrick Ohly 2013-07-19 13:49:16 UTC
Who does SyncEvolution send the events to?

Run "syncevolution --run loglevel=4 <peer config name>" after creating a test event, then look into the syncevolution-log.html in ~/.cache/syncevolution to see whether the event was sent. Quote the part after "generated:" here or attach the entire log.

If SyncEvolution sends the alarms and they are correct, then it is up to the receiving end to do something useful with them.
Comment 2 promeneur 2013-07-19 14:35:38 UTC
>> Who does SyncEvolution send the events to?

sorry

syncevolution synchronizes with funambol


in "syncevolution --run loglevel=4 <peer config name>"

what is <peer config name> ?
Comment 3 promeneur 2013-07-19 14:52:12 UTC
Created attachment 82693 [details]
log  of sync of a test eventwith alarm

i created a "test" event with an alrme 1 hour before
Comment 4 Patrick Ohly 2013-07-19 15:00:42 UTC
(In reply to comment #3)
> Created attachment 82693 [details]
> log  of sync of a test eventwith alarm
> 
> i created a "test" event with an alrme 1 hour before

The log shows that this is being sent:

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Synthesis AG//NONSGML SyncML Engine V3.4.0.47//EN
BEGIN:VTIMEZONE
TZID:Europe/Paris
BEGIN:STANDARD
DTSTART:19671029T030000
RRULE:FREQ=MONTHLY;INTERVAL=12;BYDAY=-1SU
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19870329T020000
RRULE:FREQ=MONTHLY;INTERVAL=12;BYDAY=-1SU
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
LAST-MODIFIED:20130719T143603Z
DTSTAMP:20130719T143703Z
CREATED:20130719T143703Z
UID:ff3f30ef-a471-4435-823d-75dd7e28047c
CATEGORIES:Rendez-vous
TRANSP:OPAQUE
SUMMARY:Test
DESCRIPTION:Test
DTSTART;TZID=Europe/Paris:20130721T101500
DTEND;TZID=Europe/Paris:20130721T121500
ORGANIZER;CN=Philippe ROUBACH:mailto:philippe.roubach@free.fr
BEGIN:VALARM
TRIGGER;VALUE=DURATION:-PT1H
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR

Looks correct to me. Please report the problem to Funambol. They need to check how they handle such items and how they send it to the Android phone.

If they think that the problem is in SyncEvolution, then please report back and reopen this issue.
Comment 5 promeneur 2013-07-19 15:32:02 UTC
thanks

do you know if there is a bugzilla for funambol server 10.0.3.

i only found a mailing list funambol-discussions@lists.sourceforge.net
Comment 6 Patrick Ohly 2013-07-19 15:34:38 UTC
(In reply to comment #5)
> do you know if there is a bugzilla for funambol server 10.0.3.
> 
> i only found a mailing list funambol-discussions@lists.sourceforge.net

I don't know whether there still is a public bug tracker.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.