opensync-users — The place to get help for the OpenSync project

[Opensync-users] Compatibility with Solid?

[Hans B. <han...@gm...>]

---------- Forwarded message ----------
From: Hans Bakker <han...@gm...>
Date: 20-mei-2006 18:18
Subject: Fwd: [Opensync-users] Compatibility with Solid?
To: ope...@li...


Solid is the hardware detection library that will be used in the
upcoming KDE 4. Solid depends on several backends, so that will make
it not suitable for you. Maybe you could arrange something so that
people can use Solid as a backend for OpenSync when they use KDE 4? It
would make the hardware handling more consistent, I think.

Best regards,

Hans

---------- Forwarded message ----------
From: Armin Bauer <arm...@de...>
Date: 20-mei-2006 15:55
Subject: Re: [Opensync-users] Compatibility with Solid?
To: Hans Bakker <han...@gm...>
Cc: ope...@li...


Hi Hans,

Hans Bakker wrote:
> Hi,
>
> today I read the article about OpenSync on kde.org (in the Dot) and
> Tobias mentioned that he'd like to have a hardware detection
> mechanism. It sounded to me as if you wanted to write it yourself.
> Please, don't forget that the people of Solid (solid.kde.org) are
> doing fantastic work by making a hardware detection library, and that
> you maybe could use it instead of writing such code yourself.

I dont know what solid can do exactly. So ill just explain what opensync
would need:

OpenSync would need to monitor a variety of connection types like usb,
bluetooth, serial (if possible), irda and so on. if opensync detects a
device it would try to detect what type of device it sees exactly
(manufacturer, model, version, identifier). based on this information it
would lookup the device in a database to see what options are needed to
make the device work.

Do you know if solid would be capable of helping with this task? Another
issue: OpenSync is independent from desktops and X11. so it cannot use
anything that depends on such things.

Best Regards,
Armin

>
> Keep up the good work.
>
> Cheers,
>
> Hans Bakker
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronim=
o
> http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=120709&bid&3057&dat=121642
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
>

Re: [Opensync-users] Compatibility with Solid?

[Koen K. <ko...@do...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Armin Bauer schreef:
> Hi Hans,
> 
> Hans Bakker wrote:
>> Hi,
>>
>> today I read the article about OpenSync on kde.org (in the Dot) and
>> Tobias mentioned that he'd like to have a hardware detection
>> mechanism. It sounded to me as if you wanted to write it yourself.
>> Please, don't forget that the people of Solid (solid.kde.org) are
>> doing fantastic work by making a hardware detection library, and that
>> you maybe could use it instead of writing such code yourself.
> 
> I dont know what solid can do exactly. So ill just explain what opensync
> would need:
> 
> OpenSync would need to monitor a variety of connection types like usb,
> bluetooth, serial (if possible), irda and so on. if opensync detects a
> device it would try to detect what type of device it sees exactly
> (manufacturer, model, version, identifier). based on this information it
> would lookup the device in a database to see what options are needed to
> make the device work.
> 
> Do you know if solid would be capable of helping with this task? Another
> issue: OpenSync is independent from desktops and X11. so it cannot use
> anything that depends on such things.

Sounds like you'd want HAL[1] or udev (linux only) integration.

regards,

Koen

[1] http://hal.freedesktop.org/wiki/Software_2fhal


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFEbyECMkyGM64RGpERAvSmAJsGDofetbCX1aS/xzN8UiFZdRErEACeNG6B
xCYY6q55wrAkqkPkGB829AM=
=D2kr
-----END PGP SIGNATURE-----

Re: [Opensync-users] Compatibility with Solid?

[Armin B. <arm...@de...>]

Hi Hans,

Hans Bakker wrote:
> Hi,
>=20
> today I read the article about OpenSync on kde.org (in the Dot) and
> Tobias mentioned that he'd like to have a hardware detection
> mechanism. It sounded to me as if you wanted to write it yourself.
> Please, don't forget that the people of Solid (solid.kde.org) are
> doing fantastic work by making a hardware detection library, and that
> you maybe could use it instead of writing such code yourself.

I dont know what solid can do exactly. So ill just explain what opensync
would need:

OpenSync would need to monitor a variety of connection types like usb,
bluetooth, serial (if possible), irda and so on. if opensync detects a
device it would try to detect what type of device it sees exactly
(manufacturer, model, version, identifier). based on this information it
would lookup the device in a database to see what options are needed to
make the device work.

Do you know if solid would be capable of helping with this task? Another
issue: OpenSync is independent from desktops and X11. so it cannot use
anything that depends on such things.

Best Regards,
Armin

>=20
> Keep up the good work.
>=20
> Cheers,
>=20
> Hans Bakker
>=20
>=20
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, securit=
y?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geron=
imo
> http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=120709&bid&3057&dat=121642
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
>=20

[Opensync-users] Compatibility with Solid?

[Hans B. <han...@gm...>]

Hi,

today I read the article about OpenSync on kde.org (in the Dot) and
Tobias mentioned that he'd like to have a hardware detection
mechanism. It sounded to me as if you wanted to write it yourself.
Please, don't forget that the people of Solid (solid.kde.org) are
doing fantastic work by making a hardware detection library, and that
you maybe could use it instead of writing such code yourself.

Keep up the good work.

Cheers,

Hans Bakker

[Opensync-users] gnokii-sync - contact support

[Daniel G. <dg...@su...>]

Hi list,

the latest snapshot of gnokii-sync (rev 955) supports now syncing of contacts. 
It is quite experimental and not completed. You can disable syncing of 
contacts with the msynctool parameter --filter-objtype:

# msynctool --sync gnokii-test --filter-objtype contact

! It is strongly recommended to make a full backup of your contacts while 
testing !

The latest changes of gnokii-sync also requires the latest snapshot of the 
gnokii library.

Thanks for testing gnokii-sync! I got lots of freedback! Thanks! :)

Have fun! and happy testing :P

best regards,
Daniel

Re: [Opensync-users] Sync fails between Evo2 and GPE

[Andrew B. <and...@gm...>]

On Fri, 2006-05-19 at 14:35 +1200, Martin Felis wrote:
> Maybe you can give it a try and send again the
> output.

Here is the output of the updated plugin:

andrew@r51:~$ msynctool --sync zaurus
Synchronizing group "zaurus"
The previous synchronization was unclean. Slow-syncing
Member 1 of type gpe-sync just connected
Member 2 of type evo2-sync just connected
All clients connected or error
andrew@192.168.129.201's password: Received a entry
pas-id-44522C6900000000 with data of size 4 from member 2. Changetype
ADDED
Received a entry 20060517T004525Z-3935-1000-1-2@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T004749Z-3935-1000-1-5@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005050Z-3935-1000-1-8@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T004922Z-3935-1000-1-6@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T155339Z-4054-1000-1-0@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T004703Z-3935-1000-1-4@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T004615Z-3935-1000-1-3@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T113610Z-4076-1000-1-0@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005034Z-3935-1000-1-7@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005145Z-3935-1000-1-9@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005343Z-3935-1000-1-12@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005215Z-3935-1000-1-10@r51 with data of size 4
from member 2. Changetype ADDED
Member 2 of type evo2-sync just sent all changes

Member 1 of type gpe-sync just sent all changes
All clients sent changes or error
All conflicts have been reported
Member 2 of type evo2-sync committed all changes.
Error writing entry pas-id-44522C6900000000 to member 1: Couldn't commit
contact:  invalid Base64 sequence
Mapping Write Error: Couldn't commit contact:  invalid Base64 sequence
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004525Z-3935-1000-1-2@r51 to member 1:
Couldn't commit event  invalid format for type "date/time" in attribute
DTSTART
Mapping Write Error: Couldn't commit event  invalid format for type
"date/time" in attribute DTSTART
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004749Z-3935-1000-1-5@r51 to member 1:
Couldn't commit event  invalid format for type "date/time" in attribute
DTSTART
Mapping Write Error: Couldn't commit event  invalid format for type
"date/time" in attribute DTSTART
Error writing entry 20060517T005050Z-3935-1000-1-8@r51 to member 1:
Couldn't commit event  invalid value in attribute LAST-MODIFIED
Mapping Write Error: Couldn't commit event  invalid value in attribute
LAST-MODIFIED
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004922Z-3935-1000-1-6@r51 to member 1:
Couldn't commit event  invalid format for type "date/time" in attribute
DTSTART
Mapping Write Error: Couldn't commit event  invalid format for type
"date/time" in attribute DTSTART
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004703Z-3935-1000-1-4@r51 to member 1:
Couldn't commit event  invalid format for type "date/time" in attribute
DTSTART
Mapping Write Error: Couldn't commit event  invalid format for type
"date/time" in attribute DTSTART
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004615Z-3935-1000-1-3@r51 to member 1:
Couldn't commit event  invalid format for type "date/time" in attribute
DTSTART
Mapping Write Error: Couldn't commit event  invalid format for type
"date/time" in attribute DTSTART
Error writing entry 20060517T005034Z-3935-1000-1-7@r51 to member 1:
Couldn't commit event  invalid value in attribute LAST-MODIFIED
Mapping Write Error: Couldn't commit event  invalid value in attribute
LAST-MODIFIED
Error writing entry 20060517T005145Z-3935-1000-1-9@r51 to member 1:
Couldn't commit todo:  invalid value in attribute LAST-MODIFIED
Mapping Write Error: Couldn't commit todo:  invalid value in attribute
LAST-MODIFIED
Error writing entry 20060517T005343Z-3935-1000-1-12@r51 to member 1:
Couldn't commit todo:  invalid value in attribute LAST-MODIFIED
Mapping Write Error: Couldn't commit todo:  invalid value in attribute
LAST-MODIFIED
Error writing entry 20060517T005215Z-3935-1000-1-10@r51 to member 1:
Couldn't commit todo:  invalid value in attribute LAST-MODIFIED
Mapping Write Error: Couldn't commit todo:  invalid value in attribute
LAST-MODIFIED
Error writing entry 20060517T155339Z-4054-1000-1-0@r51 to member 1:
Couldn't commit event  invalid value in attribute LAST-MODIFIED
Mapping Write Error: Couldn't commit event  invalid value in attribute
LAST-MODIFIED
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T113610Z-4076-1000-1-0@r51 to member 1:
Couldn't commit event  invalid format for type "date/time" in attribute
DTSTART
Mapping Write Error: Couldn't commit event  invalid format for type
"date/time" in attribute DTSTART
Member 1 of type gpe-sync committed all changes.
All clients have written
Member 1 of type gpe-sync just disconnected
Member 2 of type evo2-sync just disconnected
All clients have disconnected
The sync failed: Unable to write one or more objects
Error synchronizing: Unable to write one or more objects

Hope this helps,
Andrew Barr

[Opensync-users] ticket spam

[Armin B. <arm...@de...>]

Hi,

i just wanted to inform you that ticket spamming should be solved now. I
added an account manager to trac (in the top-right corner) where you can
register a new account. Once you are logged in with this account (it
does not have to be actived or anything), you can modify wiki pages,
create tickets and so on.

Have fun!

Armin

Re: [Opensync-users] UTF-8 support and more

[Armin B. <arm...@de...>]

Stef=E1n Freyr Stef=E1nsson wrote:
> Hello.
>=20
> I wanted to ask a few questions.
>=20
> First of all, what is the status of adding UTF-8 support to the
> internals of OpenSync? When I tried using OpenSync last it worked to
> some extent... it did sync most of my items (calendar and contacts)
> but for each item the text stopped when an international character
> was encountered in the item (such as an icelandic character). This is
> a major show stopper for me since pretty much all of my contacts
> contain these characters. I just took a look at the OpenSync Trac
> page and I could not find any ticket that had to do with this. Is
> that some sort of a misunderstanding? Or has this issue maybe been
> fixed? I really hope this gets fixed ASAP since I'm waiting anxiously
> to use OpenSync.

Hi,

yes, the encoding issue is known and is a big todo on our list. The
problem is that opensync uses utf-8 internally, but stuff coming in from
a differen locale messes up the utf-8 parsing (since no encoding
conversion is done at the moment)

>=20
> My other question has to do with the "spam tickets" that are in Trac.
> Why haven't these tickets been marked as invalid? I was about to do
> that but then I figured that there had to be a reason that it hadn't
> been done a long time ago. Is there a reason or should I just go
> ahead and mark them as invalid?
>=20
> Can anything be done to prevent this sort of spamming?
>=20

yes. i just installed a new version of trac with an account manager
(more about this in a separate mail to the list).

Best Regards,
Armin Bauer

> Kind regards, Stefan Freyr.
>=20
>=20
> ------------------------------------------------------- Using Tomcat
> but need to do more? Need to support web services, security? Get
> stuff done quickly with pre-integrated technology to make your job
> easier Download IBM WebSphere Application Server v.1.0.1 based on
> Apache Geronimo=20
> http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=120709&bid&3057&dat=121642 =

> _______________________________________________ Opensync-users
> mailing list Ope...@li...=20
> https://lists.sourceforge.net/lists/listinfo/opensync-users
>=20

Re: [Opensync-users] Partial success on Nokia 6630

[Armin B. <arm...@de...>]

Hi,

>=20
> The X-EPOCAGENDAENTRYTYPE:ANNIVERSARY seems to be Symbian specific agai=
n. If=20
> this is all the case and if it is common to all Symbian devices, it mig=
ht=20
> make sense to create a special syncml-symbian-client or to include a sw=
itch=20
> into the syncml-obex-client to take care of these peculiarities. What d=
o you=20
> reckon?

OpenSync supports so called "extensions" in its format converters. A
extensions implements device-specific "enhancements" to the vcards to
support such devices. So we now need a extension to the vcard format
called "symbian" which takes care of shaping the vcard into something
these devices accept.

we are currently reworking the internal format conversion to make it
more powerful. At the moment it would not be possible to create this
"symbian" extension yet.

>=20
> One other problem occured when I imported my real contact list (all uml=
auts=20
> substituted) to evolution to sync it to my phone. The sync started okey=
 and=20
> the phone display was showing a progress bar and the number of transfer=
red=20
> contacts, but suddenly after about 30 of 150 contacts the sync stoped. =

> Sometimes this occured at entry 27 sometimes at 30 and so on. I had the=
=20
> impression that this coincides with the following line appearing on the=
 CL:
>=20
> I/O error : Attempt to load network entity=20
> http://www.syncml.org/docs/syncml_represent_v11_20020213.dtd
>=20
> After a while tons of error messages of this type appear:
>=20
> Error writing entry pas-id-445FBF6C00000060 to member 2: Timeout while =
waiting=20
> for a reply to message "COMMIT_CHANGE"
> Mapping Write Error: Timeout while waiting for a reply to=20
> message "COMMIT_CHANGE"
>=20
> The syncml-obex-client trace ends with the following lines:
>=20
> [1147126085.317415]	<<<<<<<  client_message_handler
> [1147126085.755768]	>>>>>>>  _manager_event(0x80831e0, 6, 0x80c9768, (n=
il),=20
> 0x8082500)
> [1147126085.755848]	<<<<<<<  _manager_event
> [1147126085.755888]	>>>>>>>  _smlManagerEventFree(0x858dc98)
> [1147126085.755927]		>>>>>>>  smlSessionUnref(0x80c9768)
> [1147126085.755965]		<<<<<<<  smlSessionUnref
> [1147126085.756003]	<<<<<<<  _smlManagerEventFree
> [1147126091.76960]	>>>>>>>  _manager_event(0x80831e0, 7, 0x80c9768, 0x8=
667ef8,=20
> 0x8082500)
> [1147126091.77014]		There was an error in the session 219: Received a s=
tatus=20
> after commands
> [1147126091.77071]	<--- ERROR --- _manager_event: Received a status aft=
er=20
> commands
> [1147126091.77110]	>>>>>>>  _smlManagerEventFree(0x820e7e0)
> [1147126091.77149]		>>>>>>>  smlSessionUnref(0x80c9768)
> [1147126091.77187]		<<<<<<<  smlSessionUnref
> [1147126091.77227]	<<<<<<<  _smlManagerEventFree
>=20
> No idea what happened here, but it's not nice. It never happened when I=
 did=20
> the testing with only a few entries.
>=20
> I've taken traces of all the above syncs, but I decided not to attach t=
hem to=20
> this mail. I'll send em off-list.

the syncml protocols clearly states that no status has to be sent after
a command has been sent. but some devices simply ignore the standard and
do this anyways.

there is a option in the config AllowLateStatus which you can set to 1
to allow such behaviour.

Best Regards,
Armin

>=20
> Hope this helps a bit.
>=20
> Conrad.
>=20
>=20
>> Armin
>>
>=20
>=20
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, securit=
y?
> Get stuff done quickly with pre-integrated technology to make your job =
easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geron=
imo
> http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=120709&bid&3057&dat=121642
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
>=20

Re: [Opensync-users] Problem syncing with Nokia 6230

[Stef E. <st...@ep...>]

On Fri, May 19, 2006 at 08:18:34AM +0200, Francesc Guasch wrote:
> En/na stephane ha escrit:
> > I'm trying again to sync my phone using bluetooth and syncml, but sti=
ll
> > <bluetooth_channel>11</bluetooth_channel>
>=20
> I own a 6230i, I also found it reported channel 11 but
> I was advised to try channel 7 and it worked. Try it.
> If it keeps failing try other channels.

I did try the 7 and it worked way less than the 11...
--=20
St=C3=A9phane Epardaud

Re: [Opensync-users] Problem syncing with Nokia 6230

[Francesc G. <fr...@et...>]

En/na stephane ha escrit:
> Hi,
> 
> I'm trying again to sync my phone using bluetooth and syncml, but still
> <bluetooth_channel>11</bluetooth_channel>

I own a 6230i, I also found it reported channel 11 but
I was advised to try channel 7 and it worked. Try it.
If it keeps failing try other channels.

Re: [Opensync-users] Sync fails between Evo2 and GPE

[Martin F. <ma...@si...>]

Hi,

I can't tell why you are having that problem, but as far as I know are
you not the only one. I updated the plugin so that the errors will now
be reported correctly. Maybe you can give it a try and send again the
output.

Thank you!
Martin

On 5/19/06, Andrew Barr <and...@gm...> wrote:
> Well, I'm using the latest evolution-data-server software available in
> Debian, which is 1.6.1. The evo2-sync plugin was compiled against this.
>
> > I will have a look at it this. I saw that I set in gpe_sync.c at about
> > line 206 "info->is_threadsafe =3D TRUE;". I have no real clue what
> > threadsafe is, but I guess the plugin is not. This might be the cause
> > for the problem. If you can, set it to "info->is_threadsafe =3D FALSE;"
> > and give it a go.
>
> Unfortunately this didn't change anything. The output of msynctool is
> the same. Thanks for the tip though.
>
> Regards,
> Andrew Barr
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
>
> iD8DBQBEbHijhuM+Z62a52oRAtYeAJ9FaEb5J2RgVEOmTJ/sF5B8bFpTOgCgxZAi
> 3OVerqziEhGn0/y60MNGeuU=3D
> =3D0wD6
> -----END PGP SIGNATURE-----
>
>
>

[Opensync-users] syncml fails the second time

[Francesc G. <fr...@et...>]

Hi. I'm trying to sync using syncml to file. The very first time
the phone just booted it works. but it fails the second one.
The phone shows the message: "Abandoning Syncronization" ( More or
less, the message is in spanish ) . This message doesn't disapear.

I have 4 trace files, should I send all of them ?

I grepped for ERROR, here is the output:

Thread3054762928.log:[1147963902.406648]        [ENG] ERROR: Timeout 
while waiting for a reply to message 0x809ae58:"DISCONNECT". Sending 
error 0x809a4b8

Thread3063155632.log:[1147963842.403331]        <--- ERROR --- 
_manager_event: Request not successfull: 67

Thread3082077888.log:[1147963902.409369]        <--- ERROR --- 
osengine_sync_and_block: Unable to read from one of the members

Re: [Opensync-users] evo2 plugin can't find anything...

[Jose de P. E. J. <jpe...@gm...>]

On 5/18/06, daniel friedrich <dan...@gm...> wrote:
> Please post the configuration file.
> you have to enter the path to your addressbook and not the name of the
> addressbook.
>
> for example:
>
> <?xml version=3D"1.0"?>
> <config><adress_path>file:///home/daniel/.evolution/addressbook/local/</a=
dress_path>
> <calendar_path/>
> <tasks_path/>
> </config>

<config>
<adress_path>file:///home/coredump/.evolution/addressbook/local/</adress_pa=
th>
<calendar_path>file:///home/coredump/.evolution/calendar/local/</calendar_p=
ath>
<tasks_path>file:///home/coredump/.evolution/tasks/local/</tasks_path>
</config>

No game, yet :\

Member 2 of type evo2-sync had an error while connecting: Unable to
open anything

--=20
Jose de Paula Eufrasio Junior <jpe...@gm...>
aka coredump
http://coredump.osimortais.com.br

Re: [Opensync-users] Sync fails between Evo2 and GPE

[Andrew B. <and...@gm...>]

On Thu, 2006-05-18 at 14:58 +1200, Martin Felis wrote:
> Hello there,
>=20
> I am the author of al this, so I should know what the problem is. I
> was not yet able, to reproduce your error (but others though), but
> this might be due to the old evolution plugin I have.=20

Well, I'm using the latest evolution-data-server software available in
Debian, which is 1.6.1. The evo2-sync plugin was compiled against this.

> I will have a look at it this. I saw that I set in gpe_sync.c at about
> line 206 "info->is_threadsafe =3D TRUE;". I have no real clue what
> threadsafe is, but I guess the plugin is not. This might be the cause
> for the problem. If you can, set it to "info->is_threadsafe =3D FALSE;"
> and give it a go.

Unfortunately this didn't change anything. The output of msynctool is
the same. Thanks for the tip though.

Regards,
Andrew Barr

Re: [Opensync-users] evo2 plugin can't find anything...

[daniel f. <dan...@gm...>]

Please post the configuration file.
you have to enter the path to your addressbook and not the name of the
addressbook.

for example:

<?xml version=3D"1.0"?>
<config><adress_path>file:///home/daniel/.evolution/addressbook/local/</adr=
ess_path>
<calendar_path/>
<tasks_path/>
</config>

Am Donnerstag, den 18.05.2006, 03:00 -0300 schrieb Jose de Paula
Eufrasio Junior:
> Hello.
>=20
> I followed all the instructions to compile and install and configure
> the opensync 0.18 and the evolution and gpe plugins.
>=20
> Now, when I try to sync I get that:
>=20
> _____________________________
> msynctool --sync evo-gpe
> Synchronizing group "evo-gpe"
> The previous synchronization was unclean. Slow-syncing
> Member 1 of type gpe-sync just connected
> Member 2 of type evo2-sync had an error while connecting: Unable to
> open anything
> Member 1 of type gpe-sync just disconnected
> All clients have disconnected
> The sync failed: Unable to connect one of the members
> Error synchronizing: Unable to connect one of the members
> ________________________
>=20
> Member 2 is the evo2 plugin. The dataserver from evolution is running,
> and on the configuration XML I put the names of my adressbook, todo
> and contacts.
>=20
> Any help?
>=20

[Opensync-users] evo2 plugin can't find anything...

[Jose de P. E. J. <jpe...@gm...>]

Hello.

I followed all the instructions to compile and install and configure
the opensync 0.18 and the evolution and gpe plugins.

Now, when I try to sync I get that:

_____________________________
msynctool --sync evo-gpe
Synchronizing group "evo-gpe"
The previous synchronization was unclean. Slow-syncing
Member 1 of type gpe-sync just connected
Member 2 of type evo2-sync had an error while connecting: Unable to
open anything
Member 1 of type gpe-sync just disconnected
All clients have disconnected
The sync failed: Unable to connect one of the members
Error synchronizing: Unable to connect one of the members
________________________

Member 2 is the evo2 plugin. The dataserver from evolution is running,
and on the configuration XML I put the names of my adressbook, todo
and contacts.

Any help?

--=20
Jose de Paula Eufrasio Junior <jpe...@gm...>
aka coredump
http://coredump.osimortais.com.br

[Opensync-users] Pace of opensync development.

[Alex P. <not...@gm...>]

Hi there.

I'd like to get at picture of the pace of development for Opensync.

In late 2005 Opensync and KDE declared that they would be working
together. And didn't some major distro (Suse?) say that the where
going to support the project with a full/part time developer?

What has been happening since then? Is anybody getting paid to work on
this or is it all late night hacking? How many developers all in all
are actively contributing?

I'm asking because I'm working on a  GTD project  that would very much
benefit from a working sync solution for Linux. Right now I'm using
kpilot and really sucks. I chose kpilot because it will allow you to
sync icalendar files with a palm. Thus I could use an ical flat file
as my back end. I figured that any sync frameworks that appear in the
future would be likely to work with icalendar and that it would be my
safest bet. Do you think that is a correct assumption? Does Opensync
support ical files yet? Is it a planned feature? Is Opensync stable
enough to be used on a day to day basis for someone syncing to a Palm?

alex

--=20
Alex Polite
http://flosspick.org - finding the right open source

Re: [Opensync-users] Sync fails between Evo2 and GPE

[Martin F. <ma...@si...>]

Hello there,

I am the author of al this, so I should know what the problem is. I
was not yet able, to reproduce your error (but others though), but
this might be due to the old evolution plugin I have. Unfortunately I
can't compile the newer one. I am experiencing the same bug as
described under http://www.opensync.org/ticket/167 .

I will have a look at it this. I saw that I set in gpe_sync.c at about
line 206 "info->is_threadsafe =3D TRUE;". I have no real clue what
threadsafe is, but I guess the plugin is not. This might be the cause
for the problem. If you can, set it to "info->is_threadsafe =3D FALSE;"
and give it a go.
But I'll have a check for it.

So long,
Martin

On 5/17/06, Andrew Barr <and...@gm...> wrote:
> Hi, I'm trying to sync my Sharp SL-5500 running the GPE version of
> OpenZaurus 3.5.4.1 and Evolution 2.6.1 on a Debian unstable system. The
> gpe-sync plugin is configured to the Zaurus' IP address and my username,
> port 22 and use_ssh is 1. evo2-sync is using the default config. SSH'ing
> into the Zaurus works fine. I checked the code out of the SVN repo just
> about an hour ago. Here is the output of 'msynctool --sync zaurus':
>
> Synchronizing group "zaurus"
> The previous synchronization was unclean. Slow-syncing
> Member 1 of type gpe-sync just connected
> Member 2 of type evo2-sync just connected
> All clients connected or error
> Received a entry pas-id-44522C6900000000 with data of size 4 from member
> 2. Changetype ADDED
> Received a entry 20060517T004525Z-3935-1000-1-2@r51 with data of size 4
> from member 2. Changetype ADDED
> andrew@192.168.129.201's password: Received a entry
> 20060517T004749Z-3935-1000-1-5@r51 with data of size 4 from member 2.
> Changetype ADDED
> Received a entry 20060517T005050Z-3935-1000-1-8@r51 with data of size 4
> from member 2. Changetype ADDED
> Received a entry 20060517T004922Z-3935-1000-1-6@r51 with data of size 4
> from member 2. Changetype ADDED
> Received a entry 20060517T004703Z-3935-1000-1-4@r51 with data of size 4
> from member 2. Changetype ADDED
> Received a entry 20060517T004615Z-3935-1000-1-3@r51 with data of size 4
> from member 2. Changetype ADDED
> Received a entry 20060517T005034Z-3935-1000-1-7@r51 with data of size 4
> from member 2. Changetype ADDED
> Received a entry 20060517T005145Z-3935-1000-1-9@r51 with data of size 4
> from member 2. Changetype ADDED
> Received a entry 20060517T005343Z-3935-1000-1-12@r51 with data of size 4
> from member 2. Changetype ADDED
> Received a entry 20060517T005215Z-3935-1000-1-10@r51 with data of size 4
> from member 2. Changetype ADDED
> Member 2 of type evo2-sync just sent all changes
>
> Member 1 of type gpe-sync just sent all changes
> All clients sent changes or error
> All conflicts have been reported
> Error writing entry pas-id-44522C6900000000 to member 1: Couldn't commit
> contact: (null)
> Mapping Write Error: Couldn't commit contact: (null)
> Error writing entry 20060517T004525Z-3935-1000-1-2@r51 to member 1:
> Couldn't commit event: (null)
> Mapping Write Error: Couldn't commit event: (null)
> Error writing entry 20060517T004749Z-3935-1000-1-5@r51 to member 1:
> Couldn't commit event: (null)
> Mapping Write Error: Couldn't commit event: (null)
> Member 2 of type evo2-sync committed all changes.
> Error writing entry 20060517T005050Z-3935-1000-1-8@r51 to member 1:
> Couldn't commit event: (null)
> Mapping Write Error: Couldn't commit event: (null)
> Error writing entry 20060517T004922Z-3935-1000-1-6@r51 to member 1:
> Couldn't commit event: (null)
> Mapping Write Error: Couldn't commit event: (null)
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> Error writing entry 20060517T004703Z-3935-1000-1-4@r51 to member 1:
> Couldn't commit event: (null)
> Mapping Write Error: Couldn't commit event: (null)
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> Error writing entry 20060517T004615Z-3935-1000-1-3@r51 to member 1:
> Couldn't commit event: (null)
> Mapping Write Error: Couldn't commit event: (null)
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> Error writing entry 20060517T005034Z-3935-1000-1-7@r51 to member 1:
> Couldn't commit event: (null)
> Mapping Write Error: Couldn't commit event: (null)
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> Error writing entry 20060517T005145Z-3935-1000-1-9@r51 to member 1:
> Couldn't commit todo: (null)
> Mapping Write Error: Couldn't commit todo: (null)
> Error writing entry 20060517T005343Z-3935-1000-1-12@r51 to member 1:
> Couldn't commit todo: (null)
> Mapping Write Error: Couldn't commit todo: (null)
> Error writing entry 20060517T005215Z-3935-1000-1-10@r51 to member 1:
> Couldn't commit todo: (null)
> Mapping Write Error: Couldn't commit todo: (null)
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> Member 1 of type gpe-sync committed all changes.
> All clients have written
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> Member 1 of type gpe-sync just disconnected
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> Member 2 of type evo2-sync just disconnected
> All clients have disconnected
> The sync failed: Unable to write one or more objects
> Error synchronizing: Unable to write one or more objects
>
> Between the lines "Member 2 of type evo2-sync just sent all changes" and
> "Member 1 of type gpe-sync just sent all changes" it stops and waits for
> me to type my SSH password for the Zaurus.
>
> I have tried deleting the PIM database files on the Zaurus and starting
> again--the Zaurus is supposed to be empty. There are records in
> Evolution that I want copied to the Zaurus on this first sync.
>
> Any help would be greatly appreciated.
>
> Regards,
> Andrew Barr
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
>
> iD8DBQBEanpWhuM+Z62a52oRAvNLAJ0eqNhROBkT9vhVCqwGtXXqUhdtuACgoWSZ
> fpu9ileKJZzqlMzQaPR/VEU=3D
> =3DtiGn
> -----END PGP SIGNATURE-----
>
>
>

[Opensync-users] UTF-8 support and more

[<st...@ru...>]

Hello.

I wanted to ask a few questions.

First of all, what is the status of adding UTF-8 support to the =
internals of OpenSync? When I tried using OpenSync last it worked to =
some extent... it did sync most of my items (calendar and contacts) but =
for each item the text stopped when an international character was =
encountered in the item (such as an icelandic character). This is a =
major show stopper for me since pretty much all of my contacts contain =
these characters. I just took a look at the OpenSync Trac page and I =
could not find any ticket that had to do with this. Is that some sort of =
a misunderstanding? Or has this issue maybe been fixed? I really hope =
this gets fixed ASAP since I'm waiting anxiously to use OpenSync.

My other question has to do with the "spam tickets" that are in Trac. =
Why haven't these tickets been marked as invalid? I was about to do that =
but then I figured that there had to be a reason that it hadn't been =
done a long time ago. Is there a reason or should I just go ahead and =
mark them as invalid?

Can anything be done to prevent this sort of spamming?

Kind regards, Stefan Freyr.

[Opensync-users] Sync fails between Evo2 and GPE

[Andrew B. <and...@gm...>]

Hi, I'm trying to sync my Sharp SL-5500 running the GPE version of
OpenZaurus 3.5.4.1 and Evolution 2.6.1 on a Debian unstable system. The
gpe-sync plugin is configured to the Zaurus' IP address and my username,
port 22 and use_ssh is 1. evo2-sync is using the default config. SSH'ing
into the Zaurus works fine. I checked the code out of the SVN repo just
about an hour ago. Here is the output of 'msynctool --sync zaurus':

Synchronizing group "zaurus"
The previous synchronization was unclean. Slow-syncing
Member 1 of type gpe-sync just connected
Member 2 of type evo2-sync just connected
All clients connected or error
Received a entry pas-id-44522C6900000000 with data of size 4 from member
2. Changetype ADDED
Received a entry 20060517T004525Z-3935-1000-1-2@r51 with data of size 4
from member 2. Changetype ADDED
andrew@192.168.129.201's password: Received a entry
20060517T004749Z-3935-1000-1-5@r51 with data of size 4 from member 2.
Changetype ADDED
Received a entry 20060517T005050Z-3935-1000-1-8@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T004922Z-3935-1000-1-6@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T004703Z-3935-1000-1-4@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T004615Z-3935-1000-1-3@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005034Z-3935-1000-1-7@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005145Z-3935-1000-1-9@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005343Z-3935-1000-1-12@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005215Z-3935-1000-1-10@r51 with data of size 4
from member 2. Changetype ADDED
Member 2 of type evo2-sync just sent all changes

Member 1 of type gpe-sync just sent all changes
All clients sent changes or error
All conflicts have been reported
Error writing entry pas-id-44522C6900000000 to member 1: Couldn't commit
contact: (null)
Mapping Write Error: Couldn't commit contact: (null)
Error writing entry 20060517T004525Z-3935-1000-1-2@r51 to member 1:
Couldn't commit event: (null)
Mapping Write Error: Couldn't commit event: (null)
Error writing entry 20060517T004749Z-3935-1000-1-5@r51 to member 1:
Couldn't commit event: (null)
Mapping Write Error: Couldn't commit event: (null)
Member 2 of type evo2-sync committed all changes.
Error writing entry 20060517T005050Z-3935-1000-1-8@r51 to member 1:
Couldn't commit event: (null)
Mapping Write Error: Couldn't commit event: (null)
Error writing entry 20060517T004922Z-3935-1000-1-6@r51 to member 1:
Couldn't commit event: (null)
Mapping Write Error: Couldn't commit event: (null)
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004703Z-3935-1000-1-4@r51 to member 1:
Couldn't commit event: (null)
Mapping Write Error: Couldn't commit event: (null)
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004615Z-3935-1000-1-3@r51 to member 1:
Couldn't commit event: (null)
Mapping Write Error: Couldn't commit event: (null)
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T005034Z-3935-1000-1-7@r51 to member 1:
Couldn't commit event: (null)
Mapping Write Error: Couldn't commit event: (null)
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T005145Z-3935-1000-1-9@r51 to member 1:
Couldn't commit todo: (null)
Mapping Write Error: Couldn't commit todo: (null)
Error writing entry 20060517T005343Z-3935-1000-1-12@r51 to member 1:
Couldn't commit todo: (null)
Mapping Write Error: Couldn't commit todo: (null)
Error writing entry 20060517T005215Z-3935-1000-1-10@r51 to member 1:
Couldn't commit todo: (null)
Mapping Write Error: Couldn't commit todo: (null)
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Member 1 of type gpe-sync committed all changes.
All clients have written
The profile contains the unsupported custom attribute X-LIC-LOCATION.
The profile contains the unsupported custom attribute X-LIC-LOCATION.
The profile contains the unsupported custom attribute X-LIC-LOCATION.
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Member 1 of type gpe-sync just disconnected
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Member 2 of type evo2-sync just disconnected
All clients have disconnected
The sync failed: Unable to write one or more objects
Error synchronizing: Unable to write one or more objects

Between the lines "Member 2 of type evo2-sync just sent all changes" and
"Member 1 of type gpe-sync just sent all changes" it stops and waits for
me to type my SSH password for the Zaurus.

I have tried deleting the PIM database files on the Zaurus and starting
again--the Zaurus is supposed to be empty. There are records in
Evolution that I want copied to the Zaurus on this first sync.

Any help would be greatly appreciated.

Regards,
Andrew Barr

Re: [Opensync-users] Unable to commit change. Error 500

[<jv...@no...>]

Have a typo in my last mail,
the ticket is #191 (not 192).

Rgds,
           --Joris

Quoting jv...@no...:

> Hi List,
>
> I opened a problem ticket (#192) because of this problem while syncing ove=
r
> bluetooth/usb with the symcml plugin (nokia 6280) and evo2 plugin:
> Error writing entry pas-id-42790C1C0000006A to member 2: Unable to commit
> change. Error 500 Mapping Write Error: Unable to commit change. Error 500
>
> Some contacts are synced but most of them are skipped with this=20
> error. (15 are
> synced but the other, ~120 are skipped).
>
> Any idea how I could fix this?
>
> Rgds,
>         --Joris.
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job eas=
ier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
121642
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
>



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

[Opensync-users] Unable to commit change. Error 500

[<jv...@no...>]

Hi List,

I opened a problem ticket (#192) because of this problem while syncing over
bluetooth/usb with the symcml plugin (nokia 6280) and evo2 plugin:
Error writing entry pas-id-42790C1C0000006A to member 2: Unable to commit
change. Error 500 Mapping Write Error: Unable to commit change. Error 500

Some contacts are synced but most of them are skipped with this error. (15 are
synced but the other, ~120 are skipped).

Any idea how I could fix this?

Rgds,
        --Joris.


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

[Opensync-users] Crash with invalid pointer when using evo plugin under fc5

[Jason G. <ju...@lo...>]

Same stack trace as today's post by Marcos, except I get it when I try
to sync with evolution.  I currently have no tasks or calendar entries,
and only one contact.  When I remove this contact and sync, msynctool no
longer crashes.  Looks like it is a problem reading the evo file?

I'm running fedora core 5, and evolution 2.6.1 as installed from the
fedora yum repository.

I've installed the following from opensync:

-rw-rw-r--  1 jas jas 610922 May 13 14:56 libopensync-0.18.tar.gz
-rw-rw-r--  1 jas jas 976938 May 13 14:57 multisync-0.90.18.tar.gz
-rw-rw-r--  1 jas jas 315146 May 13 14:57
libopensync-plugin-evolution2-0.18.tar.gz
-rw-rw-r--  1 jas jas 314076 May 13 14:57
libopensync-plugin-file-0.18.tar.gz

Here's the output from the crash:

[jas@talby ~]$ msynctool --sync ef
Synchronizing group "ef"
Member 2 of type file-sync just connected
Member 1 of type evo2-sync just connected
All clients connected or error
Member 2 of type file-sync just sent all changes
Member 1 of type evo2-sync just sent all changes
All clients sent changes or error
Member 1 of type evo2-sync committed all changes.
Member 2 of type file-sync committed all changes.
All clients have written
Member 2 of type file-sync just disconnected
Member 1 of type evo2-sync just disconnected
All clients have disconnected
The sync was successful
[jas@talby ~]$ msynctool --sync ef
Synchronizing group "ef"
Member 2 of type file-sync just connected
Member 1 of type evo2-sync just connected
All clients connected or error
Member 2 of type file-sync just sent all changes
Received a entry pas-id-4465753100000000 with data of size 4 from member
1. Chan getype ADDED
Member 1 of type evo2-sync just sent all changes
All clients sent changes or error
All conflicts have been reported
*** glibc detected *** msynctool: munmap_chunk(): invalid pointer:
0x001e6b1b ** *
======= Backtrace: =========
/lib/libc.so.6(__libc_free+0x17b)[0xae151f]
/usr/lib/libglib-2.0.so.0(g_free+0x31)[0xc1d5a1]
/usr/local/lib/opensync/formats/xml-vcard.so[0x1dfaed]
/usr/local/lib/opensync/formats/xml-vcard.so[0x1e06fc]
/usr/local/lib/opensync/formats/xml-vcard.so[0x1debed]
/usr/local/lib/libopensync.so.0(osync_converter_invoke+0xea)[0x3a8d9a]
/usr/local/lib/libopensync.so.0(osync_conv_convert_fn+0x16a)[0x3a998a]
/usr/local/lib/libopensync.so.0(osync_change_convert_member_sink
+0x5d)[0x3aa1ad]
/usr/local/lib/libopensync.so.0(osync_member_commit_change
+0xcb)[0x3a4bfb]
/usr/local/lib/libosengine.so.0(client_message_handler+0x196)[0xcd3186]
/usr/local/lib/libosengine.so.0(_queue_dispatch+0x95)[0xcd26f5]
/usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x16d)[0xc1615d]
/usr/lib/libglib-2.0.so.0[0xc193ef]
/usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1a9)[0xc19799]
/usr/lib/libglib-2.0.so.0[0xc33a1f]
/lib/libpthread.so.0[0xdef3b6]
/lib/libc.so.6(__clone+0x5e)[0xb4233e]
======= Memory map: ========
00111000-00114000 r-xp 00000000 fd:00
20414835   /usr/local/lib/opensync/plugins /file_sync.so
00114000-00115000 rwxp 00002000 fd:00
20414835   /usr/local/lib/opensync/plugins /file_sync.so
00115000-0011b000 r-xp 00000000 fd:00
20414839   /usr/local/lib/opensync/plugins /evo2_sync.so
0011b000-0011c000 rwxp 00006000 fd:00
20414839   /usr/local/lib/opensync/plugins /evo2_sync.so
0011c000-00123000 r-xp 00000000 fd:00
18098851   /usr/lib/libpopt.so.0.0.0
00123000-00124000 rwxp 00006000 fd:00
18098851   /usr/lib/libpopt.so.0.0.0
00124000-0017e000 r-xp 00000000 fd:00
18109444   /usr/lib/libbonobo-2.so.0.0.0
0017e000-00188000 rwxp 0005a000 fd:00
18109444   /usr/lib/libbonobo-2.so.0.0.0
00188000-001d9000 r-xp 00000000 fd:00
18114244   /usr/lib/libcamel-1.2.so.0.0.0
001d9000-001dc000 rwxp 00050000 fd:00
18114244   /usr/lib/libcamel-1.2.so.0.0.0
001dc000-001e8000 r-xp 00000000 fd:00
20414794   /usr/local/lib/opensync/formats /xml-vcard.so
001e8000-001e9000 rwxp 0000b000 fd:00
20414794   /usr/local/lib/opensync/formats /xml-vcard.so
001e9000-001ec000 r-xp 00000000 fd:00
18103382   /usr/local/lib/libopensync-xml. so.0.0.0
001ec000-001ed000 rwxp 00002000 fd:00
18103382   /usr/local/lib/libopensync-xml. so.0.0.0
001ed000-00206000 r-xp 00000000 fd:00 23791068   /lib/ld-2.4.so
00206000-00207000 r-xp 00018000 fd:00 23791068   /lib/ld-2.4.so
00207000-00208000 rwxp 00019000 fd:00 23791068   /lib/ld-2.4.so
00208000-00209000 r-xp 00000000 fd:00
20414812   /usr/local/lib/opensync/formats /contact.so
00209000-0020a000 rwxp 00001000 fd:00
20414812   /usr/local/lib/opensync/formats /contact.so
0020a000-0021b000 r-xp 00000000 fd:00 23791075   /lib/libnsl-2.4.so
0021b000-0021c000 r-xp 00010000 fd:00 23791075   /lib/libnsl-2.4.so
0021c000-0021d000 rwxp 00011000 fd:00 23791075   /lib/libnsl-2.4.so
0021d000-0021f000 rwxp 0021d000 00:00 0
0021f000-00220000 r-xp 00000000 fd:00
20414814   /usr/local/lib/opensync/formats /note.so
00220000-00221000 rwxp 00000000 fd:00
20414814   /usr/local/lib/opensync/formats /note.so
00221000-00223000 r-xp 00000000 fd:00 23791079   /lib/libcom_err.so.2.1
00223000-00224000 rwxp 00001000 fd:00 23791079   /lib/libcom_err.so.2.1
00224000-00225000 r-xp 00000000 fd:00
20414810   /usr/local/lib/opensync/formats /todo.so
00225000-00226000 rwxp 00000000 fd:00
20414810   /usr/local/lib/opensync/formats /todo.so
00226000-00235000 r-xp 00000000 fd:00 23791078   /lib/libresolv-2.4.so
00235000-00236000 r-xp 0000e000 fd:00 23791078   /lib/libresolv-2.4.so
00236000-00237000 rwxp 0000f000 fd:00 23791078   /lib/libresolv-2.4.so
00237000-00239000 rwxp 00237000 00:00 0
00239000-0025d000 r-xp 00000000 fd:00
18113341   /usr/lib/libk5crypto.so.3.0
0025d000-0025e000 rwxp 00024000 fd:00
18113341   /usr/lib/libk5crypto.so.3.0
0025e000-00268000 r-xp 00000000 fd:00
20414800   /usr/local/lib/opensync/formats /xml-vnote.so
00268000-00269000 rwxp 00009000 fd:00
20414800   /usr/local/lib/opensync/formats /xml-vnote.so
00269000-0026b000 r-xp 00000000 fd:00
20414816   /usr/local/lib/opensync/formats /file.so
0026b000-0026c000 rwxp 00001000 fd:00
20414816   /usr/local/lib/opensync/formats /file.so
0026c000-00275000 r-xp 00000000 fd:00
20414798   /usr/local/lib/opensync/formats /xml-evolution.so
00275000-00276000 rwxp 00009000 fd:00
20414798   /usr/local/lib/opensync/formats /xml-evolution.so
00276000-00286000 r-xp 00000000 fd:00
20414796   /usr/local/lib/opensync/formats /xml-vcal.so
00286000-00287000 rwxp 0000f000 fd:00
20414796   /usr/local/lib/opensync/formats /xml-vcal.so
00287000-00290000 r-xp 00000000 fd:00
20414802   /usr/local/lib/opensync/formats /xml-kde.so
00290000-00291000 rwxp 00008000 fd:00
20414802   /usr/local/lib/opensync/formats /xml-kde.so
00291000-00292000 r-xp 00000000 fd:00
20414806   /usr/local/lib/opensync/formats /data.so
00292000-00293000 rwxp 00000000 fd:00
20414806   /usr/local/lib/opensync/formats /data.so
00298000-002d9000 r-xp 00000000 fd:00 23789593   /lib/libssl.so.0.9.8a
002d9000-002dd000 rwxp 00040000 fd:00 23789593   /lib/libssl.so.0.9.8a
002df000-002e3000 r-xp 00000000 fd:00
18108346   /usr/lib/libgthread-2.0.so.0.10 00.2
002e3000-002e4000 rwxp 00003000 fd:00
18108346   /usr/lib/libgthread-2.0.so.0.10 00.2
002e6000-002fb000 r-xp 00000000 fd:00
18111377   /usr/lib/libgnome-2.so.0.1400.0
002fb000-002fc000 rwxp 00015000 fd:00
18111377   /usr/lib/libgnome-2.so.0.1400.0
00306000-00354000 r-xp 00000000 fd:00
18109201   /usr/lib/libORBit-2.so.0.1.0
00354000-0035d000 rwxp 0004e000 fd:00
18109201   /usr/lib/libORBit-2.so.0.1.0
0035d000-0035e000 rwxp 0035d000 00:00 0
00372000-0038a000 r-xp 00000000 fd:00
18113343   /usr/lib/libgssapi_krb5.so.2.2
0038a000-0038b000 rwxp 00017000 fd:00
18113343   /usr/lib/libgssapi_krb5.so.2.2
00394000-003b3000 r-xp 00000000 fd:00
18099114   /usr/local/lib/libopensync.so.0 .0.0
003b3000-003b4000 rwxp 0001e000 fd:00
18099114   /usr/local/lib/libopensync.so.0 .0.0
003be000-003c1000 r-xp 00000000 fd:00
18091831   /usr/lib/libkrb5support.so.0.0
003c1000-003c2000 rwxp 00002000 fd:00
18091831   /usr/lib/libkrb5support.so.0.0
003c4000-00437000 r-xp 00000000 fd:00 18113342   /usr/lib/libkrb5.so.3.2
00437000-00439000 rwxp 00073000 fd:00 18113342   /usr/lib/libkrb5.so.3.2
00476000-0047a000 r-xp 00000000 fd:00
18109205   /usr/lib/libORBitCosNaming-2.so .0.1.0
0047a000-0047b000 rwxp 00004000 fd:00
18109205   /usr/lib/libORBitCosNaming-2.so .0.1.0
00482000-00485000 r-xp 00000000 fd:00 23791091   /lib/libcap.so.1.10
00485000-00486000 rwxp 00002000 fd:00 23791091   /lib/libcap.so.1.10
00488000-0048e000 r-xp 00000000 fd:00 23791077   /lib/librt-2.4.so
0048e000-0048f000 r-xp 00005000 fd:00 23791077   /lib/librt-2.4.so
0048f000-00490000 rwxp 00006000 fd:00 23791077   /lib/librt-2.4.so
00492000-00495000 r-xp 00000000 fd:00
18109626   /usr/lib/libavahi-glib.so.1.0.0
00495000-00496000 rwxp 00002000 fd:00
18109626   /usr/lib/libavahi-glib.so.1.0.0
00499000-0050b000 r-xp 00000000 fd:00 23791092   /lib/libdbus-1.so.2.0.0
0050b000-0050c000 rwxp 00072000 fd:00 23791092   /lib/libdbus-1.so.2.0.0
00511000-00512000 r-xp 00511000 00:00 0          [vdso]
00574000-00587000 r-xp 00000000 fd:00
18109215   /usr/lib/libbonobo-activation.s o.4.0.0
00587000-00589000 rwxp 00013000 fd:00
18109215   /usr/lib/libbonobo-activation.s o.4.0.0
005a0000-005a2000 r-xp 00000000 fd:00 23791093   /lib/libutil-2.4.so
005a2000-005a3000 r-xp 00001000 fd:00 23791093   /lib/libutil-2.4.so
005a3000-005a4000 rwxp 00002000 fd:00 23791093   /lib/libutil-2.4.so
005eb000-00647000 r-xp 00000000 fd:00
18113346   /usr/lib/libsqlite3.so.0.8.6
00647000-00649000 rwxp 0005b000 fd:00
18113346   /usr/lib/libsqlite3.so.0.8.6
006ea000-006f5000 r-xp 00000000 fd:00
18113366   /usr/lib/libavahi-common.so.3.3 .0
006f5000-006f6000 rwxp 0000a000 fd:00
18113366   /usr/lib/libavahi-common.so.3.3 .0
00716000-00720000 r-xp 00000000 fd:00
18113348   /usr/lib/libesd.so.0.2.36
00720000-00721000 rwxp 00009000 fd:00
18113348   /usr/lib/libesd.so.0.2.36
00723000-0074a000 r-xp 00000000 fd:00
18098848   /usr/lib/libaudiofile.so.0.0.2
0074a000-0074e000 rwxp 00026000 fd:00
18098848   /usr/lib/libaudiofile.so.0.0.2
00750000-00783000 r-xp 00000000 fd:00
18109203   /usr/lib/libgconf-2.so.4.1.0
00783000-00786000 rwxp 00033000 fd:00
18109203   /usr/lib/libgconf-2.so.4.1.0
00788000-007ec000 r-xp 00000000 fd:00
18109940   /usr/lib/libgnomevfs-2.so.0.140 0.0
007ec000-007f1000 rwxp 00064000 fd:00
18109940   /usr/lib/libgnomevfs-2.so.0.140 0.0
00839000-00842000 r-xp 00000000 fd:00
23789609   /lib/libnss_files-2.4.so
00842000-00843000 r-xp 00008000 fd:00
23789609   /lib/libnss_files-2.4.so
00843000-00844000 rwxp 00009000 fd:00
23789609   /lib/libnss_files-2.4.so
00868000-00877000 r-xp 00000000 fd:00
18113368   /usr/lib/libavahi-client.so.3.1 .1
00877000-00878000 rwxp 0000e000 fd:00
18113368   /usr/lib/libavahi-client.so.3.1 .1
00895000-008c7000 r-xp 00000000 fd:00
18108149   /usr/lib/libebook-1.2.so.5.2.1
008c7000-008cb000 rwxp 00031000 fd:00
18108149   /usr/lib/libebook-1.2.so.5.2.1
008cb000-0099c000 r-xp 00000000 fd:00 23791074   /lib/libasound.so.2.0.0
0099c000-009a1000 rwxp 000d0000 fd:00 23791074   /lib/libasound.so.2.0.0
009ad000-009b0000 r-xp 00000000 fd:00 18113388   /usr/lib/libplds4.so
009b0000-009b1000 rwxp 00002000 fd:00 18113388   /usr/lib/libplds4.so
009b3000-009b7000 r-xp 00000000 fd:00 18113389   /usr/lib/libplc4.so
009b7000-009b8000 rwxp 00003000 fd:00 18113389   /usr/lib/libplc4.so
00a2d000-00a62000 r-xp 00000000 fd:00 18093352   /usr/lib/libnspr4.so
00a62000-00a63000 rwxp 00035000 fd:00 18093352   /usr/lib/libnspr4.so
00a63000-00a65000 rwxp 00a63000 00:00 0
00a7a000-00ba6000 r-xp 00000000 fd:00 23791069   /lib/libc-2.4.so
00ba6000-00ba9000 r-xp 0012b000 fd:00 23791069   /lib/libc-2.4.so
00ba9000-00baa000 rwxp 0012e000 fd:00 23791069   /lib/libc-2.4.so
00baa000-00bad000 rwxp 00baa000 00:00 0
00baf000-00bd2000 r-xp 00000000 fd:00 23791072   /lib/libm-2.4.so
00bd2000-00bd3000 r-xp 00022000 fd:00 23791072   /lib/libm-2.4.so
00bd3000-00bd4000 rwxp 00023000 fd:00 23791072   /lib/libm-2.4.so
00bd6000-00bd8000 r-xp 00000000 fd:00 23791071   /lib/libdl-2.4.so
00bd8000-00bd9000 r-xp 00001000 fd:00 23791071   /lib/libdl-2.4.so
00bd9000-00bda000 rwxp 00002000 fd:00 23791071   /lib/libdl-2.4.so
00bdc000-00bee000 r-xp 00000000 fd:00 18113312   /usr/lib/libz.so.1.2.3
00bee000-00bef000 rwxp 00011000 fd:00 18113312   /usr/lib/libz.so.1.2.3
00bf1000-00c82000 r-xp 00000000 fd:00
18092132   /usr/lib/libglib-2.0.so.0.1000. 2
00c82000-00c83000 rwxp 00091000 fd:00
18092132   /usr/lib/libglib-2.0.so.0.1000. 2
00ccd000-00cdf000 r-xp 00000000 fd:00
18100054   /usr/local/lib/libosengine.so.0 .0.0
00cdf000-00ce0000 rwxp 00011000 fd:00
18100054   /usr/local/lib/libosengine.so.0 .0.0
00d91000-00dcf000 r-xp 00000000 fd:00
18092190   /usr/lib/libgobject-2.0.so.0.10 00.2
00dcf000-00dd0000 rwxp 0003e000 fd:00
18092190   /usr/lib/libgobject-2.0.so.0.10 00.2
00de4000-00de7000 r-xp 00000000 fd:00
18094287   /usr/lib/libgmodule-2.0.so.0.10 00.2
00de7000-00de8000 rwxp 00002000 fd:00
18094287   /usr/lib/libgmodule-2.0.so.0.10 00.2
00dea000-00dfa000 r-xp 00000000 fd:00 23791070   /lib/libpthread-2.4.so
00dfa000-00dfb000 r-xp 0000f000 fd:00 23791070   /lib/libpthread-2.4.so
00dfb000-00dfc000 rwxp 00010000 fd:00 23791070   /lib/libpthread-2.4.so
00dfc000-00dfe000 rwxp 00dfc000 00:00 0
00f46000-00f47000 r-xp 00000000 fd:00
20414808   /usr/local/lib/opensync/formats /event.so
00f47000-00f48000 rwxp 00000000 fd:00
20414808   /usr/local/lib/opensync/formats /event.so
043b0000-043bb000 r-xp 00000000 fd:00
23791073   /lib/libgcc_s-4.1.0-20060304.so .1
043bb000-043bc000 rwxp 0000a000 fd:00
23791073   /lib/libgcc_s-4.1.0-20060304.so .1
044f8000-0461c000 r-xp 00000000 fd:00
18113313   /usr/lib/libxml2.so.2.6.23
0461c000-04624000 rwxp 00124000 fd:00
18113313   /usr/lib/libxml2.so.2.6.23
04624000-04625000 rwxp 04624000 00:00 0
0474c000-04775000 r-xp 00000000 fd:00 18113393   /usr/lib/libssl3.so
04775000-04776000 rwxp 00029000 fd:00 18113393   /usr/lib/libssl3.so
04776000-04777000 rwxp 04776000 00:00 0
04779000-047f5000 r-xp 00000000 fd:00 18113392   /usr/lib/libnss3.so
047f5000-047fa000 rwxp 0007b000 fd:00 18113392   /usr/lib/libnss3.so
047fc000-04822000 r-xp 00000000 fd:00 18113394   /usr/lib/libsmime3.so
04822000-04824000 rwxp 00026000 fd:00 18113394   /usr/lib/libsmime3.so
0487c000-048ca000 r-xp 00000000 fd:00 18113391   /usr/lib/libsoftokn3.so
048ca000-048ce000 rwxp 0004e000 fd:00 18113391   /usr/lib/libsoftokn3.so
06268000-06340000 r-xp 00000000 fd:00
18114243   /usr/lib/libedataserver-1.2.so. 7.0.1
06340000-06342000 rwxp 000d8000 fd:00
18114243   /usr/lib/libedataserver-1.2.so. 7.0.1
06344000-063e4000 r-xp 00000000 fd:00
18108166   /usr/lib/libecal-1.2.so.3.2.8
063e4000-063f3000 rwxp 0009f000 fd:00
18108166   /usr/lib/libecal-1.2.so.3.2.8
063f3000-063f6000 rwxp 063f3000 00:00 0
065b4000-065d1000 r-xp 00000000 fd:00
18108165   /usr/lib/libedata-book-1.2.so.2 .2.1
065d1000-065d4000 rwxp 0001d000 fd:00
18108165   /usr/lib/libedata-book-1.2.so.2 .2.1
065d6000-065fd000 r-xp 00000000 fd:00
18114246   /usr/lib/libedata-cal-1.2.so.1. 3.10
065fd000-06600000 rwxp 00026000 fd:00
18114246   /usr/lib/libedata-cal-1.2.so.1. 3.10
06be4000-06d03000 r-xp 00000000 fd:00
23789586   /lib/libcrypto.so.0.9.8a
06d03000-06d16000 rwxp 0011e000 fd:00
23789586   /lib/libcrypto.so.0.9.8a
06d16000-06d19000 rwxp 06d16000 00:00 0
08048000-0804d000 r-xp 00000000 fd:00
18107488   /usr/local/bin/msynctool
0804d000-0804e000 rw-p 00005000 fd:00
18107488   /usr/local/bin/msynctool
08e92000-08ef3000 rw-p 08e92000 00:00 0          [heap]
b4bfe000-b4bff000 ---p b4bfe000 00:00 0
b4bff000-b55ff000 rw-p b4bff000 00:00 0
b55ff000-b5600000 ---p b55ff000 00:00 0
b5600000-b6021000 rw-p b5600000 00:00 0
b6021000-b6100000 ---p b6021000 00:00 0
b6162000-b6163000 ---p b6162000 00:00 0
b6163000-b61a3000 rw-p b6163000 00:00 0
b61a3000-b61a4000 ---p b61a3000 00:00 0
b61a4000-b6ba4000 rw-p b61a4000 00:00 0
b6ba4000-b6ba5000 ---p b6ba4000 00:00 0
b6ba5000-b75a5000 rw-p b6ba5000 00:00 0
b75a5000-b75a6000 ---p b75a5000 00:00 0
b75a6000-b7faa000 rw-p b75a6000 00:00 0
b7fbb000-b7fbd000 rw-p b7fbb000 00:00 0
bf9a7000-bf9bd000 rw-p bf9a7000 00:00 0          [stack]
Aborted
[jas@talby ~]$

Re: [Opensync-users] help - h2200 familiar with evolution on fedora

[Jason G. <ju...@lo...>]

See my next post with different subject.  I'm getting the same pointer
error and stack trace under fedora core 5 when trying to sync evo &
file.

Jason.

On Wed, 2006-05-10 at 20:31 -0300, Marcos "Japa" Umino wrote:

> Hi
> 
> I'm trying to synchronize my h2200 with familiar 0.8.3/0.8.4-rc1 (it's
> the one were using at h2200-port) and I'm getting errors, at gpesync
> side.
>