{5} Assigned, Active Tickets by Owner (Full Description) (54 matches)

List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.

abauer

Ticket Summary Component Milestone Type Severity Created
Description
#251 feature request: Plaxo plugin Plugin: others enhancement minor 07/23/06

Hi! Great job so far! Synced KDE-Pim and my SE k750i flawlessly today using Jahn's binaries ( http://www.in.fh-merseburg.de/~jahn/ ) in Kubuntu dapper.

What would be nice is a sync plugin for Plaxo (www.plaxo.com). For a long time linux users complained on the plaxo forums for lack of linux support. Plaxo has added an extension for Thunderbird in the meantime.

Now it would be nice to have a Plaxo-plugin for opensync. This is what Plaxo says about it: PS: For you developers out there, note that we've released this toolbar under the Mozilla Public License, which means it's open source and you're free to tinker with it. To help facilitate, we've set up a developer area on the Plaxo forums. We're also actively working on an open API that will let anyone Plaxo-enable their favorite application, so stay tuned! (http://blog.plaxo.com/archives/2005/07/thunderbird_has.html)

Kind regards LeSid?

#142 Add encoding configuration for the file-sync plugin Plugin: file-sync 0.40 defect normal 01/22/06

There seems to be no way of configuring the file encoding of the files used by the file-sync plugin.

#196 SyncML plugin should obey devinf Plugin: syncml defect normal 06/01/06

For correct SyncML behavior the plugin should obey the devinf. As I understand this requires the following things to be implemented:

1) Store the devinf somewhere.

As the device may only send it's devinf in the first session it has to be stored somewhere. Maybe the opensyc engine should provide a common functionality for that.

2) Pass the devinf to smlDevInfConfigureSession

3) Truncate the uid's which are sent to the device if necessary (MaxGUIDSize).

4) Filter vcard/vcal attributes according to <CTCap> entries.

The actual filtering should not be done by the SyncML plugin. Maybe the common formats could register filter functions. The syncml plugin could then create appropriate filters and pass the <CTCap> data as config to the filter functions.

Is there any way I could help efficiently to accomplish that?

#78 Implement a hashing function for get_info information OpenSync enhancement minor 04/14/05

4. Cache the information. Use a make like system where you compare the timestamp of the script file with the cached data. This doesn't solve the error bit but it saves you the loading of the interpreter.

I also like #4. We could keep the get_info function for scripts as it is at the moment, and just call it if the hash of the script object has changed (we could easily use the exisiting hashtable system of opensync for this). The only difference would be that the first time the script is installed (or altered), the plugin-listing would be slower.

If we provide a utility for rebuilding the cache, it can be run by the installer script for the plugin, so we can avoid the slowdown on the first time. And we may make running this script recommended, but not required, because we will validate the cache when loading the scripts, anyway.

yes. thats a very good idea!

the tool would be very simple to write. The only parameter it would need is the filename of the script plugin. It would the initialize its OSyncEnv with LOAD_PLUGINS = FALSE and load the given plugin using osync_module_load. that would work for both sync plugins and format plugins.

so... what shall it be? 3 or 4?

#96 Add install documentation to README or INSTALL files OpenSync 0.37 defect minor 08/26/05

install instructions should be included both for a downloaded package and for code checked out from the repository.

#130 Sync all evo calendars at once Plugin: evolution2 enhancement minor 11/21/05

Just a thought.. would it make sense to allow an option to syncronize all the calendars in evolution as a single global calendar? Most handsets support a single calendar, but evolution allows splitting events in more categories, and it is currently impossible to syncronize all the entries. Events created on the handsets may be synced with a default category in evolution.

#137 Please, enhace the file plugin to use ssh and ftp Plugin: file-sync enhancement minor 01/04/06

Can enhace anyone the "file plugin" to sync not only local files but foreing files using ssh or ftp?

#17 Add permission and ownership for file-sync plugin Plugin: file-sync enhancement normal 02/05/05
#143 Improving osync_trace performance OpenSync 0.38 enhancement normal 01/25/06

Reading the code, il seems that osync_trace will check environment every time it's called.

I suspect this is not optimal...

Maybe a pre-initialised func pointer (either directed to an already prepared trace function, or an empty stub if tracing is disabled in current execution environment) might be better.

Just in case someone would like to test that and performance impact...

My 2 cents.

#173 Add support for perl plugins Plugin: others enhancement normal 04/21/06

OpenSync? could be even more open if you were able to run your own program(s) when syncing. Or in other words : I don't care about C and performances, please provide me a mean to write shell / perl scripts to sync my devices/files/whatever.

To give a concrete example of the problem : the only tool able to commnicate with my Nokia 3100 is "gammu". Its output is parsable but is far from being a XML file (more like a text file) and it would be really easier and more flexible if it could be parsed through perl.

To have this feature, I think someone should write a plugin which purpose is to call external programs whenever possible and its configuration file being those external programs.

#208 kdepim should allow control over which resources are synchronised Plugin: kdepim 0.40 enhancement normal 06/16/06

It would be useful if the kdepim plugin allowed control over which resources were synchronised. Three distinct features would be useful:

1) The ability to limit synchronisation to certain types of objects: events, todos, notes, contacts or whatever.

2) The ability to specify which resources are to be synchronised. I use several different contact resources which I would like to keep synchronised with different Exchange contacts folders. Also I only want to synchronise some of these to my phone (as it has limited space and poor lookup -- I don't want every business card I have ever scanned to be synchronised to my phone).

3) The ability to specify which resource would be used to create new items. I would use this as part of synchronising my different contact resources with different Exchange folders.

I would be happy to assist in developing these features. I have looked at the KCal::CalendarResources? class documentation but I am still confused about how to handle multiple resources.

Of course, this would also require the addition of a configuration capability to the kdepim plugin.

Graham Cobb (email: g+opensync AT cobb.uk.net)

andrewb

Ticket Summary Component Milestone Type Severity Created
Description
#639 moto-sync scrambles event descriptions and locations Plugin: moto 0.40 defect major 12/02/07

As the summary says, the current HEAD of moto-sync scrambles event descriptions and event locations. There seems to be a problem with the way moto-sync writes stores events on the phone. moto-sync's AT-Command passes the event summaries in a hexadecimal encoding, while the desciptions and locations (basically all other strings) are passed as quoted strings. It seems like my phone (v3xx) is not capable of handling these two variants of strings and interpretes all strings as if they were hex encoded. The responsible lines for this are 941-943 in motosync.py: 

# HACK: only the name of the event (data[1]) should be unicode
for n in range(2, len(data)):
  if type(data[n]) == types.UnicodeType:
    data[n] = data[n].encode('ascii')

Looks like there is a reason why, the other fields are not encoded, but i don't know why. After removing the for-loop everything worked flawlessly. So far i've extensivley tested adding and removing events as well as modifying various fields of events (syncing against file-sync). And everything works fine. All issues from ticket 523 seem to be fixed.

#533 bug reading phone book entries where the entry's name contains a \n Plugin: moto 0.40 defect normal 08/08/07

After bug #531 seems to be fixed I tried to sync the V3i again and now I run into another bug. It seems that moto get all changes but isn't able to commit them to the engine.

[1186561183.788550] [SENSITIVE] <-- OK [1186561183.792043] >>>>>>> osync_context_report_osyncerror(0x8149980, 0x8146ee0:(Traceback (most recent call last):

File "/usr/lib/opensync/python-plugins/motosync.py", line 2272, in get_changes

for change in self.access.list_changes(self.objtype):

File "/usr/lib/opensync/python-plugins/motosync.py", line 2101, in list_changes

entries = [PhoneContactMoto?(d) for d in self.comms.read_contacts()]

File "/usr/lib/opensync/python-plugins/motosync.py", line 1016, in read_contacts

ret.extend(self.parse_results('MPBR', data))

File "/usr/lib/opensync/python-plugins/motosync.py", line 1117, in parse_results

assert(part[-1] == '"')

AssertionError? ))

#562 at+mode=2 stops the cell from reacting any more Plugin: moto defect normal 09/13/07

Just playing with trunk and found out the following.

Doing two msynctools --discover the second hangs at AT&F. This is caused by 

        self.__do_cmd('AT+MODE=2') # change mode again
        line = self.__readline()   # swallow the "+MBAN" output that MODE=2 generates
        assert(line.startswith('+MBAN:'), "Unexpected output after AT+MODE=2: " + line)

Removing the block above solves the problem. Otherwise I know no other way then reattaching the phone. (RazrV3xv)

bellmich

Ticket Summary Component Milestone Type Severity Created
Description
#679 syncml-obex-client fails with a Nokia phone fails with Forbidden (0x43) Plugin: syncml defect major 02/09/08

Trying to sync the phone via Obex (USB Cable) fails with Nokia phone fails with Forbidden (0x43). 

Synchronizing group "cable2pim"
The previous synchronization was unclean. Slow-syncing
contact sink of member 1 of type syncml-obex-client just connected
contact sink of member 2 of type kdepim-sync just connected
Main sink of member 2 of type kdepim-sync just connected
Main sink of member 1 of type syncml-obex-client just connected
All clients connected or error
Main sink of member 1 of type syncml-obex-client just sent all changes

Then, the local DB (KDE Pim) sends all changes, but the phone doesn't.

Afterwards, msynctool just hangs after displaying the following message: 

contact sink of member 2 of type kdepim-sync just sent all changes
Main sink of member 2 of type kdepim-sync just sent all changes

At this time, the phone displays Sync complete, just as if everything was successful, but it isn't: neither changes from the phone to kaddressbook are performed, nor the other way round

#771 Unable to sync with Nokia E65 (software 2.0633.65.01) OpenSync 0.40 defect blocker 07/04/08

Hi

I can't sync my Nokia E65 with opensync. I've tried lots of versions of opensync but it's always the same : unable to sync.

Everytime I tried I got an error: 

Received an transport error: Forbidden (0x43)

I'm using Debian, here is the installed version: 

libopensync0                                   0.22-2
libsyncml-utils                                0.4.6-3
libsyncml0                                     0.4.6-3
multisync-tools                                0.92.0~svn355-1
opensync-plugin-file                           0.22-2
opensync-plugin-syncml                         0.22-2

Here is a trace of the "syncml-obex-client" command: 

syncml-obex-client -b XX:XX:XX:XX:XX:XX 14 --dumpinfo --slow-sync text/x-vcard Contacts --wbxml --identifier "PC Suite" --useStringTable
connection with device succeeded
Received an Alert for the DS Server at Contacts: Type: 201, Last , Next 20080704T085502Z
Slowsyncing
Just received a new session with ID 1
Received the DevInf
Session 1 reported final. flushing
Received an transport error: Forbidden (0x43)
Send the output below to the libsyncml developers

========================================
Man: NOKIA
Mod: E65
FirmwareVersion:
SoftwareVersion: 2.0633.65.01
HardwareVersion:

ReceiveLimit: 0
MaxObjSize: 0
Connection used: OBEX Client
Identifier: PC Suite

Databases:
DB Locations: Contacts
DB Type: text/x-vcard
DB Slow: 1

Bluetooth: Yes
Wbxml: Yes
SyncML Version: 1.1
SupportsNumberofChanges: Yes
SupportsLargeObjects: Yes

What can I do? I've tried with unstable version of Debian (0.36), it's the same.

I think Nokia Software version is too up-to-date for opensync...

cstender

Ticket Summary Component Milestone Type Severity Created
Description
#675 XML formats do not distinguish between voice and fax numbers Plugin: vformat 0.40 defect normal 02/01/08

This problem was discovered with recent SVN versions of Opensync 0.3x during development of the SynCE plugin for WM5 and above.

Conversion path: Evo2 plugin -> vformat -> xml-doc

If an entry is created in the Evolution addressbook filling, for example the 'Business Phone' and 'Business Fax' field, there is no way to distinguish between the voice and fax numbers in the resulting XML. See below:

Evolution: The following fields were filled:

Business phone: '0116 workphone' Home phone: '0116 homephone' Mobile phone: '0116 cellphone' Business fax: '0116 workfax'

The important part of the XML at the output is: 

  <Telephone UI-Slot="4" Location="Work">
    <Content>0116 Workfax</Content>
  </Telephone>
  <Telephone UI-Slot="3" Type="Cellular">
    <Content>0116 cellphone</Content>
  </Telephone>
  <Telephone UI-Slot="2" Location="Home">
    <Content>0116 homephone</Content>
  </Telephone>
  <Telephone UI-Slot="1" Location="Work">
    <Content>0116 workphone</Content>
  </Telephone>

This is ambiguous - I can't convert this to Airsync reliably as I can not discriminate between phone and fax. Suggest that the 'Type' attribute is filled appropriately for all 'Telephone' elements.

#678 Event recurrences report schema errors Plugin: vformat 0.40 defect normal 02/07/08

Testing GPE synchronisation, using the SVN 0.3x source, I get the following errors appearing during the sync:

element Until: Schemas validity error : Element 'Until': This element is not expected. Expected is ( Frequency ). element Count: Schemas validity error : Element 'Count': This element is not expected. Expected is ( Frequency ). element Until: Schemas validity error : Element 'Until': This element is not expected. Expected is ( Frequency ).

The log file shows that there are two records which contain <Until>. Here is the relevant part of one of them:

<RecurrenceRule?>

<Frequency>YEARLY</Frequency> <Until>20301231</Until> <Interval>1</Interval>

</RecurrenceRule>

There are several which contain <Count>. I did note that only one of them also contains <Frequency>YEARLY, although I can't be sure this is the one causing the error:

<RecurrenceRule?>

<Frequency>YEARLY</Frequency> <Count>0</Count> <Interval>1</Interval>

</RecurrenceRule>

Note that gpe-sync does not provide any schemas of its own.

#361 Converting ALARM between iCalendar and vCalendar (was: Alarm notification not synchronized from Evo to SyncML) Plugin: vformat 0.40 defect normal 10/15/06

The 15-min alarm event is not transferred between Evo and SyncML client. The other direction is working correctly. It seems that it has something to do with the VALARM and DALARM. I'm attaching both traces:

1. traces from Evo to Nokia 6234 (SyncML client)

2. traces from Nokia 6234 to Evo (updating the same event with the alarm notification changed/set)

#684 element Count: Schemas validity error : Element 'Count': This element is not expected. Expected is ( Frequency ). Plugin: vformat 0.40 defect normal 02/13/08

Hi! I get this error when syncing with my nokia e51:

element Count: Schemas validity error : Element 'Count': This element is not expected. Expected is ( Frequency ).

The vevent is (sensitive information modified, but nothing else), from the file-sync local storage: 

BEGIN:VCALENDAR
PRODID:-//OpenSync//NONSGML OpenSync vformat 0.3//EN
VERSION:2.0
BEGIN:VEVENT
CLASS:PRIVATE
DTEND:20060613T220000Z
DTSTART:20060613T220000Z
LAST-MODIFIED:20080207T145019Z
PRIORITY:0
RRULE:COUNT=0;INTERVAL=1
SEQUENCE:0
SUMMARY:Foo
UID:07022008145019137375-0
END:VEVENT
END:VCALENDAR

See also discussion at: http://thread.gmane.org/gmane.comp.misc.opensync.user/2453/focus=2455

Note that I don't get the same vevent card from the phone if I sync with 'vevent10' instead of 'vevent20'. Is this a problem in the phone? If I sync using vevent20 type in the syncml-obex-client configuration, I get the following vevent card (for same instance): 

BEGIN:VCALENDAR

PRODID:-//OpenSync//NONSGML OpenSync vformat 0.3//EN

VERSION:2.0

BEGIN:VEVENT

CLASS:PRIVATE

DTEND:20060613T220000Z

DTSTART:20060613T220000Z

LAST-MODIFIED:20080207T145019Z

PRIORITY:0

RRULE:FREQ=YEARLY;UNTIL=21000613T0000-1Z;INTERVAL=1;BYMONTH=6

SEQUENCE:0

SUMMARY:Foo
UID:07022008145019137375-0

END:VEVENT

END:VCALENDAR

Thanks, Simon

#202 kdepim-plugin should synchronize journal entries Plugin: vformat 0.40 enhancement normal 06/08/06

It seems that korganizer journal entries, which are stored in the calendar file as VJOURNAL entries are not synchronized.

I am running the Mathias Jahn debian packages 0.18+svn20060604 I am using one kdepim-sync plugin and one file-sync plugin. The file-sync plugin lives on a sshfs file system, although I don't think that is relevant (other things seem to sync fine to sshfs directory)

#341 RELATED-TO not synced for TODOs kdepim->file Plugin: vformat 0.40 enhancement normal 09/29/06

I am doing a sync using msynctool from kdepim to a filesync

I set the parent of a todo in korganizer, and invoke msynctool.

I see the event sent from kdepim and to filesync as modified. I check the modification time of the file in the filesync directory, and it has been written out, but there is no RELATED-TO entry. In fact, there are no RELATED-TO entries at all.

Is this implemented?

I am using debian packages 0.19+svn20060911-1

#394 irmc <-> evolution mix phone types Plugin: vformat 0.40 defect normal 12/15/06

From (https://bugzilla.novell.com/show_bug.cgi?id=219117)

"It totally mixes phone type, probably depending on existing entries. E. g. if work phone is missing, phone Home phone is synced as evo Work. If all phones are filled, phone Other phone is synced as evo Other fax etc."

#456 Ability to sync Kontact Categories into Nokia Groups Plugin: vformat enhancement normal 03/06/07

Say I have a Family or Work or Business or Friends Category in KDE Kontact, I would like opensync to sync these into my Nokia N73 Symbian phone as Groups.

#462 add workarounds for all-day-events in vcalendar Plugin: vformat defect normal 03/15/07

We need workarounds for cellphones which use the vcalendar standard. Sadly, there is no spec or rfc which describe how to implement all-day-events in vcalendar. We figured out that e.g. Sony Ericsson use YYYYMMDDT000000Z - YYYYMMDDT235900Z for this kind of events. We need to know how other vendors do it with there cellphones and than use capabilities to workaround it.

#506 kdepim-sync plugin: conflicts, duplicate events Plugin: vformat 0.40 defect normal 06/16/07

When synchronizing a small KDE-calendar with only one test-event with only a date and no time specified, opensync always reports a conflict when syncing with the file-sync plugin using --slow-sync.

On the second sync run, the two sides differ in <DateCalendarCreated?>. Additionally <DateStarted?> and <DateEnd?> contain only the date on KDE-side (<Content>20070616</Content>) and the date and time on the filesync-side (<Content>20070615T000000</Content> for <DateStarted?> and <Content>20070615T235900</Content> for <DateEnd?>).

If I select "Duplicate", it adds a new entry on both sides, of course. On the third sync, it reports a conflict between the duped events. Those events differ in <DateCalendarCreated?> but the <DateStarted?> and <DateEnd?> times now contain a trailing Z on one side (e.g. 20070615T000000 vs 20070615T000000Z).

Trace-files and sync-output:

Initial sync Second (slow) sync Third (slow) sync

file-sync output

KDE calendar-file

Opensync-config

#590 Schemas validity error (StatusValue is not allowed to be 'NEEDS ACTION') Plugin: vformat 0.40 defect normal 10/30/07

While synchronizing a Nokia E50 with Google calendar, I get some of these:

element Content: Schemas validity error : Element 'Content': 'NEEDS ACTION' is not a valid value of the atomic type 'StatusValue?'. Received a entry 33 from member 2 (syncml-obex-client). Changetype ADDED element Content: Schemas validity error : Element 'Content': [facet 'enumeration'] The value 'NEEDS ACTION' is not an element of the set {'TENTATIVE', 'CONFIRMED', 'CANCELLED'}. element Content: Schemas validity error : Element 'Content': 'NEEDS ACTION' is not a valid value of the atomic type 'StatusValue?'.

I am currently running this:

msynctool --sync sync_svn --conflict 2

msynctool is on revision 339. libsyncml is on revision 259. google-calendar is on revision 2691. vformat is on revision 2691. opensync is on revision 2691.

#637 DAYLIGHT lines in calendar entries fail with a Nokia E65 Plugin: vformat defect normal 11/26/07

My Nokia E65 gives me calendar entries with multiple DAYLIGHT lines for repeated appointments when I sync it to files. These entries cannot be synced back to the phone. 

:; cat ~/etc/NokiaE65/opensync/Calendar/427
BEGIN:VCALENDAR
VERSION:1.0
TZ:+01
DAYLIGHT:TRUE
DAYLIGHT:TRUE
DAYLIGHT:TRUE
DAYLIGHT:TRUE
DAYLIGHT:TRUE
BEGIN:VEVENT
SUMMARY:14 juillet
DTSTART:20060714T070000Z
DTEND:20060714T070000Z
CLASS:PUBLIC
SEQUENCE:0
RRULE:YM1 7 #0
LAST-MODIFIED:20071125T210216Z
PRIORITY:0
END:VEVENT
END:VCALENDAR
:; msynctool --sync NokiaE65Calendar_file  
Synchronizing group "NokiaE65Calendar_file" 
Member 1 of type file-sync just connected
received event dsession
Member 2 of type syncml-obex-client just connected
All clients connected or error
Received an entry 427 with data of size 4 from member 1 (file-sync). Changetype ADDED
Member 1 of type file-sync just sent all changes
Received an reply to our Alert
Going to receive 0 changes
Member 2 of type syncml-obex-client just sent all changes
All clients sent changes or error
All conflicts have been reported
Member 1 of type file-sync committed all changes.
Received an reply to our sync
Error writing entry 427 to member 2 (syncml-obex-client): Unable to commit change. Error 500
Mapping Write Error: Unable to commit change. Error 500
Member 2 of type syncml-obex-client committed all changes.
All clients have written
Member 1 of type file-sync just disconnected
Member 2 of type syncml-obex-client just disconnected
All clients have disconnected
The sync failed: Unable to write one or more objects
Error while synchronizing: Unable to write one or more objects

:; cat ~/etc/NokiaE65/opensync/Calendar/427
BEGIN:VCALENDAR
VERSION:1.0
TZ:+01
DAYLIGHT:TRUE
BEGIN:VEVENT
SUMMARY:14 juillet
DTSTART:20060714T070000Z
DTEND:20060714T070000Z
CLASS:PUBLIC
SEQUENCE:0
RRULE:YM1 7 #0
LAST-MODIFIED:20071125T210216Z
PRIORITY:0
END:VEVENT
END:VCALENDAR
:; msynctool --sync NokiaE65Calendar_file  
Synchronizing group "NokiaE65Calendar_file" 
Member 1 of type file-sync just connected
received event dsession
Member 2 of type syncml-obex-client just connected
All clients connected or error
Received an entry 427 with data of size 4 from member 1 (file-sync). Changetype MODIFIED
Member 1 of type file-sync just sent all changes
Received an reply to our Alert
Going to receive 0 changes
Member 2 of type syncml-obex-client just sent all changes
All clients sent changes or error
All conflicts have been reported
Member 1 of type file-sync committed all changes.
Received an reply to our sync
Error writing entry 427 to member 2 (syncml-obex-client): Unable to commit change. Error 500
Mapping Write Error: Unable to commit change. Error 500
Member 2 of type syncml-obex-client committed all changes.
All clients have written
Member 1 of type file-sync just disconnected
Member 2 of type syncml-obex-client just disconnected
All clients have disconnected
The sync failed: Unable to write one or more objects
Error while synchronizing: Unable to write one or more objects

:; cat ~/etc/NokiaE65/opensync/Calendar/427
BEGIN:VCALENDAR
VERSION:1.0
TZ:+01
BEGIN:VEVENT
SUMMARY:14 juillet
DTSTART:20060714T070000Z
DTEND:20060714T070000Z
CLASS:PUBLIC
SEQUENCE:0
RRULE:YM1 7 #0
LAST-MODIFIED:20071125T210216Z
PRIORITY:0
END:VEVENT
END:VCALENDAR
:; msynctool --sync NokiaE65Calendar_file  
Synchronizing group "NokiaE65Calendar_file" 
Member 1 of type file-sync just connected
received event dsession
Member 2 of type syncml-obex-client just connected
All clients connected or error
Received an entry 427 with data of size 4 from member 1 (file-sync). Changetype MODIFIED
Member 1 of type file-sync just sent all changes
Received an reply to our Alert
Going to receive 0 changes
Member 2 of type syncml-obex-client just sent all changes
All clients sent changes or error
All conflicts have been reported
Member 1 of type file-sync committed all changes.
Received an reply to our sync
Sent an entry 427 of size 235 to member 2 (syncml-obex-client). Changetype MODIFIED
Member 2 of type syncml-obex-client committed all changes.
All clients have written
Member 1 of type file-sync just disconnected
Member 2 of type syncml-obex-client just disconnected
All clients have disconnected
The sync was successful
#644 kdepim-sync does not write formatted name (FN) corretly (using irmc-sync at other end) Plugin: vformat 0.40 defect normal 12/07/07

If I add new contacts on my mobile that have only one name, then the formatted name field is empty after syncing to kontact. I think this should be generated.

I'm using the trunk version of today.

#645 evo2-sync: element Note: Schemas validity error : Element 'Note': This element is not expected Plugin: vformat 0.40 defect normal 12/09/07

Hello, I'm trying to sync my Nokia E65 contacts with evolution and I get the message "element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone )."

When I run evolution it indicates that I have the correct number of contacts but they are all empty. Running strings(1) on addressbook.db seems to show lots of empty entries.

I have the traces if required. Am I wasting my time with 0.34? Should I try the SVN version directly? 

:; OSYNC_TRACE=/tmp/trace msynctool034 --sync Evolution034
Synchronizing group "Evolution034" 
Main sink of member 2 of type syncml-obex-client just connected
contact sink of member 1 of type evo2-sync just connected
Main sink of member 1 of type evo2-sync just connected
contact sink of member 2 of type syncml-obex-client just connected
All clients connected or error
contact sink of member 1 of type evo2-sync just sent all changes
Main sink of member 1 of type evo2-sync just sent all changes
Main sink of member 2 of type syncml-obex-client just sent all changes
Going to receive 168 changes
Received a entry 1 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 2 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 5 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 6 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 7 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 8 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 9 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 10 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 11 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 12 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 13 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 15 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 16 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 17 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 18 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 19 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 20 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 21 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 22 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 23 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 24 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 25 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 26 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 27 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 28 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 29 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 30 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 31 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 32 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 33 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 34 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 35 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 36 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 37 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 38 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 39 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 40 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 42 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 43 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 44 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 45 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 46 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 47 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 48 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 49 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 50 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 51 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 52 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 53 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 54 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 55 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 56 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 57 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 58 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 59 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 60 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 61 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 62 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 63 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 64 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 65 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 66 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 67 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 68 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 69 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 70 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 71 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 72 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 73 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 74 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 75 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 76 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 77 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 78 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 79 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 80 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 81 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 82 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 83 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 84 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 85 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 86 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 88 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 89 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 90 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 91 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 92 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 93 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 94 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 95 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 96 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 97 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 98 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 99 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 100 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 101 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 102 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 103 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 104 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 105 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 106 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 108 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 109 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 110 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 111 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 112 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 113 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 114 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 115 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 116 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 117 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 119 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 120 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 121 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 122 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 123 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 124 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 125 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 126 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 127 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 128 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 129 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 130 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 131 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 132 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 134 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 135 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 136 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 137 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 141 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 142 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 143 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 144 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 145 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 146 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 148 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 149 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 151 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 153 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 154 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 155 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 156 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 157 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 158 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 160 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 161 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 162 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 163 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 164 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 166 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 167 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 169 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 170 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 173 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 174 from member 2 (syncml-obex-client). Changetype ADDED
element Note: Schemas validity error : Element 'Note': This element is not expected. Expected is one of ( Organization, Photo, PhotoUrl, Profession, Revision, Role, SMS, Sound, Spouse, Telephone ).
Received a entry 175 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 178 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 180 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 182 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 183 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 184 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 185 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 186 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 188 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 189 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 190 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 192 from member 2 (syncml-obex-client). Changetype ADDED
Received a entry 193 from member 2 (syncml-obex-client). Changetype ADDED
contact sink of member 2 of type syncml-obex-client just sent all changes
All clients sent changes or error
All conflicts have been reported
Main sink of member 2 of type syncml-obex-client committed all changes.
Sent a entry pas-id-475BC46300000000 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000001 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000002 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000003 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000004 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000005 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000006 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000007 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000008 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000009 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4630000000A to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4630000000B to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4630000000C to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4630000000D to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4630000000E to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4630000000F to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000010 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000011 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000012 to member 1 (evo2-sync). Changetype ADDED
Received an reply to our sync
Sent a entry pas-id-475BC46300000013 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000014 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000015 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000016 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000017 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000018 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000019 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4630000001A to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4630000001B to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4630000001C to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4630000001D to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4630000001E to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4630000001F to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000020 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000021 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46300000022 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000023 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000024 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000025 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000026 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000027 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000028 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000029 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000002A to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000002B to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000002C to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000002D to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000002E to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000002F to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000030 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000031 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000032 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000033 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000034 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000035 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000036 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000037 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000038 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000039 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000003A to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000003B to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000003C to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000003D to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000003E to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000003F to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000040 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000041 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000042 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000043 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000044 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000045 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000046 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000047 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000048 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000049 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000004A to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000004B to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000004C to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000004D to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000004E to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000004F to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000050 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000051 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000052 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000053 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000054 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000055 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000056 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000057 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000058 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000059 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000005A to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000005B to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000005C to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000005D to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000005E to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000005F to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000060 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000061 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000062 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000063 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000064 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000065 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000066 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000067 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000068 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000069 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000006A to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000006B to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000006C to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000006D to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000006E to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000006F to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000070 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000071 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000072 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000073 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000074 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000075 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000076 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000077 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000078 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000079 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000007A to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000007B to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000007C to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000007D to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000007E to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000007F to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000080 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000081 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000082 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000083 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000084 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000085 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000086 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000087 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000088 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000089 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000008A to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000008B to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000008C to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000008D to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000008E to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4640000008F to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000090 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000091 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000092 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46400000093 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46500000094 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46500000095 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46500000096 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46500000097 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46500000098 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC46500000099 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4650000009A to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4650000009B to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4650000009C to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4650000009D to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4650000009E to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC4650000009F to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC465000000A0 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC465000000A1 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC465000000A2 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC465000000A3 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC465000000A4 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC465000000A5 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC465000000A6 to member 1 (evo2-sync). Changetype ADDED
Sent a entry pas-id-475BC465000000A7 to member 1 (evo2-sync). Changetype ADDED
contact sink of member 1 of type evo2-sync committed all changes.
Main sink of member 1 of type evo2-sync committed all changes.
contact sink of member 2 of type syncml-obex-client committed all changes.
All clients have written
contact sink of member 2 of type syncml-obex-client reported sync done.
Main sink of member 2 of type syncml-obex-client reported sync done.
contact sink of member 1 of type evo2-sync reported sync done.
Main sink of member 1 of type evo2-sync reported sync done.
All clients reported sync done
contact sink of member 1 of type evo2-sync just disconnected
Main sink of member 1 of type evo2-sync just disconnected
contact sink of member 2 of type syncml-obex-client just disconnected
Main sink of member 2 of type syncml-obex-client just disconnected
All clients have disconnected
The sync was successful

:; msynctool034 --showgroup  Evolution034
Group: Evolution034
Member 1: evo2-sync
        Configuration : <?xml version="1.0"?>
<config>
  <address_path>file:///home/stuart/.evolution/addressbook/local/system</address_path>
  <calendar_path>file:///home/stuart/.evolution/calendar/local/system</calendar_path>
  <tasks_path>file:///home/stuart/.evolution/tasks/local/system</tasks_path>
</config>

Member 2: syncml-obex-client
        Configuration : <?xml version="1.0"?>
<config>
  <!-- (Only for bluetooth) The bluetooth address if the bluetooth mode is selected -->
  <bluetooth_address>xx:xx:xx:xx:xx:xx</bluetooth_address>
  <!-- (Only for bluetooth) The bluetooth channel to use. `sdptool browse $MAC` to search for the correct channel -->
  <bluetooth_channel>14</bluetooth_channel>
  <!-- (Only for USB) The usb interface number of the SYNCML-SYNC target. use syncml-obex-client -u (you will need access to the USB raw device) to find it. -->
  <interface>0</interface>
  <!-- The string that the plugin will use to identify itself. Some devices need a special string here. -->
  <identifier>Evolution034</identifier>
  <!-- The syncml version to use: 0 for 1.0, 1 for 1.1 and 2 for 1.2 -->
  <version>1</version>
  <!-- if the plugin should use wbxml -->
  <wbxml>1</wbxml>
  <!-- The username to use. Leave empty to not require a username -->
  <username></username>
  <!-- the password for the username -->
  <password></password>
  <!-- sets the connection type to use. 5 means obex over usb, 2 means obex over bluetooth -->
  <type>2</type>
  <!-- If wbxml is enabled, defines wether the wbxml should use string tables -->
  <usestringtable>0</usestringtable>
  <!-- Never send ADD command, but send REPLACE (not needed normally) -->
  <onlyreplace>0</onlyreplace>
  <!-- Workaround around for mobile phones which only use local timestamps and _no_ UTC timestamps! -->
  <onlyLocaltime>0</onlyLocaltime>
  <!-- Sets the maximum allowed size in bytes of incoming messages (some device need this option set). Example: 10000 -->
  <recvLimit>10000</recvLimit>
  <maxObjSize>0</maxObjSize>
  <database>
     <name>Contacts</name>
     <objtype>contact</objtype>
     <objformat>vcard21</objformat>
  </database>
</config>
#670 Fix dead loop in vformat Plugin: vformat 0.40 task normal 01/22/08

A wrong formatted vcard can cause a dead loop in vformat. 

BEGIN:VCARD
VERSION:2.1
N:Blub;Bla
FN:Bla Blub
ATTENDEE;ROLE=ATTENDEE;STATUS=NEEDS
ACTION;RSVP=YES;EXPECT=FYI;X-ROLE=REQ-PARTICIPANT;X-STATUS=NEEDS-ACTION:MyName
END:VCARD
#683 element Url: Schemas validity error : Element 'Url', attribute 'Location': The attribute 'Location' is not allowed. Plugin: vformat 0.40 defect normal 02/13/08

Hi! I get this error when syncing with my nokia e51:

element Url: Schemas validity error : Element 'Url', attribute 'Location': The attribute 'Location' is not allowed.

The vcard is (sensitive information modified, but nothing else): 

BEGIN:VCARD
VERSION:3.0
N:Foo;Bar;;;
REV:20080207T183307Z
TEL:123
URL;TYPE=HOME:http://example.org/
END:VCARD

See also discussion at: http://thread.gmane.org/gmane.comp.misc.opensync.user/2453/focus=2455

Thanks, Simon

#685 element Completed: Schemas validity error : Element 'Completed': This element is not expected. Expected is one of ( Comment, Contact, Created, DateCalendarCreated, DateEnd, DateStarted ). Plugin: vformat 0.40 defect normal 02/13/08

Hi! I get this error when syncing with my nokia e51:

element Completed: Schemas validity error : Element 'Completed': This element is not expected. Expected is one of ( Comment, Contact, Created, DateCalendarCreated?, DateEnd?, DateStarted? ).

The vevent card is for a 'Task' that has been completed. 

BEGIN:VCALENDAR
PRODID:-//OpenSync//NONSGML OpenSync vformat 0.3//EN
VERSION:2.0
BEGIN:VEVENT
CLASS:PRIVATE
COMPLETED:20080212T224422Z
DUE:20080211T000000
LAST-MODIFIED:20080212T224422Z
PRIORITY:2
SEQUENCE:0
STATUS:COMPLETED
SUMMARY:Foo bar
UID:z65cjDAQ4EFkg56AwF8ca1
END:VEVENT
END:VCALENDAR

Unlike #684 I get the same vevent card if I use both vevent10 and vevent20.

See also discussion at: http://thread.gmane.org/gmane.comp.misc.opensync.user/2453/focus=2455

Thanks, Simon

#686 element AlarmAttach: Schemas validity error : Element 'AlarmAttach': Character content other than whitespace is not allowed because the content type is 'element-only'. Plugin: vformat 0.40 defect normal 02/14/08

Hi! I get this error when syncing with my nokia e51: 

element AlarmAttach: Schemas validity error : Element 'AlarmAttach': Character content other than whitespace is not allowed because the content type is 'element-only'.
element AlarmAttach: Schemas validity error : Element 'AlarmAttach': Missing child element(s). Expected is ( Content ).

The vevent card received from the phone is (retrieved using syncml-obex-client): 

BEGIN:VCALENDAR
VERSION:1.0
TZ:+01
DAYLIGHT:TRUE;+02;20070325T010000Z;20071028T010000Z;;
DAYLIGHT:TRUE;+02;20080330T010000Z;20081026T010000Z;;
DAYLIGHT:TRUE;+02;20090329T010000Z;20091025T010000Z;;
DAYLIGHT:TRUE;+02;20100328T010000Z;20101031T010000Z;;
DAYLIGHT:TRUE;+02;20110327T010000Z;20111030T010000Z;;
BEGIN:VEVENT
UID:07022008145018409625-0
SUMMARY:Pdc
DTSTART:20070504T080000Z
DTEND:20070504T100000Z
X-EPOCAGENDAENTRYTYPE:APPOINTMENT
CLASS:PUBLIC
SEQUENCE:0
X-METHOD:NONE
RRULE:W1 FR #0
AALARM;TYPE=X-EPOCSOUND;ENCODING=QUOTED-PRINTABLE:20070504T071500Z;;;z:=5Csystem=5CSystemSounds=5Calarm.wav
LAST-MODIFIED:20080207T145018Z
PRIORITY:0
X-SYMBIAN-LUID:15
END:VEVENT
END:VCALENDAR

The card imported into my local file-sync sink is: 

BEGIN:VCALENDAR
PRODID:-//OpenSync//NONSGML OpenSync vformat 0.3//EN
VERSION:2.0
BEGIN:VEVENT
BEGIN:VALARM
ACTION:AUDIO
ATTACH:z:\\system\\SystemSounds\\alarm.wav
TRIGGER:20070504T071500Z
END:VALARM
CLASS:PUBLIC
DTEND:20070504T100000Z
DTSTART:20070504T080000Z
LAST-MODIFIED:20080207T145018Z
PRIORITY:0
RRULE:FREQ=WEEKLY;COUNT=0;INTERVAL=1;BYDAY=FR
SEQUENCE:0
SUMMARY:Pdc
UID:07022008145018409625-0
END:VEVENT
END:VCALENDAR

See also discussion at: http://thread.gmane.org/gmane.comp.misc.opensync.user/2453/focus=2455

Thanks, Simon

#656 Add support for X-EPOCAGENDAENTRYTYPE Plugin: vformat enhancement normal 01/01/08

Related to #462

My Nokia E70 exports X-EPOCAGENDAENTRYTYPE to VEVENTS. For me it seems that the only way of importing other types of calendar entries than appointments is having this present.

Some samples can be found with google.

Possible values I have found are APPOINTMENT, TODO, EVENT, and ANNIVERSARY.

dfriedrich

Ticket Summary Component Milestone Type Severity Created
Description
#289 modification: ignore spaces in phone numbers OpenSync defect blocker 08/02/06

In kdepim, I saved my numbers as +41 761234567 (the space is required by outlook, which I synced with Plaxo of which I imported the data into kdepim using an ldif file). When syncing with the empty address book of the SE k750i, the number is saved as +41761234567. When I sync again without making further changes, opensync reports a conflict and asks what to do. It would be nice, if such a difference was ignored automatically, since pressing i for ignore for 300 contacts takes quite some time.

dgollub

Ticket Summary Component Milestone Type Severity Created
Description
#643 Assertion "mapping_entry" in opensync_mapping_engine.c:66 fails OpenSync 0.37 defect blocker 12/03/07

Dear OpenSync? developers,

thank you very much for your great work.

When doing a normal sync (slow sync works and was finished successfully before) between moto-sync and kdepim-sync using libopensync revision 2915, I reliably get the following error: 

Synchronizing group "Handy" 
/home/steve/opensync/opensync/opensync/engine/opensync_mapping_engine.c:66:E:osync_mapping_engine_new: Assertion "mapping_entry" failed
Aborted (core dumped)

My configuration is: 

Member 1: moto-sync
        Configuration : <?xml version="1.0"?>
<config>
  <!-- device file name of the phone (/dev/ttyACM0 or /dev/rfcomm0) -->
  <device>/dev/rfcomm0</device>
</config>

Member 2: kdepim-sync
        No Configuration found: Plugin is not configured

A little gdb play results in: 

Core was generated by `msynctool --sync Handy --conflict 2'.
Program terminated with signal 6, Aborted.
#0  0xb7c74ea6 in raise () from /lib/libc.so.6
(gdb) bt
#0  0xb7c74ea6 in raise () from /lib/libc.so.6
#1  0xb7c767b1 in abort () from /lib/libc.so.6
#2  0xb7ea2386 in osync_mapping_engine_new (parent=0x8158d00, mapping=0x8165bd0, 
    error=0x80b02e0)
    at /home/steve/opensync/opensync/opensync/engine/opensync_mapping_engine.c:66
#3  0xb7ea3997 in osync_obj_engine_initialize (engine=0x8158d00, error=0x80b02e0)
    at /home/steve/opensync/opensync/opensync/engine/opensync_obj_engine.c:497
#4  0xb7e9f2fe in osync_engine_command (engine=0x80b0260, command=0x8158100)
    at /home/steve/opensync/opensync/opensync/engine/opensync_engine.c:1093
#5  0xb7ea0749 in _command_dispatch (source=0x80de608, callback=0, 
    user_data=0x80b0260)
    at /home/steve/opensync/opensync/opensync/engine/opensync_engine.c:215
#6  0xb7e0b1c6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#7  0xb7e0e552 in ?? () from /usr/lib/libglib-2.0.so.0
#8  0x080f1588 in ?? ()
#9  0x00000000 in ?? ()
(gdb) f 2
#2  0xb7ea2386 in osync_mapping_engine_new (parent=0x8158d00, mapping=0x8165bd0, 
    error=0x80b02e0)
    at /home/steve/opensync/opensync/opensync/engine/opensync_mapping_engine.c:66
66                      osync_assert(mapping_entry);
(gdb) p mapping_entry
$1 = <value optimized out>
(gdb) p mapping
$2 = (OSyncMapping *) 0x8165bd0
(gdb) p *mapping
$3 = {ref_count = 2, id = 12, entries = 0x815e070}
(gdb) p mapping->entries
$4 = (GList *) 0x815e070
(gdb) p *mapping->entries
$5 = {data = 0x81661b8, next = 0x0, prev = 0x0}
(gdb) p mapping->entries->data
$6 = (gpointer) 0x81661b8
(gdb) p (OSyncMappingEntry*)mapping->entries->data
$7 = (struct OSyncMappingEntry *) 0x81661b8
(gdb) p *(OSyncMappingEntry*)mapping->entries->data
$8 = {ref_count = 1, uid = 0x8166168 "libkcal-437768252.771", member_id = 2, 
  id = 12}
(gdb) f 3
#3  0xb7ea3997 in osync_obj_engine_initialize (engine=0x8158d00, error=0x80b02e0)
    at /home/steve/opensync/opensync/opensync/engine/opensync_obj_engine.c:497
497                     OSyncMappingEngine *mapping_engine = osync_mapping_engine_new(engine, mapping, error);
(gdb) p engine 
$9 = (OSyncObjEngine *) 0x8158d00
(gdb) p *engine
$10 = {ref_count = 1, parent = 0x80b0260, objtype = 0x8157948 "event", 
  slowsync = 0, archive = 0x809db18, mapping_table = 0x8158d58, 
  mapping_engines = 0x8164420, sink_engines