Re: [SyncEvolution] Sync on Debian Stretch
Patrick Ohly wrote: > So have you built 1.5.2 with libopenobex2 from Debian Stretch and it > failed? With which phone? > yes - built 1.5.2 with libopenobex2 from Debian Stretch. phone is Nokia N9 I can't recall now but I think I tested also with older Nokia 5530 Desktop is Trinity - former KDE3 > I'm just asking for the sake of completeness. I probably won't have > your exact phone either :-/ > sure > What I did is a "configure --disable-shared --enable-static CFLAGS=-g > CXXFLAGS=-g ..." and then in the build directory I ran > "SYNCEVOLUTION_DEBUG=10 ./src/syncevolution --daemon=no nokia-n97-mini@ > devices addressbook". > > This allows running the command under gdb. The interesting line is is > the error message in ObexTransportAgent::obex_callback. What value does > obex_rsp have, and why does OBEX_ResponseToString not know it? I may try test this next and post the output. thanks and regards ___ SyncEvolution mailing list SyncEvolution@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution
Re: [SyncEvolution] Sync on Debian Stretch
On Mon, 2017-09-04 at 19:11 +0200, deloptes wrote: > Patrick Ohly wrote: > > > Have you gotten around to testing this combination? > > > > I just tried with SyncEvolution master (= 1.5.2), libopenobex2 from > > Debian Stretch (= 1.7.2-1), and a Nokia N97 mini. No problem here. > > > > FWIW, the binaries from syncevolution.org shouldn't be affected, > > because for the 1.5.2 release I had started linking libopenobex.a > > from > > Ubuntu Trusty directly into the binaries. That's of course not a > > solution for binaries compiled from source. > > Hi > I have no Nokia N97 mini and for the Trinity Desktop I have to > compile from > source. > I am not sure if you are asking me, but as it is posted in this > thread, I > just assume it. > On top I use Debian Stretch - the problem reported originally is > based on it. So have you built 1.5.2 with libopenobex2 from Debian Stretch and it failed? With which phone? I'm just asking for the sake of completeness. I probably won't have your exact phone either :-/ What I did is a "configure --disable-shared --enable-static CFLAGS=-g CXXFLAGS=-g ..." and then in the build directory I ran "SYNCEVOLUTION_DEBUG=10 ./src/syncevolution --daemon=no nokia-n97-mini@ devices addressbook". This allows running the command under gdb. The interesting line is is the error message in ObexTransportAgent::obex_callback. What value does obex_rsp have, and why does OBEX_ResponseToString not know 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. ___ SyncEvolution mailing list SyncEvolution@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution
Re: [SyncEvolution] Sync on Debian Stretch
Patrick Ohly wrote: > Have you gotten around to testing this combination? > > I just tried with SyncEvolution master (= 1.5.2), libopenobex2 from > Debian Stretch (= 1.7.2-1), and a Nokia N97 mini. No problem here. > > FWIW, the binaries from syncevolution.org shouldn't be affected, > because for the 1.5.2 release I had started linking libopenobex.a from > Ubuntu Trusty directly into the binaries. That's of course not a > solution for binaries compiled from source. Hi I have no Nokia N97 mini and for the Trinity Desktop I have to compile from source. I am not sure if you are asking me, but as it is posted in this thread, I just assume it. On top I use Debian Stretch - the problem reported originally is based on it. regards ___ SyncEvolution mailing list SyncEvolution@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution
Re: [SyncEvolution] Sync on Debian Stretch
On Thu, 2017-07-27 at 14:23 +0200, deloptes wrote: > I'll just look into if 1.5.2 works with > libopenobex1. If so it will be much easier. Have you gotten around to testing this combination? I just tried with SyncEvolution master (= 1.5.2), libopenobex2 from Debian Stretch (= 1.7.2-1), and a Nokia N97 mini. No problem here. FWIW, the binaries from syncevolution.org shouldn't be affected, because for the 1.5.2 release I had started linking libopenobex.a from Ubuntu Trusty directly into the binaries. That's of course not a solution for binaries compiled from source. -- 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. ___ SyncEvolution mailing list SyncEvolution@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution
Re: [SyncEvolution] Sync on Debian Stretch
On Thu, 2017-07-27 at 14:23 +0200, deloptes wrote: > As reported originally it dies with error "OBEX Request 3 got a > failed response Unknown response" etc. One would need to dig into the source of ObexTransportAgent.cpp and libopenobex2 to determine what that unknown response is and why it occurs. -- 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. ___ SyncEvolution mailing list SyncEvolution@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution
Re: [SyncEvolution] Sync on Debian Stretch
Patrick Ohly wrote: > Thanks for root causing this. > > Unfortunately I have no idea what changed in libopenobex. I also > haven't written the code which uses it, so I'd be in for some amount of > reverse-engineering before I might be able to fix it :-/ No prob. If you need input and testing let me know. I don't have any idea/knowledge how I can test it. I'll just look into if 1.5.2 works with libopenobex1. If so it will be much easier. As reported originally it dies with error "OBEX Request 3 got a failed response Unknown response" etc. I'm facing some issues with the kgpg app I use as things changed from gpg v1 in jessie to gpg v2 in stretch and as I have working syncevolution I'll be chasing this next :/ Progress keeps us all busy. regards ___ SyncEvolution mailing list SyncEvolution@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution
Re: [SyncEvolution] Sync on Debian Stretch
On Thu, 2017-07-27 at 10:16 +0200, deloptes wrote: > I think this will work also, because it looks like the problem is > coming from the obex lib. Thanks for root causing this. Unfortunately I have no idea what changed in libopenobex. I also haven't written the code which uses it, so I'd be in for some amount of reverse-engineering before I might be able to fix 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. ___ SyncEvolution mailing list SyncEvolution@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution
Re: [SyncEvolution] Sync on Debian Stretch
Tino Mettler wrote: > it was not meant as a permanent solution, but to help finding the root > cause of the problem. Thanks I will report when 1.5.2 testing done. regards ___ SyncEvolution mailing list SyncEvolution@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution
Re: [SyncEvolution] Sync on Debian Stretch
On Thu, Jul 27, 2017 at 10:16:46 +0200, deloptes wrote: [...] > There is however a problem with libopenobex1 and perhaps I need to customize > the way it gets installed and the dependencies, because it conflicts with > libopenobex2 and drops all obex related apps like obexfs, which I am > interested in. So for now it is acceptable solution, but it needs to be > addressed for a permanent solution Hi, it was not meant as a permanent solution, but to help finding the root cause of the problem. Regards, Tino ___ SyncEvolution mailing list SyncEvolution@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution
Re: [SyncEvolution] Sync on Debian Stretch
Tino Mettler wrote: > you could build libopenobex1 for Stretch and build Syncevolution from > Stretch against libopenobex1 to see if it really makes a difference. Hi Tino, thanks for the response. My last msg (perhaps you did not see it) reported exactly that. Because of lack of time, I build libopenobex1 on stretch and syncevolution-1.5.1+20161014+SE+46a81a3+SYSYNC+7c9a4bf, which I new was working. And indeed it worked. I will try with 1.5.2 (from the debian sources) with libopenobex1. I think this will work also, because it looks like the problem is coming from the obex lib. There is however a problem with libopenobex1 and perhaps I need to customize the way it gets installed and the dependencies, because it conflicts with libopenobex2 and drops all obex related apps like obexfs, which I am interested in. So for now it is acceptable solution, but it needs to be addressed for a permanent solution Thanks and regards ___ SyncEvolution mailing list SyncEvolution@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution
Re: [SyncEvolution] Sync on Debian Stretch
On Wed, Jul 26, 2017 at 01:25:26 +0200, deloptes wrote: > deloptes wrote: > > > So could be the problem in libopenobex2? > > syncevolution 1.5.1 with libopenobex1 works as before Hi, you could build libopenobex1 for Stretch and build Syncevolution from Stretch against libopenobex1 to see if it really makes a difference. Regards, Tino ___ SyncEvolution mailing list SyncEvolution@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution
Re: [SyncEvolution] Sync on Debian Stretch
deloptes wrote: > So could be the problem in libopenobex2? syncevolution 1.5.1 with libopenobex1 works as before ___ SyncEvolution mailing list SyncEvolution@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution
