9:47 a.m.
Hello,
I'm trying to use syncevolution http server to sync may Android phone
(Nexus S) to my Evolution backend. On the Nexus I use the Funambol
SyncML client for Android. I'm using Ubuntu 11.10 distribution and I've
compiled version 1.2.2 of syncevolution using configuration:
./configure --prefix=/usr --enable-gui --enable-dbus-service
--disable-ecal --disable-ebook --disable-shared
I've tried following various HOWTO:s to no avail. From the mailing list
archives I've gatherd, that this one:
http://syncevolution.org/wiki/synchronizing-evolution-http-howto
should be the up-to-date one. Is this correct?
Anyhow, when I try to sync my phone, using a minimal config from the
HOWTO, I get the following:
jpahka@laptop:~$ rm -fr .config/syncevolution
jpahka@laptop:~$ syncevolution --configure --template SyncEvolution_Client \
--sync-property remoteDeviceId=fac-355031040909281 \
--sync-property username= \
--sync-property password= \
--source-property addressbook/uri=contacts \
nexus
jpahka@laptop:~$
jpahka@laptop:~$ syncevo-http-server http://127.0.0.1:9000
[INFO] syncevo-http: new SyncML session for 192.168.10.52
[INFO] sync: matched deviceID fac-355031040909281 against config nexus
(/home/jpahka/.config/syncevolution/default/peers/nexus)
[INFO] sync: todo: inactive
[INFO] sync: memo: inactive
[INFO] sync: addressbook: inactive
[INFO] sync: calendar: inactive
[ERROR] sync: error code from SyncEvolution fatal error (local, status
10500): no sources active, check configuration
[INFO] sync: creating complete data backup after sync (enabled with
dumpData and needed for printChanges)
[INFO] sync:
[INFO] sync: Synchronization failed, see
/home/jpahka/.cache/syncevolution/nexus-2012-02-15-11-00/syncevolution-log.html
for details.
[INFO] sync:
Changes applied during synchronization:
[INFO] sync:
+---------------|-----------------------|-----------------------|-CON-+
[INFO] sync: | | LOCAL |
REMOTE | FLI |
[INFO] sync: | Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL |
ERR | CTS |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: | start Wed Feb 15 11:00:49 2012, duration
0:00min |
[INFO] sync: | fatal error (local, status
10500) |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: First ERROR encountered: error code from SyncEvolution
fatal error (local, status 10500): no sources active, check configuration
[INFO] sync:
And indeed, there seems to be no sources active in the configuration.
Now, If I try to activate by editing the config, and try again:
jpahka@laptop:~$ nano
.config/syncevolution/default/peers/nexus/sources/addressbook/config.ini
replace the following: sync = disabled -> sync = refresh-from-server
jpahka@laptop:~$ syncevo-http-server http://127.0.0.1:9000
[INFO] syncevo-http: new SyncML session for 192.168.10.52
[INFO] sync: matched deviceID fac-355031040909281 against config nexus
(/home/jpahka/.config/syncevolution/default/peers/nexus)
[INFO] sync: todo: inactive
[INFO] sync: memo: inactive
[ERROR] sync: error code from SyncEvolution fatal error (local, status
10500): addressbook: backend 'addressbook' not supported or not
correctly configured (databaseFormat '', syncFormat '')
[INFO] sync: creating complete data backup after sync (enabled with
dumpData and needed for printChanges)
[INFO] sync:
[INFO] sync: Synchronization failed, see
/home/jpahka/.cache/syncevolution/nexus-2012-02-15-11-06/syncevolution-log.html
for details.
[INFO] sync:
Changes applied during synchronization:
[INFO] sync:
+---------------|-----------------------|-----------------------|-CON-+
[INFO] sync: | | LOCAL |
REMOTE | FLI |
[INFO] sync: | Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL |
ERR | CTS |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: | start Wed Feb 15 11:06:34 2012, duration
0:00min |
[INFO] sync: | fatal error (local, status
10500) |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: First ERROR encountered: error code from SyncEvolution
fatal error (local, status 10500): addressbook: backend 'addressbook'
not supported or not correctly configured (databaseFormat '', syncFormat
'')
[INFO] sync:
I'm obviously doing something wrong, but I don't know what to try out
next. How do I need to config the addressbook backend?
Thanks in advance,
Juhis
10:16 a.m.
On Wed, 2012-02-15 at 11:47 +0200, Juha Pahkala wrote:
I'm trying to use syncevolution http server to sync may Android
phone
(Nexus S) to my Evolution backend. On the Nexus I use the Funambol
SyncML client for Android.
Beware that previous attempts to sync with that client failed because of
SyncML protocol violations in the client. It seemed to be written
specifically for the Funambol server. It might be better now.
Your problem however is something else.
I'm using Ubuntu 11.10 distribution and I've
compiled version 1.2.2 of syncevolution using configuration:
./configure --prefix=/usr --enable-gui --enable-dbus-service
--disable-ecal --disable-ebook --disable-shared
I've tried following various HOWTO:s to no avail. From the mailing list
archives I've gatherd, that this one:
http://syncevolution.org/wiki/synchronizing-evolution-http-howto
should be the up-to-date one. Is this correct?
No. It's the one "to keep a phone in sync with Evolution". It's based
on
the assumption that you are using Evolution Data Server, which you
explicitly disabled.
I know that this can be confusing, so the HOWTO above explicitly says
"Setting up SyncEvolution as such an intermediary on an Internet server
is explained in another HOWTO":
http://syncevolution.org/wiki/http-server-howto
Do you have a suggestion how such a misunderstanding can be avoid in the
future?
Anyhow, when I try to sync my phone, using a minimal config from the
HOWTO, I get the following:
jpahka@laptop:~$ rm -fr .config/syncevolution
jpahka@laptop:~$ syncevolution --configure --template SyncEvolution_Client \
> --sync-property remoteDeviceId=fac-355031040909281 \
> --sync-property username= \
> --sync-property password= \
> --source-property addressbook/uri=contacts \
> nexus
The key difference in the HOWTOs is that the configuration you are
quoting here implicitly uses the backend=addressbook, which doesn't work
without the EDS backend. Please have a look at the other HOWTO, it shows
how to set up the file backend instead.
jpahka@laptop:~$
jpahka@laptop:~$ syncevo-http-server http://127.0.0.1:9000
[INFO] syncevo-http: new SyncML session for 192.168.10.52
[INFO] sync: matched deviceID fac-355031040909281 against config nexus
(/home/jpahka/.config/syncevolution/default/peers/nexus)
[INFO] sync: todo: inactive
[INFO] sync: memo: inactive
[INFO] sync: addressbook: inactive
[INFO] sync: calendar: inactive
[...]
And indeed, there seems to be no sources active in the configuration.
I think that's a side effect of not having a functional backend for
these sources. They are not activated unless that check succeeds.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
12:17 p.m.
This is a copy of the message I replied to Patrick, with the difference
that the attached log file is not included in this mail, because it is
too big. If anybody is interested in the log file, please let me know
and I'll send it to private mail.
Hello Patrick,
Thanks for your quick response and help. Really appreciated.
> I'm trying to use syncevolution http server to sync may
Android phone
> (Nexus S) to my Evolution backend. On the Nexus I use the Funambol
> SyncML client for Android.
Beware that previous attempts to sync with that client failed because of
SyncML protocol violations in the client. It seemed to be written
specifically for the Funambol server. It might be better now.
Ok. The version of the Funambol Client I'm using is 10.0.8, which is the
latest one as far as I can tell. I've used a local Funambol server in
the past, and I really don't want to go there again if at all possible,
it's no fun.
Do you have a suggestion how such a misunderstanding can be avoid in the
future?
Well, not really. Reading only the two wiki pages, it's relatively clear
what they mean. I guess I got confused with all the different HOWTOS I
was reading. The thing I'm after is just syncing my phon with a local
EDS. What I did is, I compiled syncevolution again with the following
configure:
./configure --prefix=/usr --enable-gui --enable-dbus-service
And after that did as below, and now perhaps hitting the problems you
mentioned earlier...
jpahka@laptop:~$ rm -fr .config/syncevolution
jpahka@laptop:~$ syncevolution --configure --template
SyncEvolution_Client \
--sync-property remoteDeviceId=fac-355031040909281 \
--sync-property username= \
--sync-property password= \
--source-property addressbook/uri=contacts \
nexus
jpahka@laptop:~$ syncevo-http-server http://127.0.0.1:9000
[INFO] syncevo-http: new SyncML session for 192.168.10.52
[INFO] sync: matched deviceID fac-355031040909281 against config nexus
(/home/jpahka/.config/syncevolution/default/peers/nexus)
[INFO] syncevo-http: new SyncML session for 192.168.10.52
[INFO] sync: matched deviceID fac-355031040909281 against config nexus
(/home/jpahka/.config/syncevolution/default/peers/nexus)
[INFO] sync: creating complete data backup after sync (enabled with
dumpData and needed for printChanges)
[INFO] sync:
[INFO] sync: Synchronization failed, see
/home/jpahka/.cache/syncevolution/nexus-2012-02-15-12-52/syncevolution-log.html
for details.
[INFO] sync:
Changes applied during synchronization:
[INFO] sync:
+---------------|-----------------------|-----------------------|-CON-+
[INFO] sync: | | LOCAL |
REMOTE | FLI |
[INFO] sync: | Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL |
ERR | CTS |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: | addressbook | 0 | 0 | 0 | 0 | 0 | 0 | 0
| 0 | 0 |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: | calendar | 0 | 0 | 0 | 0 | 0 | 0 | 0
| 0 | 0 |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: | memo | 0 | 0 | 0 | 0 | 0 | 0 | 0
| 0 | 0 |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: | todo | 0 | 0 | 0 | 0 | 0 | 0 | 0
| 0 | 0 |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: | start Wed Feb 15 12:52:58 2012, duration
0:09min |
[INFO] sync: | aborted on behalf of user (local, status
20017) |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync:
I've attached the log file to thi mail, compressed.
Is it so, that the Client still doesn't play ball?
br, juhis
On 02/15/2012 12:16 PM, Patrick Ohly wrote:
On Wed, 2012-02-15 at 11:47 +0200, Juha Pahkala wrote:
> I'm trying to use syncevolution http server to sync may Android phone
> (Nexus S) to my Evolution backend. On the Nexus I use the Funambol
> SyncML client for Android.
Beware that previous attempts to sync with that client failed because of
SyncML protocol violations in the client. It seemed to be written
specifically for the Funambol server. It might be better now.
Your problem however is something else.
> I'm using Ubuntu 11.10 distribution and I've
> compiled version 1.2.2 of syncevolution using configuration:
>
> ./configure --prefix=/usr --enable-gui --enable-dbus-service
> --disable-ecal --disable-ebook --disable-shared
>
> I've tried following various HOWTO:s to no avail. From the mailing list
> archives I've gatherd, that this one:
>
> http://syncevolution.org/wiki/synchronizing-evolution-http-howto
>
> should be the up-to-date one. Is this correct?
No. It's the one "to keep a phone in sync with Evolution". It's based
on
the assumption that you are using Evolution Data Server, which you
explicitly disabled.
I know that this can be confusing, so the HOWTO above explicitly says
"Setting up SyncEvolution as such an intermediary on an Internet server
is explained in another HOWTO":
http://syncevolution.org/wiki/http-server-howto
Do you have a suggestion how such a misunderstanding can be avoid in the
future?
> Anyhow, when I try to sync my phone, using a minimal config from the
> HOWTO, I get the following:
>
> jpahka@laptop:~$ rm -fr .config/syncevolution
> jpahka@laptop:~$ syncevolution --configure --template SyncEvolution_Client \
> > --sync-property remoteDeviceId=fac-355031040909281 \
> > --sync-property username= \
> > --sync-property password= \
> > --source-property addressbook/uri=contacts \
> > nexus
The key difference in the HOWTOs is that the configuration you are
quoting here implicitly uses the backend=addressbook, which doesn't work
without the EDS backend. Please have a look at the other HOWTO, it shows
how to set up the file backend instead.
> jpahka@laptop:~$
> jpahka@laptop:~$ syncevo-http-server http://127.0.0.1:9000
>
> [INFO] syncevo-http: new SyncML session for 192.168.10.52
> [INFO] sync: matched deviceID fac-355031040909281 against config nexus
> (/home/jpahka/.config/syncevolution/default/peers/nexus)
> [INFO] sync: todo: inactive
> [INFO] sync: memo: inactive
> [INFO] sync: addressbook: inactive
> [INFO] sync: calendar: inactive
[...]
> And indeed, there seems to be no sources active in the configuration.
I think that's a side effect of not having a functional backend for
these sources. They are not activated unless that check succeeds.
1:34 p.m.
On Wed, 2012-02-15 at 14:17 +0200, Juha Pahkala wrote:
> Do you have a suggestion how such a misunderstanding can be
avoid in the
> future?
>
Well, not really. Reading only the two wiki pages, it's relatively
clear what they mean.
It might be worth mentioning in the "prerequisites" part which features
the SyncEvolution binary has to support.
BTW, why did you decide to compile your own binaries instead of using
the apt repos? Those should work on your Ubuntu installation.
I guess I got confused with all the different HOWTOS I was reading.
The thing I'm after is just syncing my phon with a local EDS. What I
did is, I compiled syncevolution again with the following configure:
./configure --prefix=/usr --enable-gui --enable-dbus-service
And after that did as below, and now perhaps hitting the problems you
mentioned earlier...
No, there's still a configuration problem.
The server log shows that the phone is trying to sync against "card",
which is not a know source on the server.
[2012-02-15 12:56:09.545] - Processing Alert Item (code=200), Source='contacts',
Target='card'
[2012-02-15 12:56:09.545] Determined relative, identifying URI (w/o CGI): card
–
[2012-02-15 12:56:09.545] 'issue' - issuing command,
Cmd=Status [--][++] [->end] [->enclosing]
* [2012-02-15 12:56:09.545] Command 'Status': is 0-th counted cmd,
cmdsize(+tags needed to end msg)=179, available=64809
(maxfree=295267, freeaftersend=295088,
notUsableBufferBytes()=230458)
* [2012-02-15 12:56:09.545] WARNING: Non-OK Status 404 returned to
remote!
You can add "card" as an alias for "addressbook".
jpahka@laptop:~$ rm -fr .config/syncevolution
jpahka@laptop:~$ syncevolution --configure --template
SyncEvolution_Client \
> --sync-property remoteDeviceId=fac-355031040909281 \
> --sync-property username= \
> --sync-property password= \
> --source-property addressbook/uri=contacts \
> nexus
Use "card" instead of "contacts " above, or update your existing
config:
syncevolution --configure uri=card nexus addressbook
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
7:51 p.m.
On 02/15/2012 03:34 PM, Patrick Ohly wrote:
It might be worth mentioning in the "prerequisites" part
which features
the SyncEvolution binary has to support.
Yep, that would be helpful
BTW, why did you decide to compile your own binaries instead of using
the apt repos? Those should work on your Ubuntu installation.
Well, as I said, I tried all kinds of things to get it to work.
Compiling the latest stable version was one of them. My background with
syncevolution has been with a Nokia phones, and everything has always
worked out of the box with them. With Android, this has been a bit more
involved...
No, there's still a configuration problem.
The server log shows that the phone is trying to sync against "card",
which is not a know source on the server.
You can add "card" as an alias for "addressbook".
Use "card" instead of "contacts " above, or update your existing
config: syncevolution --configure uri=card nexus addressbook
This worked out. I can confirm that the first sync, when the phone
contact list is empty, works out fine with the funambol client 10.0.8,
and uri=card for addressbook on a Nexus S phone.
The next one, involving a comparison, doesn't work however. This is what
I get:
[INFO] syncevo-http: new SyncML session for 192.168.10.52
[INFO] sync: /usr/libexec/syncevo-dbus-server: ready to run
[INFO] sync: matched deviceID fac-355031040909281 against config nexus
(/home/jpahka/.config/syncevolution/default/peers/nexus)
[INFO] sync: addressbook: starting first time sync, two-way
[INFO] sync: creating complete data backup before sync (enabled with
dumpData and needed for printChanges)
[INFO] sync: Local data changes to be applied during synchronization:
[INFO] sync: *** addressbook ***
[INFO] sync: Comparison was impossible.
[INFO] sync:
[INFO] sync: addressbook: started
[INFO] sync: addressbook: first time sync done unsuccessfully
[ERROR] sync: SML (or SAN) error processing incoming message (local,
status 20007)
[INFO] sync: creating complete data backup after sync (enabled with
dumpData and needed for printChanges)
[INFO] sync:
[INFO] sync: Synchronization failed, see
/home/jpahka/.cache/syncevolution/nexus-2012-02-15-21-19/syncevolution-log.html
for details.
[INFO] sync:
Changes applied during synchronization:
[INFO] sync:
+---------------|-----------------------|-----------------------|-CON-+
[INFO] sync: | | LOCAL |
REMOTE | FLI |
[INFO] sync: | Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL |
ERR | CTS |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: | addressbook | 0 | 0 | 0 | 0 | 0 | 0 | 0
| 0 | 0 |
[INFO] sync: | slow, 0 KB sent by client, 0 KB
received |
[INFO] sync: | item(s) in database backup: 378 before sync, 378 after
it |
[INFO] sync: |SML (or SAN) error processing incoming message (local,
status 20007) |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: | calendar | 0 | 0 | 0 | 0 | 0 | 0 | 0
| 0 | 0 |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: | memo | 0 | 0 | 0 | 0 | 0 | 0 | 0
| 0 | 0 |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: | todo | 0 | 0 | 0 | 0 | 0 | 0 | 0
| 0 | 0 |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: | start Wed Feb 15 21:19:06 2012, duration
0:17min |
[INFO] sync: |SML (or SAN) error processing incoming message (local,
status 20007) |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: First ERROR encountered: SML (or SAN) error processing
incoming message (local, status 20007)
[INFO] sync:
Data modified locally during synchronization:
[INFO] sync: *** addressbook ***
[INFO] sync: no changes
[INFO] sync:
I will again send the log file privately to you Patrick, since it's big
again.
Calendar syncing I can't say much about, since apparently my Evolution
calendar is somehow screwed. My calendar.ics file is empty, and I've
seen that this has come up previously on syncevolution list. Why it's
empty, I don't know.
Anyhow, the correct uri for calendar entries on this phone is: uri=event
Thank you Patrick for your help, now I at least have my old entries in
the phone. Thank You.
br, juhis
3:57 p.m.
On Wed, 2012-02-15 at 21:51 +0200, Juha Pahkala wrote:
On 02/15/2012 03:34 PM, Patrick Ohly wrote:
> It might be worth mentioning in the "prerequisites" part which features
> the SyncEvolution binary has to support.
Yep, that would be helpful
Added.
This worked out. I can confirm that the first sync, when the phone
contact list is empty, works out fine with the funambol client 10.0.8,
and uri=card for addressbook on a Nexus S phone.
The next one, involving a comparison, doesn't work however. This is what
I get:
[...]
[INFO] sync: |SML (or SAN) error processing incoming message (local,
status 20007) |
You log shows that this is the same problem reported before:
http://lists.syncevolution.org/pipermail/syncevolution/2011-September/002...
[2012-02-15 21:19:18.880] ===> smlProcessData failed, returned 0x200B
I guess I'll have to install the app myself and try it out locally.
Debugging this further will require recompiling SyncEvolution to get
more debug information out of the libsmltk library.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
8:20 p.m.
On Fri, 2012-02-17 at 16:57 +0100, Patrick Ohly wrote:
You log shows that this is the same problem reported before:
http://lists.syncevolution.org/pipermail/syncevolution/2011-September/002...
[2012-02-15 21:19:18.880] ===> smlProcessData failed, returned 0x200B
I guess I'll have to install the app myself and try it out locally.
Debugging this further will require recompiling SyncEvolution to get
more debug information out of the libsmltk library.
I've installed the Funambol app 10.0.8 on an HTC Desire. I can't
reproduce the smlProcessData error. Sending a new contact worked, both
ways. I have not enabled any other data source.
What I see instead is that the Funambol app doesn't properly respond to
all SyncML commands. That has the effect that the server keeps the
session open:
[2012-02-17 21:01:55.757] - Not yet received status for command 'Put', (outgoing
MsgID=1, CmdID=3)
[2012-02-17 21:01:55.757] - Not yet received REQUIRED status for command 'Get',
(outgoing MsgID=1, CmdID=5)
[2012-02-17 21:01:55.757] - Not yet received status for command 'SyncHdr',
(outgoing MsgID=3, CmdID=0)
[2012-02-17 21:01:55.757] SESSION CANNOT END - Not yet received REQUIRED status for some
of 3 commands
The session then has to be aborted, which causes it to end with a local
400 status code. Not nice, but seems to work otherwise. Hmm, I always
encounter a slow sync. I haven't checked whether that is a side effect
of the 400 error.
My host side is Debian Testing, 64 bit, with SyncEvolution 1.2.2 from
syncevolution.org. I was using plain http.
As I can't replicate the problem, someone else will have to provide more
log files. Can someone set the loglevel to 5 in the SyncEvolution config
for the phone and send me the entire session directory, including the
syncevolution-log.html and the message dump files?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
9:17 a.m.
Hi Patrick,
I was away for a while but now I'm back. I'm very grateful for your help
and willing to try and help anyway I can to solve this issue. So, I'll
send the whole directory to your privately.
Note, that my client now is the FunV10 client, as the "official"
funambol client no longer has the ability to select the server it syncs
with. But this seems to be the same client more or less than the
previous 10.0.8.
br, Juhis
On 02/17/2012 10:20 PM, Patrick Ohly wrote:
On Fri, 2012-02-17 at 16:57 +0100, Patrick Ohly wrote:
> You log shows that this is the same problem reported before:
>
> http://lists.syncevolution.org/pipermail/syncevolution/2011-September/002...
>
> [2012-02-15 21:19:18.880] ===> smlProcessData failed, returned 0x200B
>
> I guess I'll have to install the app myself and try it out locally.
> Debugging this further will require recompiling SyncEvolution to get
> more debug information out of the libsmltk library.
I've installed the Funambol app 10.0.8 on an HTC Desire. I can't
reproduce the smlProcessData error. Sending a new contact worked, both
ways. I have not enabled any other data source.
What I see instead is that the Funambol app doesn't properly respond to
all SyncML commands. That has the effect that the server keeps the
session open:
[2012-02-17 21:01:55.757] - Not yet received status for command 'Put', (outgoing
MsgID=1, CmdID=3)
[2012-02-17 21:01:55.757] - Not yet received REQUIRED status for command 'Get',
(outgoing MsgID=1, CmdID=5)
[2012-02-17 21:01:55.757] - Not yet received status for command 'SyncHdr',
(outgoing MsgID=3, CmdID=0)
[2012-02-17 21:01:55.757] SESSION CANNOT END - Not yet received REQUIRED status for some
of 3 commands
The session then has to be aborted, which causes it to end with a local
400 status code. Not nice, but seems to work otherwise. Hmm, I always
encounter a slow sync. I haven't checked whether that is a side effect
of the 400 error.
My host side is Debian Testing, 64 bit, with SyncEvolution 1.2.2 from
syncevolution.org. I was using plain http.
As I can't replicate the problem, someone else will have to provide more
log files. Can someone set the loglevel to 5 in the SyncEvolution config
for the phone and send me the entire session directory, including the
syncevolution-log.html and the message dump files?
10:09 a.m.
New subject: [SyncEvolution] Using syncevolution http server to sync Google Nexus S (Funambol SyncML client)
On Mon, 2012-02-27 at 11:17 +0200, Juha Pahkala wrote:
Note, that my client now is the FunV10 client, as the
"official"
funambol client no longer has the ability to select the server it syncs
with. But this seems to be the same client more or less than the
previous 10.0.8.
I've tried FunV10, but I cannot get it to work with SyncEvolution at
all. The initial configuration requires logging into the server
("Anmelden" in my German localization). That fails with a generic error
dialog ("Allgemeiner Fehler").
The server-side logs show that the client is trying to sync with a
"configuration" data source. There's no guarantee that such a source
exists on a generic SyncML service. In a normal SyncEvolution
installation, it doesn't, so the client gets a 404 error.
I tried creating one:
syncevolution --configure \
backend=file \
database=file:///tmp/funambol-config \
databaseFormat=text/plain \
sync=two-way \
funambol-android configuration
That avoids the 404 error, but because the server treats this as a
normal source with no special semantic attached, it requests a slow sync
(508 status code) in the initial sync and the client still shows the
same "generic error" dialog.
Even if we got past that point, there's no guarantee that emulating the
"configuration" source with plain text items would work with the client.
Quite frankly, I think you are better off with a SyncML client for
Android which is meant to be used with arbitrary SyncML servers by the
authors of the client. I can recommend the Synthesis client. I know that
you have to pay for it, but at least it works and you'll get support for
what you are trying to do with it.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
10:21 a.m.
New subject: [SyncEvolution] Using syncevolution http server to sync Google Nexus S (Funambol SyncML client)
Really. For me, the FunV10 worked exactly like the older funambol
client. I could log in to syncevolution (1.2.2) just fine, and the first
sync worked, like before.
Doing a two-way sync failed with the same SAN error:
[ERROR] sync: SML (or SAN) error processing incoming message (local,
status 20007)
I think it would be great if syncevolution worked with an open source
android client, and funambol client seems to be the only one. Of course,
I'm not the one writing the code, so.... If you do find time and
motivation, I'll send you the logs anyhow.
br, Juhis
On 02/27/2012 12:09 PM, Patrick Ohly wrote:
On Mon, 2012-02-27 at 11:17 +0200, Juha Pahkala wrote:
> Note, that my client now is the FunV10 client, as the "official"
> funambol client no longer has the ability to select the server it syncs
> with. But this seems to be the same client more or less than the
> previous 10.0.8.
I've tried FunV10, but I cannot get it to work with SyncEvolution at
all. The initial configuration requires logging into the server
("Anmelden" in my German localization). That fails with a generic error
dialog ("Allgemeiner Fehler").
The server-side logs show that the client is trying to sync with a
"configuration" data source. There's no guarantee that such a source
exists on a generic SyncML service. In a normal SyncEvolution
installation, it doesn't, so the client gets a 404 error.
I tried creating one:
syncevolution --configure \
backend=file \
database=file:///tmp/funambol-config \
databaseFormat=text/plain \
sync=two-way \
funambol-android configuration
That avoids the 404 error, but because the server treats this as a
normal source with no special semantic attached, it requests a slow sync
(508 status code) in the initial sync and the client still shows the
same "generic error" dialog.
Even if we got past that point, there's no guarantee that emulating the
"configuration" source with plain text items would work with the client.
Quite frankly, I think you are better off with a SyncML client for
Android which is meant to be used with arbitrary SyncML servers by the
authors of the client. I can recommend the Synthesis client. I know that
you have to pay for it, but at least it works and you'll get support for
what you are trying to do with it.
11:51 a.m.
New subject: [SyncEvolution] Using syncevolution http server to sync Google Nexus S (Funambol SyncML client)
On Mon, 2012-02-27 at 12:21 +0200, Juha Pahkala wrote:
Really. For me, the FunV10 worked exactly like the older funambol
client. I could log in to syncevolution (1.2.2) just fine, and the first
sync worked, like before.
I am running FunV10, Version 10.1.1. Is that also your version?
Doing a two-way sync failed with the same SAN error:
[ERROR] sync: SML (or SAN) error processing incoming message (local,
status 20007)
I've looked at the logs that you sent me. It does indeed look like the
old problem.
Can you run the test again with the attached syncevo-http-server.py and
-d on its command line?
I'd like to double-check whether the corrupted incoming XML messages is
really broken the way it is dumped (with a complete Synthesis SyncML
messages appended after the incoming SyncML message) or whether that is
an artifact of how message buffers are handled internally:
syncevolution-log_msg003_006_incoming_ERR_0x200B.xml:
...
</Sync>
</SyncBody>
</SyncML>
<?xml version="1.0" encoding="UTF-8"?>...
The part with line breaks was encoded by Funambol, the part without from
libsynthesis/SyncML Toolkit.
The updated Python script will log "processing incoming message"
followed by the actual message data. Does it contain the same mixture of
messages as quoted above?
I think it would be great if syncevolution worked with an open source
android client, and funambol client seems to be the only one. Of course,
I'm not the one writing the code, so.... If you do find time and
motivation, I'll send you the logs anyhow.
Of course I'd like to support an open source Android client, but if that
client is making invalid assumptions ("server has 'configuration'
source") the it simply might not be possible without changing the
client.
Now your problem is different. I'm not sure yet where it comes from yet.
If the step above shows that the incoming data is sane, then we'll have
to resort to enabling debug code to the SyncML message decoding library.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
12:32 p.m.
New subject: [SyncEvolution] Using syncevolution http server to sync Google Nexus S (Funambol SyncML client)
On 02/27/2012 01:51 PM, Patrick Ohly wrote:
I am running FunV10, Version 10.1.1. Is that also your version?
I'm on 10.1.1 also. Strange...
> Doing a two-way sync failed with the same SAN error:
>
> [ERROR] sync: SML (or SAN) error processing incoming message (local,
> status 20007)
I've looked at the logs that you sent me. It does indeed look like the
old problem.
Can you run the test again with the attached syncevo-http-server.py and
-d on its command line?
Sure. Just did and sent the output to you.
> I think it would be great if syncevolution worked with an open source
> android client, and funambol client seems to be the only one. Of course,
> I'm not the one writing the code, so.... If you do find time and
> motivation, I'll send you the logs anyhow.
Of course I'd like to support an open source Android client, but if that
client is making invalid assumptions ("server has 'configuration'
source") the it simply might not be possible without changing the
client.
Understood. And if this is the case, then I'll go talk to the client
people, and with your help, ask them the right questions ;)
br, juhis
1:22 p.m.
New subject: [SyncEvolution] Using syncevolution http server to sync Google Nexus S (Funambol SyncML client)
On Mon, 2012-02-27 at 14:32 +0200, Juha Pahkala wrote:
On 02/27/2012 01:51 PM, Patrick Ohly wrote:
> I am running FunV10, Version 10.1.1. Is that also your version?
I'm on 10.1.1 also. Strange...
>> Doing a two-way sync failed with the same SAN error:
>>
>> [ERROR] sync: SML (or SAN) error processing incoming message (local,
>> status 20007)
>
> I've looked at the logs that you sent me. It does indeed look like the
> old problem.
>
> Can you run the test again with the attached syncevo-http-server.py and
> -d on its command line?
>
Sure. Just did and sent the output to you.
The concatenation in the XML message dump is indeed an artifact of how
buffers are handled; it's not the root cause of the problem.
I tried to reproduce the decoding problem by feeding the same message
into a local SyncEvolution installation, but after making a few changes
to the message to fit into a normal session the problem didn't occur.
Juha, I have to rely on you for some remote debugging.
As a first step, please use the pre-release 1.2.99+20120228+SE+cb0b7f6
+SYSYNC+5e0f652 from the experimental apt repo on syncevolution.org or
from dowloads.syncevolution.org.
It has additional debug printing enabled in the SyncML Toolkit. Please
send me another server-side log of a failed sync attempt with that
version.
Perhaps it'll tell me something (not sure yet).
If it doesn't, do you know gdb well enough to step through the source
code manually?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
1:25 p.m.
New subject: [SyncEvolution] Using syncevolution http server to sync Google Nexus S (Funambol SyncML client)
On 02/29/2012 03:22 PM, Patrick Ohly wrote:
On Mon, 2012-02-27 at 14:32 +0200, Juha Pahkala wrote:
>
> Sure. Just did and sent the output to you.
The concatenation in the XML message dump is indeed an artifact of how
buffers are handled; it's not the root cause of the problem.
I tried to reproduce the decoding problem by feeding the same message
into a local SyncEvolution installation, but after making a few changes
to the message to fit into a normal session the problem didn't occur.
Juha, I have to rely on you for some remote debugging.
Sure thing, no problem, other than the fact that I'll be away for two
weeks from Saturday onwards, but before and after, I'm glad to help.
As a first step, please use the pre-release
1.2.99+20120228+SE+cb0b7f6
+SYSYNC+5e0f652 from the experimental apt repo on syncevolution.org or
from dowloads.syncevolution.org.
I tried the .deb package, but it depended on kde,
so I skipped it and
tried the binary build instead. That gave me some dbus version error,
can't recall what it was. Anyhow, compiling the source worked out, and I
ran it again. Output sent to you.
It has additional debug printing enabled in the SyncML Toolkit.
Please
send me another server-side log of a failed sync attempt with that
version.
Perhaps it'll tell me something (not sure yet).
If it doesn't, do you know gdb well enough to step through the source
code manually?
Hmm, don't know gdb at all, but I do have some experience of debugging
and stepping through source code... so I'm pretty sure I'll be able to help.
br, juhis
2:25 p.m.
New subject: [SyncEvolution] Using syncevolution http server to sync Google Nexus S (Funambol SyncML client)
On Thu, 2012-03-01 at 15:25 +0200, Juha Pahkala wrote:
On 02/29/2012 03:22 PM, Patrick Ohly wrote:
> On Mon, 2012-02-27 at 14:32 +0200, Juha Pahkala wrote:
>>
>> Sure. Just did and sent the output to you.
> The concatenation in the XML message dump is indeed an artifact of how
> buffers are handled; it's not the root cause of the problem.
>
> I tried to reproduce the decoding problem by feeding the same message
> into a local SyncEvolution installation, but after making a few changes
> to the message to fit into a normal session the problem didn't occur.
>
> Juha, I have to rely on you for some remote debugging.
Sure thing, no problem, other than the fact that I'll be away for two
weeks from Saturday onwards, but before and after, I'm glad to help.
> As a first step, please use the pre-release 1.2.99+20120228+SE+cb0b7f6
> +SYSYNC+5e0f652 from the experimental apt repo on syncevolution.org or
> from dowloads.syncevolution.org.
I tried the .deb package, but it depended on kde,
How much of a problem is that?
I had to make a choice between compiling and packaging SyncEvolution
once, which implies that these binaries are run through all tests, and
compiling multiple times (for Evolution, for KDE) and then only
partially testing each package.
In the end I went for compiling once, because it is also less work.
What I could do is disable the KDE UI dependencies in the core
SyncEvolution by disabling KWallet support. The dependency on Akonadi in
the Akonadi backend doesn't have to be a hard dependency because only an
optional module depends on it. Failing to load that when libs are
missing is handled.
Yet another option, already discussed before, is to move
platform-specific code into modules. But that'll require further changes
to source code.
so I skipped it and
tried the binary build instead. That gave me some dbus version error,
can't recall what it was.
You mean the .tar.gz? For that you still need the same KDE libs
(libkdeui, libkdecore, QtDbus, ...) on the system, otherwise
SyncEvolution can't start.
Anyhow, compiling the source worked out, and I
ran it again. Output sent to you.
Thanks. It remains a mystery. The logs show that it seems to parse six
vCards (last one: N:Tho). I don't see anything special in that vCard or
the one after it.
I also don't see any particular limits in the code, items in the Replace
command are a linked list that can be extended infinitely.
> It has additional debug printing enabled in the SyncML Toolkit.
Please
> send me another server-side log of a failed sync attempt with that
> version.
>
> Perhaps it'll tell me something (not sure yet).
>
> If it doesn't, do you know gdb well enough to step through the source
> code manually?
>
Hmm, don't know gdb at all, but I do have some experience of debugging
and stepping through source code... so I'm pretty sure I'll be able to help.
Please give it a try. Run "script /tmp/gdb.log; gdb
syncevo-dbus-server". Set a breakpoint in buildGenericCmd:
$ gdb /usr/libexec/syncevo-dbus-server
...
Reading symbols from /usr/libexec/syncevo-dbus-server...done.
(gdb) b buildGenericCmd
Function "buildGenericCmd" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (buildGenericCmd) pending.
(gdb) run
The symbol should get resolved once the shared libs are loaded.
Then run syncevo-http-server in a separate window. I think the first
call of buildGenericCmd() will be the right one, for the Replace command
in the second incoming message.
What we are looking out for is the place where the return code (usually
called rc) is set to SML_ERR_XLT_INVAL_SYNCML_DOC == 0x200B.
I suspect that the culprit is either inside appendItemList() or the
default case:
case TN_ITEM:
rc = appendItemList(pDecoder, &pGenCmd->itemList);
items++;
break;
default:
rc =
SML_DECODEERROR(SML_ERR_XLT_INVAL_SYNCML_DOC,pScanner,"buildGenericCmd");
So it should be okay to step over all other functions (with n = next)
and only step into appendItemList() with s (= step).
But before you do that, let's try a simpler approach for locating the
parse error:
$ gdb /usr/libexec/syncevo-dbus-server
...
(gdb) run
Starting program: /usr/libexec/syncevo-dbus-server
[Thread debugging using libthread_db enabled]
Traceback (most recent call last):
File "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.16-gdb.py", line 59, in
<module>
from libstdcxx.v6.printers import register_libstdcxx_printers
ImportError: No module named libstdcxx.v6.printers
^CStopped due to shared library event
Quit
(gdb) b show_decode_error
Breakpoint 1 at 0x7ffff0058e00: file
/data/runtests/work/sources/libsynthesis/src/syncml_tk/src/sml/xlt/all/xltdec.c, line
235.
(gdb) cond 1 aRc == 0x200b
(gdb) c
Continuing.
...
I expect that to stop at the breakpoint. What's the output of "bt" then?
If never stops there, then perhaps SML_ERR_XLT_INVAL_SYNCML_DOC is set
in those few places which are not wrapped in SML_DECODEERROR(). A grep
of the source turned up some places:
src/syncml_tk/src/sml/xlt/all/xltmetinf.c:77: return SML_ERR_XLT_INVAL_SYNCML_DOC;
src/syncml_tk/src/sml/xlt/all/xltmetinf.c:104: rc =
SML_ERR_XLT_INVAL_SYNCML_DOC;
src/syncml_tk/src/sml/xlt/all/xltmetinf.c:130: return
SML_ERR_XLT_INVAL_SYNCML_DOC;
src/syncml_tk/src/sml/xlt/all/xltmetinf.c:169: rc =
SML_ERR_XLT_INVAL_SYNCML_DOC;
src/syncml_tk/src/sml/xlt/all/xltmetinf.c:196: return
SML_ERR_XLT_INVAL_SYNCML_DOC;
src/syncml_tk/src/sml/xlt/all/xltmetinf.c:260:
In gdb, after "b show_decode_error", can you also cut-and-paste this:
b xltmetinf.c:77
b xltmetinf.c:104
b xltmetinf.c:130
b xltmetinf.c:169
b xltmetinf.c:196
b xltmetinf.c:260
If it never stops at any of these breakpoints, then please send me the
syncevolution-log.html of that failed sync. There must be an error in it
which is different from the one seen before.
If it stops and you used the "script" command, then /tmp/gdb.log will
have a full dump of your debug session. That's what you can send me.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
7:08 p.m.
New subject: [SyncEvolution] Using syncevolution http server to sync Google Nexus S (Funambol SyncML client)
On 03/01/2012 04:25 PM, Patrick Ohly wrote:
On Thu, 2012-03-01 at 15:25 +0200, Juha Pahkala wrote:
> On 02/29/2012 03:22 PM, Patrick Ohly wrote:
>> As a first step, please use the pre-release 1.2.99+20120228+SE+cb0b7f6
>> +SYSYNC+5e0f652 from the experimental apt repo on syncevolution.org or
>> from dowloads.syncevolution.org.
> I tried the .deb package, but it depended on kde,
How much of a problem is that?
I had to make a choice between compiling and packaging SyncEvolution
once, which implies that these binaries are run through all tests, and
compiling multiple times (for Evolution, for KDE) and then only
partially testing each package.
In the end I went for compiling once, because it is also less work.
What I could do is disable the KDE UI dependencies in the core
SyncEvolution by disabling KWallet support. The dependency on Akonadi in
the Akonadi backend doesn't have to be a hard dependency because only an
optional module depends on it. Failing to load that when libs are
missing is handled.
Yet another option, already discussed before, is to move
platform-specific code into modules. But that'll require further changes
to source code.
Well, it certainly isn't that big a deal, but since I don't have any kde
libs installed, and don't mind compiling, I went that route instead.
If it doesn't, do you know gdb well enough to step through the
source
code manually?
> Hmm, don't know gdb at all, but I do have some experience of debugging
> and stepping through source code... so I'm pretty sure I'll be able to help.
Please give it a try.[snip]
Thanks for the detailed instructions, I *think* I got it right. Here's
what I did:
gdb /usr/libexec/syncevo-dbus-server
(gdb) run
###################################
# run sync from phone
###################################
^C
(gdb) b show_decode_error
Breakpoint 1 at 0xd84dc0: file
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/syncml_tk/src/sml/xlt/all/xltdec.c,
line 235.
(gdb) cond 1 aRc == 0x200b
(gdb) c
###################################
# run sync from phone again
###################################
Breakpoint 1, show_decode_error (aRc=8203, aScanner=0x8513110,
aRoutineName=0xd93169 "xmlHTMLEntity")
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/syncml_tk/src/sml/xlt/all/xltdec.c:235
235 {
(gdb) bt
#0 show_decode_error (aRc=8203, aScanner=0x8513110,
aRoutineName=0xd93169 "xmlHTMLEntity")
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/syncml_tk/src/sml/xlt/all/xltdec.c:235
#1 0x00d897ea in xmlHTMLEntity (pScanner=<optimized out>,
begin=0xbfffe288,
len=0xbfffe28c)
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/syncml_tk/src/sml/xlt/all/xltdecxml.c:667
#2 0x00d8ad68 in xmlSkipPCDATA (pScanner=0x8513110)
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/syncml_tk/src/sml/xlt/all/xltdecxml.c:1158
#3 _nextTok (pScanner=0x8513110)
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/syncml_tk/src/sml/xlt/all/xltdecxml.c:262
#4 0x00d8509a in nextToken (pDecoder=0x88100b0)
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/syncml_tk/src/sml/xlt/all/xltdec.c:643
#5 0x00d856c5 in buildPCData (pDecoder=0x88100b0, ppPCData=0x8658144)
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/syncml_tk/src/sml/xlt/all/xltdec.c:2385
#6 0x00d85f8b in buildItem (pDecoder=0x88100b0, ppElem=0x88287d0)
---Type <return> to continue, or q <return> to quit---
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/syncml_tk/src/sml/xlt/all/xltdec.c:2023
#7 0x00d860d4 in appendItemList (pDecoder=0x88100b0, ppItemList=0x8611d74)
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/syncml_tk/src/sml/xlt/all/xltdec.c:2501
#8 0x00d877ea in buildGenericCmd (pDecoder=0x88100b0, ppElem=0xbfffe484)
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/syncml_tk/src/sml/xlt/all/xltdec.c:1217
#9 0x00d85394 in xltDecNext (pDecoder=0x88100b0,
pBufEnd=0x8451078 " <value index=\"0\"
field=\"ALARM_TIME\"
conversion=\"emptyonly\"/>\n", ' ' <repeats 12 times>,
"<value
index=\"1\" field=\"ALARM_SNOOZE\"
conversion=\"emptyonly\"/>\n", ' '
<repeats 12 times>, "<value index=\"2\"
field=\"ALARM_REPEAT\"
conversio"..., ppBufPos=0xbfffe480, pe=0xbfffe48c,
ppContent=0xbfffe484)
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/syncml_tk/src/sml/xlt/all/xltdec.c:524
#10 0x00d81a8c in mgrProcessNextCommand (pInstanceInfo=0x88054b0,
id=0x88054b0)
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/syncml_tk/src/sml/mgr/all/mgrcmddispatcher.c:303
#11 smlProcessData (id=0x88054b0, mode=SML_NEXT_COMMAND)
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYN---Type
<return> to continue, or q <return> to quit---
C+5e0f652/./src/synthesis/src/syncml_tk/src/sml/mgr/all/mgrcmddispatcher.c:146
#12 0x00972c30 in sysync::TSyncAgent::ServerProcessingStep (this=0x840e760,
aStepCmd=@0xbfffe996, aInfoP=0xbfffe700)
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/sysync/syncagent.cpp:3157
#13 0x00973016 in sysync::TSyncAgent::ServerSessionStep (this=0x840e760,
aStepCmd=@0xbfffe996, aInfoP=0xbfffe700)
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/sysync/syncagent.cpp:3122
#14 0x00973852 in sysync::TSyncAgent::SessionStep (this=0x840e760,
aStepCmd=@0xbfffe996, aInfoP=0xbfffe700)
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/sysync/syncagent.cpp:2932
#15 0x008e6375 in sysync::TServerEngineInterface::SessionStep
(this=0x81eff58,
aSessionH=0x861d3e8, aStepCmd=@0xbfffe996, aInfoP=0xbfffe700)
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/Transport_interfaces/engine/enginesessiondispatch.cpp:477
#16 0x009125ca in sysync::SessionStep (aCB=0x81eff5c, aSessionH=0x861d3e8,
aStepCmd=0xbfffe996, aInfoP=0xbfffe700)
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYN---Type
<return> to continue, or q <return> to quit---
C+5e0f652/./src/synthesis/src/sysync/engineentry.cpp:88
#17 0x002afa86 in sysync::TEngineModuleBridge::SessionStep (this=0x818c5d8,
aSessionH=0x861d3e8, aStepCmd=@0xbfffe996, aInfoP=0xbfffe700)
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/sysync_SDK/Sources/enginemodulebridge.cpp:109
#18 0x001d176a in SyncEvo::SharedEngine::SessionStep (this=0x835a920,
aSessionH=..., aStepCmd=@0xbfffe996, aInfoP=0xbfffe700)
at src/syncevo/SynthesisEngine.cpp:96
#19 0x002475ba in SyncEvo::SyncContext::doSync (this=0x835a830)
at src/syncevo/SyncContext.cpp:3549
#20 0x0024ef30 in SyncEvo::SyncContext::sync (this=0x835a830,
report=0xbfffeb54) at src/syncevo/SyncContext.cpp:3016
#21 0x080b0914 in SyncEvo::Session::run (this=0x84383d0, redirect=...)
at src/dbus/server/session.cpp:743
#22 0x08096448 in SyncEvo::Server::run (this=0xbfffef80, redirect=...)
at src/dbus/server/server.cpp:362
#23 0x0808f2ae in main (argc=993277475, argv=0x6769766c, envp=0x70756f72)
at src/dbus/server/main.cpp:120
(gdb) Quit
So, there's one backtrace, hopefully a relevant one. If I did something
wrong or if you need more, please don't hesitate to ask. And thanks for
working on this.
br, juhis
7:55 p.m.
New subject: [SyncEvolution] Using syncevolution http server to sync Google Nexus S (Funambol SyncML client)
On Thu, 2012-03-01 at 21:08 +0200, Juha Pahkala wrote:
On 03/01/2012 04:25 PM, Patrick Ohly wrote:
>> Hmm, don't know gdb at all, but I do have some experience of debugging
>> and stepping through source code... so I'm pretty sure I'll be able to
help.
>
> Please give it a try.[snip]
Thanks for the detailed instructions, I *think* I got it right. Here's
what I did:
gdb /usr/libexec/syncevo-dbus-server
(gdb) run
[...]
#1 0x00d897ea in xmlHTMLEntity (pScanner=<optimized out>,
begin=0xbfffe288,
len=0xbfffe28c)
at
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/syncml_tk/src/sml/xlt/all/xltdecxml.c:667
Bingo.
Some of the vCards contain characters which were encoded using numeric
character references, for example @ became @ - these entities are
not handled by xmlHTMLEntity().
Of course, when I fed your message into the parser here I had picked
only the first contact, which didn't have an email address and thus
didn't trigger the problem.
I am unsure whether numeric character references are valid in XML. They
are certainly not necessary for things like the at sign, which has no
special meaning in XML.
I should be able to reproduce and fix the problem now. Stay tuned...
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
8:32 a.m.
New subject: [SyncEvolution] Using syncevolution http server to sync Google Nexus S (Funambol SyncML client)
On 03/01/2012 09:55 PM, Patrick Ohly wrote:
On Thu, 2012-03-01 at 21:08 +0200, Juha Pahkala wrote:
> On 03/01/2012 04:25 PM, Patrick Ohly wrote:
>>> Hmm, don't know gdb at all, but I do have some experience of debugging
>>> and stepping through source code... so I'm pretty sure I'll be able
to help.
>> Please give it a try.[snip]
> Thanks for the detailed instructions, I *think* I got it right. Here's
> what I did:
>
> gdb /usr/libexec/syncevo-dbus-server
> (gdb) run
[...]
> #1 0x00d897ea in xmlHTMLEntity (pScanner=<optimized out>,
> begin=0xbfffe288,
> len=0xbfffe28c)
> at
>
/home/jpahka/src/android/3/syncevolution-1.2.99+20120228+SE+cb0b7f6+SYSYNC+5e0f652/./src/synthesis/src/syncml_tk/src/sml/xlt/all/xltdecxml.c:667
Bingo.
Some of the vCards contain characters which were encoded using numeric
character references, for example @ became@ - these entities are
not handled by xmlHTMLEntity().
Of course, when I fed your message into the parser here I had picked
only the first contact, which didn't have an email address and thus
didn't trigger the problem.
I am unsure whether numeric character references are valid in XML. They
are certainly not necessary for things like the at sign, which has no
special meaning in XML.
I should be able to reproduce and fix the problem now. Stay tuned...
Great! Don't know how that has happened in my contacts list, it's been
through various databases :)
Anyhow, it's probably good to fix it in syncevolution, maybe just by
converting the invalid entries to valid characters?
br, juhis
9:03 a.m.
New subject: [SyncEvolution] Using syncevolution http server to sync Google Nexus S (Funambol SyncML client)
On Fri, 2012-03-02 at 10:32 +0200, Juha Pahkala wrote:
I am unsure whether numeric character references are valid in XML.
They
> are certainly not necessary for things like the at sign, which has
no
> special meaning in XML.
>
> I should be able to reproduce and fix the problem now. Stay tuned...
>
Great! Don't know how that has happened in my contacts list, it's
been
through various databases :)
The Funambol App must be encoding the characters like that. Probably
they use some code that was meant for HTML, which is unnecessarily
conservative regarding special characters when used for XML.
Of course, using binary XML would be a lot more efficient and avoid this
pitfall completely ;-}
Anyhow, it's probably good to fix it in syncevolution, maybe just
by
converting the invalid entries to valid characters?
I have a patch which does exactly that. I'll compile new binaries
soonish. But as you were compiling from source anyway, perhaps you can
try it? It's attached.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
3614
days inactive
3630
days old
syncevolution@synevolution.org
18 comments
2 participants
participants (2)
-
Juha Pahkala -
Patrick Ohly