Ticket #567 (closed defect: worksforme)

Opened 4 years ago

Last modified 4 years ago

cannot sync calendar between nokia 5500 and evolution

Reported by: wrobell Owned by: cstender
Priority: normal Milestone: Plugin Format: vformat 0.40
Component: Format Plugin: vformat Version: 0.22
Severity: major Keywords:
Cc:

Description

i've configured opensync to sync calendar between nokia 5500 and evolution (disabled: contacts, todo).

i am getting segmentation fault at the end:

Synchronizing group "evo-n5500" 
Member 1 of type evo2-sync just connected
received event dsession
Member 2 of type syncml-obex-client just connected
All clients connected or error
Received an entry 20041028T133632Z-13707-1000-12602-15@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T133632Z-13707-1000-12602-27@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T133632Z-13707-1000-12602-5@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T133633Z-13707-1000-12602-32@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T133632Z-13707-1000-12602-17@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T133632Z-13707-1000-12602-29@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20070927T192051Z-18588-1000-1-7@borg with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T133632Z-13707-1000-12602-7@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an reply to our Alert
Going to receive 2 changes
Received an entry 20041028T133633Z-13707-1000-12602-34@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041122T133916Z-1507-1000-1505-5@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20060309T223518Z-4772-1000-4421-0@borg with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20060309T223917Z-4772-1000-4421-33@borg with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T133632Z-13707-1000-12602-19@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20070927T192051Z-18588-1000-1-9@borg with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T133632Z-13707-1000-12602-9@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T133632Z-13707-1000-12602-21@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T133633Z-13707-1000-12602-36@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20060309T223635Z-4772-1000-4421-4@borg with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20060309T222855Z-1467-1000-1-9@borg with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T133633Z-13707-1000-12602-37@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T133632Z-13707-1000-12602-11@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T133632Z-13707-1000-12602-23@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20070331T153436Z-4336-1000-1-26@borg with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T133633Z-13707-1000-12602-39@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T135831Z-14868-1000-8624-90@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041109T011403Z-13506-1000-3111-70@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T133632Z-13707-1000-12602-13@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T133632Z-13707-1000-12602-25@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T133632Z-13707-1000-12602-3@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041028T133633Z-13707-1000-12602-30@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20041106T144915Z-3104-1000-3102-3@pred with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Member 1 of type evo2-sync just sent all changes
Received an entry 6 with data of size 4 from member 2 (syncml-obex-client). Changetype ADDED
Received an entry 7 with data of size 4 from member 2 (syncml-obex-client). Changetype ADDED
Member 2 of type syncml-obex-client just sent all changes
All clients sent changes or error
All conflicts have been reported
Pipe closed! Exiting.
Pipe closed! Exiting.
zsh: segmentation fault  msynctool --sync evo-n5500

Attachments

Thread805441744.log Download (30.1 KB) - added by wrobell 4 years ago.
Thread830665904.log Download (89.0 KB) - added by wrobell 4 years ago.
opensync-alarm_trigger.patch Download (2.2 KB) - added by wrobell 4 years ago.
fix segfault when no alarm trigger specified

Change History

Changed 4 years ago by wrobell

Changed 4 years ago by wrobell

comment:1 Changed 4 years ago by dfriedrich

  • Status changed from new to closed
  • Resolution set to wontfix

please try opensync 0.3x and append also the OSYNC_TRACEs not only the SYNCML_TRACEs

comment:2 Changed 4 years ago by wrobell

  • Component changed from Plugin: evolution2 to OpenSync

there were no osync trace files.

cannot test with opensync 0.3x. no bluetooth, no evolution plugins :)

http://www.opensync.org/wiki/download

Warning''' the version number for the OpenSync core must match that of the plugins you want to use. This means that you shouldn't use OpenSync 0.31 (or any further 0.3x) just now, unless you want to develop or port the plugins yourself (see PluginPortingGuide-0.30).

i am changing to opensync component - see next comment for the reason.

comment:3 Changed 4 years ago by wrobell

backtrace

#0  0x0fef09c0 in osxml_get_node () from /usr/lib/libopensync.so.0
#1  0x0fef0b34 in osxml_find_node () from /usr/lib/libopensync.so.0
#2  0x0e664864 in ?? () from /usr/lib/opensync/formats/xml-vcal.so
#3  0x0e669a08 in xml_parse_attribute () from /usr/lib/opensync/formats/xml-vcal.so
#4  0x0e669770 in xml_parse_attribute () from /usr/lib/opensync/formats/xml-vcal.so
#5  0x0e669e74 in ?? () from /usr/lib/opensync/formats/xml-vcal.so
#6  0x0feeaedc in osync_converter_invoke () from /usr/lib/libopensync.so.0
#7  0x0feebbb4 in osync_conv_convert_fn () from /usr/lib/libopensync.so.0
#8  0x0feec458 in osync_change_convert_member_sink () from /usr/lib/libopensync.so.0
#9  0x0fea0148 in osync_client_commit_change () from /usr/lib/libosengine.so.0
#10 0x0fea919c in osengine_mappingentry_decider () from /usr/lib/libosengine.so.0
#11 0x0fea3be4 in ?? () from /usr/lib/libosengine.so.0
#12 0x0fef25dc in ?? () from /usr/lib/libopensync.so.0
#13 0x0ff47f7c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#14 0x0ff4bf20 in ?? () from /usr/lib/libglib-2.0.so.0
#15 0x0ff4c38c in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#16 0x0ff72c28 in ?? () from /usr/lib/libglib-2.0.so.0
#17 0x0fab4a10 in ?? () from /lib/libpthread.so.0
#18 0x0fe02eac in clone () from /lib/libc.so.6

comment:4 Changed 4 years ago by wrobell

  • Status changed from closed to reopened
  • Resolution wontfix deleted

i do not want to be rude, but i am reopening the bug, reasons

  • there are no required plugins to test the bug (irmc, evolution) for opensync 0.3x (according to download page 0.22 plugins are not compatible)
  • i've managed to prepare a patch, which prevents segfaulting opensync 0.22; i need probably bit more time to look around and make the patch better, so please give me some more time

please take into account that i would more than happy to test my configuration with opensync 0.3x, but it is not possible if i understand current opensync development status well.

Changed 4 years ago by wrobell

fix segfault when no alarm trigger specified

comment:5 Changed 4 years ago by wrobell

added a patch, seems to be ok for me. any comments?

comment:6 Changed 4 years ago by dfriedrich

please assign this patch to cstender; maybe he can take him to 0.30

comment:7 Changed 4 years ago by wrobell

  • Owner changed from abauer to cstender
  • Status changed from reopened to new

assigning to cstender as suggested by dfriedrich.

comment:8 Changed 4 years ago by cstender

  • Status changed from new to assigned
  • Component changed from OpenSync to Plugin: vformat

comment:9 Changed 4 years ago by cstender

Well, I need the complete trace files (not only the syncml traces). You cannot make the trigger value additional, because it is required in rfc2445 and vcal-1.0 spec. That's the reason why I cannot add your patch, sorry. Please attach full osync traces. Thanks.

comment:10 Changed 4 years ago by cstender

  • Milestone set to OpenSync 0.40

Argh, vcal-1.0 allows the following: AALARM;TYPE=WAVE;VALUE=URL:19960415T235959; ; ;  file:///mmedia/taps.wav AALARM;TYPE=WAVE;VALUE=CONTENT-ID:19960903T060000;PT15M;4;<jsmith.part2.=

960901T083000.xyzMail@…>

Your AALARM entry looks like this: AALARM;TYPE=X-EPOCSOUND:20070913T170000Z;;0;

So yes, this seems to be an opensync bug.

comment:11 Changed 4 years ago by cstender

  • Status changed from assigned to closed
  • Resolution set to worksforme

I can't reproduce your error.

Your vcal entry contains: AALARM;TYPE=X-EPOCSOUND:20070913T170000Z;;0;

which got converted to:

<Alarm>

<AlarmAction?>AUDIO</AlarmAction?> <AlarmTrigger?>

<Content>-PT2H30M</Content> <Value>DURATION</Value> <Related>START</Related>

</AlarmTrigger?> <UnknownParam?>X-EPOCSOUND<ParamName?>TYPE</ParamName?></UnknownParam?>

</Alarm>

Looks correct, but I'm not sure if the UnknownParam? can cause some trouble. Nevertheless with latest svn from 0.2x-branch I can't reproduce your segfault. If you can please reopen this bug and attach trace files (export OSYNC_TRACE=/tmp/bla). Thanks for your help.

Note: See TracTickets for help on using tickets.