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

Re: [Opensync-users] Trying to synchronize text messages (sms) to/from Nokia N80

[Brian J. <br...@do...>]

Daniel,

Thanks for getting back to me. I have not had a chance to try out the
patch, but I will when I get home (I'm at work).

Regarding the "PC Suite 2" profile. Nokia by default on their Series 60
version 3 phones (Nokia E/N-Series) have a default "PC Suite" sync profile
in Connectivity -> Sync. Unfortunately, this profile only allows you to
use SyncML over Bluetooth/USB to sync the contacts, notes and calendar
(todo in S60v3 is part of the calendar). If the user wants to synchronize
additional items -- the only other items are browser favorites -- which I
need to talk to you about when you get some free time, and text messages
"sms", then the user has to create another sync profile. In the profile
settings, there is an option to pick an identifier. This is how SyncML
determines which profile to use. I simply called it PC Suite 2.

- Brian

On Wed, January 2, 2008 5:28 am, Daniel Gollub wrote:
> On Wednesday 02 January 2008 08:10:55 Brian Johnson wrote:
>
>> With that said, when using the
>> syncml-obex-client command line program, I get the following output (I
>> assume this is good):
>>
>> $ syncml-obex-client -u 0 --identifier "PC Suite 2" --wbxml --sync
>> "text/x-vMessage" Messages
>> connection with device succeeded Received an Alert for the DS Server at
>> Messages: Type: 201, Last , Next
>> 20080102T065600Z
>> Just received a new session with ID 1
>> Received the DevInf
>> Session 1 reported final. flushing
>>
>
> Interesting. You changed the profile on your mobile to "PC Suite 2"
> right? Didn't know that there is a relation.. i wonder how determine the
> available profiles...
>
> Could you try --slow-sync instead of --sync as well .. this should get
> all message (not only the latest one). Just to proof that it's working...
>
>> I did notice that the phone responds when using the "text/x-vMessage"
>> mime type on syncml-obex-client, and I do not know if objtype = data,
>> objformat = plain corresponds to text/plain, but I somehow need to get
>> msynctool to use text/x-vMessage.
>
> Correct, currently there handling of this mimetype is missing. Actually
> we should provide another field (e.g. <mimetype>) and drop the <objtype>
> field. <objtype> isn't needed since the <objformat> is mapped to one
> objtype already (redundancy).
>
>
> Anyway, i just did an untested hack to just hardcode text/x-vMessage for
> <objformat> plain, for testing purposes.
>
>
> best regards, Daniel
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/___________________
> ____________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
>
>

[Opensync-users] We're fooling users currently

[Juha T. <Juh...@ik...>]

On Wednesday 02 January 2008 15:09:05 Daniel Gollub wrote:
> OpenSync 0.34 is experimental development and changed all over the place.

> Make sure you're using a ported version of Kitchensync for the OpenSync 0.3x 
> API ... which tries to run the discovery after configurating the group. 
> Currently we don't have any update process from 0.2x to 0.3x ... as i already 
> mentioned 0.3x is experimental and intended to be a development branch. There 

This is something that most users stumble nowdays. opensync.org
front page highlights list of versions - which gives an wrong impression 
that things are being polished, instead of being heavily broken and
under construction.

At the moment, there isn't really a working solution for nobody 
as 0.2x works only in some use cases and config combinations 
(yes, you can get quite a long list those in opensync).

So, there should be a big red warning box at the top of the page
stating the facts and telling end users to go away, come back
later. If you're a developer/willing to help in testing, here
are checkout + compilation instructions.

It's better to drive them away directly compared to having 
a lot of people to waste time over and over again to find 
out the current state in hard way. That pisses people off 
which nobody wants.

I'm not saying that we should loose testers actively but we should
put it out clearly and frankly, which isn't the case now.

Daniel, I'd like to hear your comments on this, do you agree?


Br,

Tuju


PS: I've saw a message that fedora maintainer is updating their pkgs.
-- 
Älä luota hattupäiseen autoilijaan.

Re: [Opensync-users] Trying to synchronize text messages (sms) to/from Nokia N80

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

On Wednesday 02 January 2008 08:10:55 Brian Johnson wrote:
> With that said, when using the
> syncml-obex-client command line program, I get the following output (I
> assume this is good):
>
> $ syncml-obex-client -u 0 --identifier "PC Suite 2" --wbxml --sync
> "text/x-vMessage" Messages
> connection with device succeeded
> Received an Alert for the DS Server at Messages: Type: 201, Last , Next
> 20080102T065600Z
> Just received a new session with ID 1
> Received the DevInf
> Session 1 reported final. flushing

Interesting. You changed the profile on your mobile to "PC Suite 2" right? 
Didn't know that there is a relation.. i wonder how determine the available 
profiles...

Could you try --slow-sync instead of --sync as well .. this should get all 
message (not only the latest one). Just to proof that it's working...

> I did notice that the phone responds when using the "text/x-vMessage" mime
> type on syncml-obex-client, and I do not know if objtype = data, objformat
> = plain corresponds to text/plain, but I somehow need to get msynctool to
> use text/x-vMessage.

Correct, currently there handling of this mimetype is missing. Actually we 
should provide another field (e.g. <mimetype>) and drop the <objtype> field. 
<objtype> isn't needed since the <objformat> is mapped to one objtype already 
(redundancy).

Anyway, i just did an untested hack to just hardcode text/x-vMessage for 
<objformat> plain, for testing purposes.

best regards,
Daniel

Re: [Opensync-users] Kitchensync doesn't work (update from 0.20 to 0.34)

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

On Wednesday 02 January 2008 13:02:15 Nicoco wrote:
> I've been using opensync 0.20 with kdepim and syncml plugin for some time
> now.
> Since the recent 0.34 update, nothing works.
> kitchensync now complains :

Which version of Kitchensync do you use?!

OpenSync 0.34 is experimental development and changed all over the place. The 
API changed al lot since 0.2x ... you need a ported Kitchensync version for 
the OpenSync 0.3x API. This is only the case for KDE4 and a special 
work-branch of KDE makes this possible... the default KDE3 is still intended 
for 0.2x..

>
> Error initializing Synchronization Engine for group "Nokia"
> No synchronizable objtype
>
> Clicking OK results in a "This engine was not in state initialized: 0" in
> the terminal

The group got never "discovered", this prodcure got introduced with the 
OpenSync 0.3x API. This got only slightly integrated so far in the 
Kitchensync compatible 0.3x versions... this is NOT (yet) integrated in the 
default KDE3 Kitchensync.... and those implementation are quite experimental 
as well since the discovery process is blocking and makes the UI not usable. 
There are some issues inside OpenSync 0.3x API to make "sane" use of a 
non-blocking osync_engine_discover call (on my todo list).

>
> Has anyone a clue about what's going on ?

Make sure you're using a ported version of Kitchensync for the OpenSync 0.3x 
API ... which tries to run the discovery after configurating the group. 
Currently we don't have any update process from 0.2x to 0.3x ... as i already 
mentioned 0.3x is experimental and intended to be a development branch. There 
are still the plans to change several configuration stored in ~/.opensync. If 
the latest changes about configuration are fixed, then we might provide 
update functionality. This isn't fixed yet, since OpenSync is still in a very 
early stage of development and we might just provide some "update scripts" 
instead of doing a proper update implementation from 0.2x to 0.3x. Since 0.2x 
didn't have any version information about the configuration, which makes 
out-of-the-box updating quite tricky. So for now the best way to got is just 
to drop/move your 0.2x ~/.opensync configuration... and experiment with a 
configuration from scratch.

Btw. did you build this from scratch? Or got this shipped by your distro?

best regards,
Daniel

[Opensync-users] Kitchensync doesn't work (update from 0.20 to 0

[Nicoco <tru...@gm...>]

Hi,

I've been using opensync 0.20 with kdepim and syncml plugin for some time
now.
Since the recent 0.34 update, nothing works.
kitchensync now complains :

Error initializing Synchronization Engine for group "Nokia"
No synchronizable objtype

Clicking OK results in a "This engine was not in state initialized: 0" in
the terminal

Has anyone a clue about what's going on ?

Thanks a lot.
-- 
View this message in context: http://www.nabble.com/Kitchensync-doesn%27t-work-%28update-from-0.20-to-0-tp14577217p14577217.html
Sent from the Opensync - User mailing list archive at Nabble.com.

[Opensync-users] Trying to synchronize text messages (sms) to/from Nokia N80

[Brian J. <br...@do...>]

I'm trying to synchronize my text messages (sms) to/from my Nokia N80. By
default, Nokia has a sync profile called "PC Suite". I've duplicated this,
changed the identifier to "PC Suite 2" and enabled text messages (SMS)
with the database name "Messages".

I upgraded all of the opensync stuff to version 0.35, which should allow
me to create custom objtype and objformat databases instead of the normal
<contacts_db> <notes_db> etc. With that said, when using the
syncml-obex-client command line program, I get the following output (I
assume this is good):

$ syncml-obex-client -u 0 --identifier "PC Suite 2" --wbxml --sync
"text/x-vMessage" Messages
connection with device succeeded
Received an Alert for the DS Server at Messages: Type: 201, Last , Next
20080102T065600Z
Just received a new session with ID 1
Received the DevInf
Session 1 reported final. flushing

However, when using msynctool, it comes up with error 67.

Relevant config files are here:

/home/brian/.opensync/group4/1/file-sync.conf

<?xml version="1.0"?>
<config>
<directory>
    <path>/home/brian/.nokia/n80/messages</path>
    <objtype>data</objtype>
    <objformat>plain</objformat>
  </directory>
</config>

/home/brian/.opensync/group4/2/

<?xml version="1.0"?>
<config>
  <!-- (Only for bluetooth) The bluetooth address if the bluetooth mode is
selected -->
  <bluetooth_address></bluetooth_address>

  <!-- (Only for bluetooth) The bluetooth channel to use. `sdptool browse
$MAC` to search for the correct channel -->
  <bluetooth_channel></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>PC Suite 2</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>5</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>0</recvLimit>

  <maxObjSize>0</maxObjSize>

  <database>
     <name>Messages</name>
     <objtype>data</objtype>
     <objformat>plain</objformat>
  </database>

</config>

I did notice that the phone responds when using the "text/x-vMessage" mime
type on syncml-obex-client, and I do not know if objtype = data, objformat
= plain corresponds to text/plain, but I somehow need to get msynctool to
use text/x-vMessage.

Any ideas? Or am I going about this all wrong?

- Brian

Re: [Opensync-users] documentation

[Tonus <to...@gm...>]

Le samedi 29 d=C3=A9cembre 2007, vous avez =C3=A9crit=C2=A0:
> > By the way, I can't manage to get the kitchensync files from the svn
> > with the indications of the opensync related page. And can't find it
> > homepage anymore.
>
> http://opensync.org/wiki/kitchensync
I thought there was something different, sorry.
> Work's for me ... make sure you checkout:
>
> svn co
> svn://anonsvn.kde.org/home/kde/branches/work/kitchensync-OpenSync0.30AP
>I kitchensync
>
It was my firewall : haden't realise that svn uses specific port.

Thanks for your help.
=2D-=20
Tonus_at_gmail_dot_com
http://da.tonus.webpage.free.fr/

Re: [Opensync-users] Problems with libsyncml

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

On Saturday 29 December 2007 14:06:32 li...@ba... wrote:
> I've used the latest version of libsyncml and tried the syncml-obex-client
> tool for testing. This showed the same behavior as opensync. Therefore I
> assume it might be a problem in libsyncml. In the following the debug
> output, with a self-compiled open-obex library.

I just had a quick look on the syncml log dumps. I guess following SyncML 
message generated by libsyncml is wrong (sent-1.xml):

<SyncBody>
    <Status>
        ...
        <SourceRef>Sony Ericss</SourceRef>
        <TargetRef>IMEI:xxxxxxxxxxxxxx</TargetRef>
       ....
    </Status>
    ....
</SyncBody>

Actually your identifier string should be in that context the <TargetRef/>, 
and the IMEI string in <SourceRef/>. Since the Status refers from a SyncML 
command which got emitted by the mobile. And for the mobile the Target is 
libsyncml ...

I'll review the commits to see when this bug got introduced... not quite sure 
if r263 is affected or not.

best regards,
Daniel

[Opensync-users] sync Nokia 6230/Evolution: sync does not complete when contact contains image, charset conversion fails

[Ulf M. <ulf...@gm...>]

I am using opensync+msynctool 0.34 from Debian/experimental to sync the
contact database of a Nokia 6230 cellphone (syncml-obex-client) with
Evolution 2.12.2 (Debian unstable; evo2-sync) via bluetooth. The group
configuration files are attached. Syncing was done via msynctool;
initially, the address database of the phone was empty.

The connection was established but the phone display went off after
showing a progress bar for a while. The normal phone menu appeared again
shortly afterwards, and the msynctool program seemed to hang. The last
lines of output were:

        ...
        Sent a entry 117 to member 1 (syncml-obex-client). Changetype
        ADDED
        contact sink of member 1 of type syncml-obex-client had an
        error: Command is too large
        Sent a entry 132 to member 1 (syncml-obex-client). Changetype
        ADDED
        Sent a entry 131 to member 1 (syncml-obex-client). Changetype
        ADDED
        Sent a entry 130 to member 1 (syncml-obex-client). Changetype
        ADDED
        Sent a entry 129 to member 1 (syncml-obex-client). Changetype
        ADDED
        Sent a entry 128 to member 1 (syncml-obex-client). Changetype
        ADDED
        Sent a entry 127 to member 1 (syncml-obex-client). Changetype
        ADDED
        Sent a entry 126 to member 1 (syncml-obex-client). Changetype
        ADDED
        Sent a entry 125 to member 1 (syncml-obex-client). Changetype
        ADDED
        Sent a entry 124 to member 1 (syncml-obex-client). Changetype
        ADDED

The phone had indeed received all contacts but one which had an image
attached. After removing the image, sync'ing worked. However, names
which contained letters with accents etc. were not displayed correctly.
Evolution runs within a session with UTF-8 locale, and opensync seems to
transmit two-byte characters to the phone, which is probably using a
single-byte character set. I found an older opensync mailing list
contribution stating that utf-8 cannot be converted correctly -- is that
still true?

I'd appreciate any suggestions how to fix the charset problem ... If you
need further information, please let me know.

Thanks! Ulf

-- 
 Ulf Mehlig    <ulf...@gm...>
-----------------------------------------------------------------------

[Opensync-users] Problems with libsyncml

[<li...@ba...>]

Hi,

I tried the latest version of opensync without success. The scenario was to 
syncronize the phone (syncml-obex-client) with the file system. The mobile 
phone only says: "Session failed Invalid server response". I tried bluetooth 
as well as usb connections.

I've tested two phones, which are probably quite the same: Sony Ericsson 750i 
and a W810i, both showed the same behavior.

I've used the latest version of libsyncml and tried the syncml-obex-client 
tool for testing. This showed the same behavior as opensync. Therefore I 
assume it might be a problem in libsyncml. In the following the debug output, 
with a self-compiled open-obex library.

./syncml-obex-client -u 0 --identifier "Sony Ericss" --sync text/x-vcard 
Contacts --dumpinfo --wbxml
Tx: 80 00 15 10 00 FF FF 46 00 0E 53 59 4E 43 4D 4C 2D 53 59 4E 43
Rx: A0 00 1A 10 00 10 00 CB 00 00 00 01 4A 00 0E 53 59 4E 43 4D 4C 2D 53 59 4E 
43
Tx: 82 00 A7 CB 00 00 00 01 42 00 20 61 70 70 6C 69 63 61 74 69 6F 6E 2F 76 6E 
64
Tx: 2E 73 79 6E 63 6D 6C 2B 77 62 78 6D 6C 00 C3 00 00 00 77 49 00 7A 02 9F 53 
6A
Tx: 00 6D 6C 71 03 31 2E 31 00 01 72 03 53 79 6E 63 4D 4C 2F 31 2E 31 00 01 65 
03
Tx: 31 00 01 5B 03 31 00 01 6E 57 03 2F 00 01 01connection with device 
succeeded
67 57 03 53 6F 6E 79 20 45 72 69
Tx: 63 73 73 00 01 01 01 6B 46 4B 03 31 00 01 4F 03 32 30 36 00 01 54 67 57 03 
43
Tx: 6F 6E 74 61 63 74 73 00 01 01 5A 00 01 53 03 74 65 78 74 2F 78 2D 76 63 61 
72
Tx: 64 00 01 01 01 01 00 00 12 01 01
Rx: A0 00 03
Tx: 83 00 28 CB 00 00 00 01 42 00 20 61 70 70 6C 69 63 61 74 69 6F 6E 2F 76 6E 
64
Tx: 2E 73 79 6E 63 6D 6C 2B 77 62 78 6D 6C 00
Rx: 90 01 4C C3 00 00 01 41 48 01 44 02 00 00 6A 1D 2D 2F 2F 53 59 4E 43 4D 4C 
2F
Rx: 2F 44 54 44 20 53 79 6E 63 4D 4C 20 31 2E 31 2F 2F 45 4E 6D 6C 71 03 31 2E 
31
Rx: 00 01 72 03 53 79 6E 63 4D 4C 2F 31 2E 31 00 01 65 03 31 00 01 5B 03 31 00 
01
Rx: 6E 57 03 53 6F 6E 79 20 45 72 69 63 73 73 00 01 01 67 57 03 49 4D 45 49 3A 
33
Rx: 35 36 35 35 33 30 30 39 32 30 32 35 37 31 00 01 01 5A 00 01 4C 03 36 30 30 
30
Rx: 00 01 01 01 00 00 6B 69 4B 03 31 00 01 5C 03 31 00 01 4C 03 30 00 01 4A 03 
53
Rx: 79 6E 63 48 64 72 00 01 6F 03 2F 00 01 68 03 53 6F 6E 79 20 45 72 69 63 73 
73
Rx: 00 01 4F 03 32 30 30 00 01 01 69 4B 03 32 00 01 5C 03 31 00 01 4C 03 31 00 
01
Rx: 4A 03 41 6C 65 72 74 00 01 68 03 43 6F 6E 74 61 63 74 73 00 01 4F 03 32 30 
30
Rx: 00 01 01 46 4B 03 33 00 01 4F 03 32 30 31 00 01 54 6E 57 03 43 6F 6E 74 61 
63
Rx: 74 73 00 01 01 67 57 03 43 6F 6E 74 61 63 74 73 00 01 01 5A 00 01 45 4A 03 
30
Rx: 00 01 4F 03 31 00 01 01 55 03 36 35 35 33 35 00 01 4D 49 03 33 32 37 30 31 
39
Rx: 36 35 00 01 48 03 34 39 39 00 01 01 01 01 01 00 00 12 01 01
Tx: 83 00 03
Rx: A0 00 06 49 00 03
Received an Alert for the DS Server at Contacts: Type: 201, Last 0, Next 1
Just received a new session with ID 1
Going to request the devinf
Session 1 reported final. flushing
Tx: 82 01 64 CB 00 00 00 01 42 00 20 61 70 70 6C 69 63 61 74 69 6F 6E 2F 76 6E 
64
Tx: 2E 73 79 6E 63 6D 6C 2B 77 62 78 6D 6C 00 C3 00 00 01 34 49 01 37 02 9F 53 
6A
Tx: 38 49 4D 45 49 3A 33 35 36 35 35 33 30 30 39 32 30 32 35 37 31 00 53 6F 6E 
79
Tx: 20 45 72 69 63 73 73 00 73 79 6E 63 6D 6C 3A 6D 65 74 69 6E 66 00 43 6F 6E 
74
Tx: 61 63 74 73 00 6D 6C 71 03 31 2E 31 00 01 72 03 53 79 6E 63 4D 4C 2F 31 2E 
31
Tx: 00 01 65 03 31 00 01 5B 03 32 00 01 6E 57 83 00 01 01 67 57 83 15 01 01 01 
6B
Tx: 69 4B 03 31 00 01 5C 03 31 00 01 4C 03 30 00 01 4A 03 53 79 6E 63 48 64 72 
00
Tx: 01 68 83 15 01 6F 83 00 01 4F 03 32 30 30 00 01 01 69 4B 03 32 00 01 5C 03 
31
Tx: 00 01 4C 03 33 00 01 4A 03 41 6C 65 72 74 00 01 54 4F 00 01 45 4F 03 31 00 
01
Tx: 01 01 01 00 00 68 83 2F 01 6F 83 2F 01 4F 03 32 30 30 00 01 01 46 4B 03 33 
00
Tx: 01 4F 03 32 30 36 00 01 54 6E 57 83 2F 01 01 67 57 83 2F 01 01 01 01 53 4B 
03
Tx: 34 00 01 5A 00 01 53 03 61 70 70 6C 69 63 61 74 69 6F 6E 2F 76 6E 64 2E 73 
79
Tx: 6E 63 6D 6C 2D 64 65 76 69 6E 66 2B 77 62 78 6D 6C 00 01 01 00 00 54 6E 57 
03
Tx: 2E 2F 64 65 76 69 6E 66 31 31 00 01 01 01 01 12 01 01
Rx: D0 00 03
Received an transport error: Request not successful: 0x50
Tx: 81 00 08 CB 00 00 00 01
Rx: A0 00 03
Didnt receive the devinf though it was requested

marc@A64-Ubuntu:~/opensync/build/bin$ ldd ./syncml-
syncml-http-client  syncml-http-server  syncml-obex-client
marc@A64-Ubuntu:~/opensync/build/bin$ ldd ./syncml-obex-client
        linux-gate.so.1 =>  (0xffffe000)
        libsyncml.so.0 => /home/marc/opensync/build/lib/libsyncml.so.0 
(0xb7ed7000)
        libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb7e2d000)
        libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xb7e29000)
        libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xb7e25000)
        libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xb7e20000)
        librt.so.1 => /lib/tls/i686/cmov/librt.so.1 (0xb7e17000)
        libxml2.so.2 => /usr/lib/libxml2.so.2 (0xb7cfa000)
        libbluetooth.so.2 => /usr/lib/libbluetooth.so.2 (0xb7ce8000)
        libwbxml2.so.0 => /usr/lib/libwbxml2.so.0 (0xb7cc8000)
        libsoup-2.2.so.8 => /usr/lib/libsoup-2.2.so.8 (0xb7c9c000)
        libgnutls.so.13 => /usr/lib/libgnutls.so.13 (0xb7c2c000)
        libopenobex.so.1 => /home/marc/opensync/build/lib/libopenobex.so.1 
(0xb7c22000)
        libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb7ae1000)
        /lib/ld-linux.so.2 (0xb7f27000)
        libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0xb7ac9000)
        libz.so.1 => /usr/lib/libz.so.1 (0xb7ab5000)
        libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0xb7a8e000)
        libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb7a6e000)
        libpopt.so.0 => /lib/libpopt.so.0 (0xb7a66000)
        libnsl.so.1 => /lib/tls/i686/cmov/libnsl.so.1 (0xb7a4e000)
        libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xb7a14000)
        libtasn1.so.3 => /usr/lib/libtasn1.so.3 (0xb79ff000)
        libgcrypt.so.11 => /usr/lib/libgcrypt.so.11 (0xb79ae000)
        libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0xb79aa000)
        libusb-0.1.so.4 => /lib/libusb-0.1.so.4 (0xb79a1000)

I've used different names of "Contacts" and for the Identifier, but nothing 
changed.

I've used libsyncml with opensync 0.34 in November and at that time it worked. 
Switching back to libsyncml revision 263 (probably the version I've used at 
that time) brought no success. The only difference is the computer and 
probably the installed version of Ubuntu.

Find attached the libsyncml log-files. If required, I can sent the trace 
files.

Best regards
Marc

[Opensync-users] documentation

[Tonus <to...@gm...>]

Hello,
I think the INSTALL and README files in the svn plugin directories (at=20
least for the file, kdepim and vformat plugins) are out to date.
It says to use ./configure etc, as it seems to use the cmake way.

By the way, I can't manage to get the kitchensync files from the svn with=20
the indications of the opensync related page. And can't find it homepage=20
anymore.

Thank you by advance.
=2D-=20
Tonus_at_gmail_dot_com
http://da.tonus.webpage.free.fr/

Re: [Opensync-users] can't compile opensync from svn

[Tonus <to...@gm...>]

> I'll change it to g_timeout_source_new() which should be available even
> for glib2 2.12. Milliseconds should be precise enough...

I did the change in my opensync/ipc/opensync_queue.c
and it went without errors.
Just worked fine :)

Thanks to Paul and Daniel.
=2D-=20
Tonus_at_gmail_dot_com
http://da.tonus.webpage.free.fr/

Re: [Opensync-users] can't compile opensync from svn

[Tonus <to...@gm...>]

Hello,
Le samedi 29 d=E9cembre 2007, Daniel Gollub a =E9crit=A0:
> Ooops, g_timeout_source_new_seconds() got introduced with glib2 2.14.
>
> http://library.gnome.org/devel/glib/unstable/glib-The-Main-Event-Loop.h
>tml#g-timeout-source-new-seconds
>
> I'll change it to g_timeout_source_new() which should be available even
> for glib2 2.12.
It would be great :)
Thank you.
=2D-=20
Tonus_at_gmail_dot_com
http://da.tonus.webpage.free.fr/

Re: [Opensync-users] can't compile opensync from svn

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

On Saturday 29 December 2007 01:39:22 Tonus wrote:
> > Sounds like you are using an older version of glib than OpenSync is
> > expecting. What version of glib do you have installed on your system?
>
> glib-1.2.10-i486-3
> glib2-2.12.12-i486-1
> I use linux slackware-12.0

Ooops, g_timeout_source_new_seconds() got introduced with glib2 2.14.

http://library.gnome.org/devel/glib/unstable/glib-The-Main-Event-Loop.html#g-timeout-source-new-seconds

I'll change it to g_timeout_source_new() which should be available even for 
glib2 2.12. Milliseconds should be precise enough...

best regards,
Daniel

Re: [Opensync-users] can't compile opensync from svn

[Tonus <to...@gm...>]

Hello,
=46irst, thank you for helping.
Le samedi 29 d=E9cembre 2007, Paul Eggleton a =E9crit=A0:
> Sounds like you are using an older version of glib than OpenSync is
> expecting. What version of glib do you have installed on your system?
glib-1.2.10-i486-3
glib2-2.12.12-i486-1
I use linux slackware-12.0
=2D-=20
Tonus_at_gmail_dot_com
http://da.tonus.webpage.free.fr/

Re: [Opensync-users] can't compile opensync from svn

[Paul E. <blu...@bl...>]

On Sat, 29 Dec 2007, Tonus wrote:
> >/path/to/build/opensync/libopensync.so: undefined reference to
>
> `g_timeout_source_new_seconds'

Sounds like you are using an older version of glib than OpenSync is expecting. 
What version of glib do you have installed on your system?

Cheers,
Paul

[Opensync-users] can't compile opensync from svn

[Tonus <to...@gm...>]

Hello,
I can't manage compiling the svn version with this new cmake manner.

Here is the first error after=20
cmake -DCMAKE_INSTALL_PREFIX=3D/usr/local /path/to/sources/ :
> -- Found Python: /usr/lib/python2.5/config/libpython2.5.a
> -- checking for one of the modules 'check'
> -- Could NOT find CHECK

then, after make :
> [ 54%] Building C object=20
opensync/CMakeFiles/opensync.dir/ipc/opensync_queue.o
> /path/to/sources/opensync/ipc/opensync_queue.c: In=20
function 'osync_queue_send_message_with_timeout':
> /path/to/sources/opensync/ipc/opensync_queue.c:994: warning:=20
initialization makes pointer from integer without a cast
> [ 56%] Building C object=20
opensync/CMakeFiles/opensync.dir/ipc/opensync_serializer.o
>Linking C executable osplugin
=2E..
>/path/to/build/opensync/libopensync.so: undefined reference to=20
`g_timeout_source_new_seconds'
>collect2: ld returned 1 exit status
>make[2]: *** [opensync/osplugin] Error 1
>make[1]: *** [opensync/CMakeFiles/osplugin.dir/all] Error 2
>make: *** [all] Error 2

If someone has a clue...
Thanks by advance.
=2D-=20
Tonus_at_gmail_dot_com
http://da.tonus.webpage.free.fr/

[Opensync-users] A new beginning in the New 2008 Year

[<fj...@sy...>]

Dance to the New 2008 Year tune
http://newyearwithlove.com/

Re: [Opensync-users] (no subject)

[Ryan V. <sim...@ya...>]

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

Ryan Voots wrote:
 > ok i managed to get a good backtrace, not sure what it means (haven't
> looked at the source)
> 

boy i'm just posting over and over to myself again
after installing the vformat plugins and kde-pim i'm able to synchronize
without a problem i'll add the phone and the settings to the wiki

- -------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Opensync-users mailing list
Ope...@li...
https://lists.sourceforge.net/lists/listinfo/opensync-users



- --
- -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
Updated: 2005-04-19
GCS/CM/M/S d-(--) s:+ a-->->>+>++>+++$>?$ C+++(++)>++++$ ULB+++(++)>++++$
P++++>++++$ L++++ E----(@) W+++ N++ o? K? w---(--) O-- !M V? PS+ PE Y++
PGP++(+++@) t+(++) 5 X+++(++@) R(+) !tv() DI++++ b+ D++ G++ e*()>++>++++$
h(*)>---- r++@>+++ !y?(**)
- ------END GEEK CODE BLOCK------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6-ecc01.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHdFT9URIHekb7KEARAuTEAJoDedhzXhkW6xi0PZcgcskH5XfTDACfR54a
0p/Ix8mTddps4fyCAmCk16g=
=h7Kz
-----END PGP SIGNATURE-----

Re: [Opensync-users] (no subject)

[Ryan V. <sim...@ya...>]

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

Ryan Voots wrote:

> 
> ok i've found out that the correct Identifier is "PC Suite Data Sync",
> and i've gotten it to start syncing, (works fine with
> syncml-obex-client) but then msynctool segfaults, so i'm recompiling
> with debugging symbols to see what i can find

ok i managed to get a good backtrace, not sure what it means (haven't
looked at the source)

#0  0x00002b8ec4cdfc10 in strlen () from /lib/libc.so.6
#1  0x00002b8ec4556b11 in osync_message_write_string (message=0x54cd10,
value=0x6c61423b3a4e0a0d <Address 0x6c61423b3a4e0a0d out of bounds>)
    at
/var/tmp/portage/app-pda/libopensync-0.35/work/libopensync-0.35/opensync/ipc/opensync_message.c:322
#2  0x00002b8ec5b7491d in marshal_file (input=0x568270
"BEGIN:VCARD\r\nVERSION:2.1\r\nN:;Ball\r\nTEL;PREF;VOICE:1234567890\r\nTEL;CELL;VOICE:7704231595\r\nEND:VCARD\r\n",
inpsize=<value optimized out>,
    message=0x54cd10, error=<value optimized out>) at
/var/tmp/portage/app-pda/libopensync-0.35/work/libopensync-0.35/formats/file.c:178
#3  0x00002b8ec4558eb8 in osync_marshal_data (message=0x54cd10,
data=0x539700, error=0x44807e78) at
/var/tmp/portage/app-pda/libopensync-0.35/work/libopensync-0.35/opensync/ipc/opensync_serializer.c:61
#4  0x00002b8ec4558f7a in osync_marshal_change (message=0x54cd10,
change=0x53f9b0, error=0x44807e78)
    at
/var/tmp/portage/app-pda/libopensync-0.35/work/libopensync-0.35/opensync/ipc/opensync_serializer.c:156
#5  0x00002b8ec453e507 in _osync_client_change_callback
(change=0x53f9b0, data=<value optimized out>)
    at
/var/tmp/portage/app-pda/libopensync-0.35/work/libopensync-0.35/opensync/client/opensync_client.c:215
#6  0x00002b8ec4536355 in osync_context_report_change (context=0x56e780,
change=0x53f9b0) at
/var/tmp/portage/app-pda/libopensync-0.35/work/libopensync-0.35/opensync/opensync_context.c:148
#7  0x00002b8ec5e7fa5d in ?? () from
/usr/lib64/opensync-1.0/plugins/syncml-plugin.so
#8  0x00002b8ec5ff57ba in smlDsSessionDispatch () from
/usr/lib/libsyncml.so.0
#9  0x00002b8ec5e7eac6 in ?? () from
/usr/lib64/opensync-1.0/plugins/syncml-plugin.so
#10 0x00002b8ec46b1051 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#11 0x00002b8ec46b183d in ?? () from /usr/lib/libglib-2.0.so.0
#12 0x00002b8ec46b1ae5 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#13 0x00002b8ec46dbc86 in ?? () from /usr/lib/libglib-2.0.so.0
#14 0x00002b8ec52ba135 in start_thread () from /lib/libpthread.so.0
#15 0x00002b8ec4d2c35d in clone () from /lib/libc.so.6
#16 0x0000000000000000 in ?? ()



- -------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Opensync-users mailing list
Ope...@li...
https://lists.sourceforge.net/lists/listinfo/opensync-users



- --
- -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
Updated: 2005-04-19
GCS/CM/M/S d-(--) s:+ a-->->>+>++>+++$>?$ C+++(++)>++++$ ULB+++(++)>++++$
P++++>++++$ L++++ E----(@) W+++ N++ o? K? w---(--) O-- !M V? PS+ PE Y++
PGP++(+++@) t+(++) 5 X+++(++@) R(+) !tv() DI++++ b+ D++ G++ e*()>++>++++$
h(*)>---- r++@>+++ !y?(**)
- ------END GEEK CODE BLOCK------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6-ecc01.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHdE5xURIHekb7KEARAsjqAJ4r+3lAJQ6KjJz4YAvc1VdAwhsx7QCfUNQG
WfbqYBvLkTlJg3bv4iBNLXw=
=dubp
-----END PGP SIGNATURE-----

Re: [Opensync-users] (no subject)

[Ryan V. <sim...@ya...>]

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

Ryan Voots wrote:
> i've been trying to get syncing setup for my phone with libsyncml, so
> far i haven't had much luck, i'm currently using libsyncml-0.4.5
.... snip ...

ok i've found out that the correct Identifier is "PC Suite Data Sync",
and i've gotten it to start syncing, (works fine with
syncml-obex-client) but then msynctool segfaults, so i'm recompiling
with debugging symbols to see what i can find


- -------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Opensync-users mailing list
Ope...@li...
https://lists.sourceforge.net/lists/listinfo/opensync-users



- --
- -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
Updated: 2005-04-19
GCS/CM/M/S d-(--) s:+ a-->->>+>++>+++$>?$ C+++(++)>++++$ ULB+++(++)>++++$
P++++>++++$ L++++ E----(@) W+++ N++ o? K? w---(--) O-- !M V? PS+ PE Y++
PGP++(+++@) t+(++) 5 X+++(++@) R(+) !tv() DI++++ b+ D++ G++ e*()>++>++++$
h(*)>---- r++@>+++ !y?(**)
- ------END GEEK CODE BLOCK------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6-ecc01.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHdEoPURIHekb7KEARAmdFAJ9oClu6SIecVrfqO6//sOPemSFvIACdH6t+
eNkQhPGUxwX3OGWHsC+0D5Y=
=YL6t
-----END PGP SIGNATURE-----

[Opensync-users] (no subject)

[Ryan V. <sim...@ya...>]

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

i've been trying to get syncing setup for my phone with libsyncml, so
far i haven't had much luck, i'm currently using libsyncml-0.4.5

this is the command i've tried, (with various changes, e.g. no wbxml,
playing with the identifier, and the uri name, this one SEEMS to me to
be the most success full, some others just seem to fail to connect)

i've got a couple of files from the trace not sure where i should put
them for the list to find them, if anyone has any ideas (the phone
appears to have two syncml channels, one calls itself "SyncML Client"
[channel 11], the other "Nokia SyncML Server" [channel 7], they both
give the same results as near as i can tell)

ryan@andromeda64 ~/phonesync $ syncml-obex-client --slow-sync
text/x-vcard Contacts --identifier "PC Suite" --wbxml -b
00:1C:D4:93:DB:22 11 --dumpinfo
connection with device succeeded
Received an Alert for the DS Server at Contacts: Type: 201, Last 0, Next 67
Slowsyncing
Just received a new session with ID 1
Received the DevInf
Session 1 reported final. flushing
Received an transport error: Request not successfull: 68
Send the output below to the libsyncml developers

========================================
Man: Nokia
Mod: Nokia 6126
FirmwareVersion: V 04.28
29-01-07
RM-126
(c) N..
SoftwareVersion: V 04.28
29-01-07
RM-126
(c) N..
HardwareVersion: 7102

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


- -- -----BEGIN GEEK CODE BLOCK----- Version: 3.12 Updated: 2005-04-19
GCS/CM/M/S d-(--) s:+ a-->->>+>++>+++$>?$ C+++(++)>++++$
ULB+++(++)>++++$ P++++>++++$ L++++ E----(@) W+++ N++ o? K? w---(--) O--
!M V? PS+ PE Y++ PGP++(+++@) t+(++) 5 X+++(++@) R(+) !tv() DI++++ b+ D++
G++ e*()>++>++++$ h(*)>---- r++@>+++ !y?(**) ------END GEEK CODE
BLOCK------
- --
- -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
Updated: 2005-04-19
GCS/CM/M/S d-(--) s:+ a-->->>+>++>+++$>?$ C+++(++)>++++$ ULB+++(++)>++++$
P++++>++++$ L++++ E----(@) W+++ N++ o? K? w---(--) O-- !M V? PS+ PE Y++
PGP++(+++@) t+(++) 5 X+++(++@) R(+) !tv() DI++++ b+ D++ G++ e*()>++>++++$
h(*)>---- r++@>+++ !y?(**)
- ------END GEEK CODE BLOCK------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6-ecc01.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHdAq1URIHekb7KEARAm2aAKCQv0khUAK90jYJgA+vtmV/UXUdZgCfTSev
0K85VXo1ZnX3Hymvzkm2j1w=
=o0Ff
-----END PGP SIGNATURE-----

Re: [Opensync-users] Sync from phone?

[Sebastian V. <seb...@gm...>]

On Dec 27, 2007 2:48 PM, Ilpo Nyyss=F6nen <in...@ik...> wrote:

> > That's how i used to do it at least. I start ActiveSync
>

Whoops :)  I (wrongly) thought you had a Windows CE based device. I'm sorry=
,
i don't know anything about other devices.

S.

Re: [Opensync-users] Sync from phone?

[<in...@ik...>]

"Sebastian Vieira" <seb...@gm...> writes:

> On Dec 27, 2007 8:22 AM, Ilpo Nyyssönen <in...@ik...> wrote:
>
>>
>> Well, I could buy bluetooth, but that would still require starting the
>> sync from the computer side.
>>
>
> If you connect via bluetooth you can initiate the sync on your device.

Well, I would prefer using WLAN / 3G as then I could also sync while on
the road. I also really do not have bluetooth connectivity in my
computers currently so I would need to buy something. Somehow it feels
silly as I already can use WLAN in most of the cases.

And what program in the computer side would do it? How would it start
when the computer reboots?

> That's how i used to do it at least. I start ActiveSync

What is that?

> and then go to the menu and choose 'Connect via Bluetooth'.

No, this does not sound like an option. Even doing it with python sounds
better alternative.

-- 
Ilpo Nyyssönen # biny # /* :-) */

Re: [Opensync-users] Sync from phone?

[Sebastian V. <seb...@gm...>]

On Dec 27, 2007 8:22 AM, Ilpo Nyyss=F6nen <in...@ik...> wrote:

>
> Well, I could buy bluetooth, but that would still require starting the
> sync from the computer side.
>

If you connect via bluetooth you can initiate the sync on your device.
That's how i used to do it at least. I start ActiveSync and then go to the
menu and choose 'Connect via Bluetooth'.

Sebastian