From deloptes at gmail.com Tue Jul 25 21:20:56 2017 From: deloptes at gmail.com (deloptes) Date: Tue, 25 Jul 2017 23:20:56 +0200 Subject: [SyncEvolution] Sync on Debian Stretch Message-ID: Hi, I got Debian Stretch on a new computer and tried SyncEvolution, but I am getting an err message I can not deal with (see below). As usual I'll be very thankful to you for any idea where to look at or what I need to do to fix it. To complete the picture I built and installed in custom dir from source on jessie and I used debuild to build packages from 1.5.2_2 the debian source on stretch. On jessie I have 1.5.1 as 1.5.2 failed because of libopenobex2 (AFAIR). So could be the problem in libopenobex2? regards Before (on Jessie) I got this: [2017-07-05 23:44:24.466] Connecting Bluetooth device with address xxxxxxxxxx and channel 25 [2017-07-05 23:44:24.573] OBEX_EV_PROGRESS [2017-07-05 23:44:24.573] ObexTransportAgent::wait(): iteration [2017-07-05 23:44:25.167] OBEX_EV_REQDONE [2017-07-05 23:44:25.167] OBEX Transport: get header who from connect response with value SYNCML-SYNC [2017-07-05 23:44:25.167] ObexTransportAgent::wait(): is ready [2017-07-05 23:44:25.167] Server sending SAN [2017-07-05 23:44:25.167] ObexTransport send is called (46 bytes) [2017-07-05 23:44:25.167] OBEX_EV_PROGRESS [2017-07-05 23:44:25.167] ObexTransportAgent::wait(reply) [2017-07-05 23:44:25.167] ObexTransportAgent::wait(): iteration [2017-07-05 23:44:25.199] OBEX_EV_REQDONE [2017-07-05 23:44:25.199] ObexTransport send completed [2017-07-05 23:44:25.199] ObexTransportAgent::wait(): is ready [2017-07-05 23:44:25.199] OBEX_EV_PROGRESS [2017-07-05 23:44:25.938] OBEX_EV_REQDONE [2017-07-05 23:44:25.946] Module_DeleteContext 'session' ... sync goes on Now on Stretch I have this: [2017-07-25 23:00:07.630] Connecting Bluetooth device with address xxxxxxxxxx and channel 25 [2017-07-25 23:00:07.789] ObexTransportAgent::wait(): iteration [2017-07-25 23:00:07.789] OBEX_EV_PROGRESS [2017-07-25 23:00:07.789] ObexTransportAgent::wait(): iteration [2017-07-25 23:00:08.271] OBEX_EV_REQDONE [2017-07-25 23:00:08.272] OBEX Transport: get header who from connect response with value SYNCML-SYNC [2017-07-25 23:00:08.272] ObexTransportAgent::wait(): is ready [2017-07-25 23:00:08.272] Server sending SAN [2017-07-25 23:00:08.272] ObexTransport send is called (46 bytes) [2017-07-25 23:00:08.272] ObexTransportAgent::wait(reply) [2017-07-25 23:00:08.272] ObexTransportAgent::wait(): iteration [2017-07-25 23:00:08.272] OBEX_EV_PROGRESS [2017-07-25 23:00:08.272] ObexTransportAgent::wait(): iteration [2017-07-25 23:00:08.304] OBEX_EV_REQDONE [2017-07-25 23:00:08.304] ObexTransport send completed [2017-07-25 23:00:08.304] ObexTransportAgent::wait(): is ready [2017-07-25 23:00:08.304] OBEX_EV_PROGRESS [2017-07-25 23:00:08.315] OBEX_EV_REQDONE [2017-07-25 23:00:08.315] OBEX Request 3 got a failed response Unknown response [2017-07-25 23:00:08.316] Server Alerted Sync init with SANFormat 12 failed, trying with legacy format [2017-07-25 23:00:08.316] starting SAN 11 auth 1B2M2Y8AsgTpgAmY7PhCfg== nonce SyncEvolution session 1 server PC Suite [2017-07-25 23:00:08.316] SAN datastore addressbook uri Contacts type text/x-vcard [2017-07-25 23:00:08.316] SAN with overall sync mode 206 sync breaks here _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From deloptes at gmail.com Tue Jul 25 23:25:26 2017 From: deloptes at gmail.com (deloptes) Date: Wed, 26 Jul 2017 01:25:26 +0200 Subject: [SyncEvolution] Sync on Debian Stretch References: Message-ID: deloptes wrote: > So could be the problem in libopenobex2? syncevolution 1.5.1 with libopenobex1 works as before _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From tino.keitel+syncevolution at tikei.de Thu Jul 27 07:40:35 2017 From: tino.keitel+syncevolution at tikei.de (Tino Mettler) Date: Thu, 27 Jul 2017 09:40:35 +0200 Subject: [SyncEvolution] Sync on Debian Stretch In-Reply-To: References: Message-ID: <20170727074034.GA18421@eazy.amigager.de> 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 at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From deloptes at gmail.com Thu Jul 27 08:16:46 2017 From: deloptes at gmail.com (deloptes) Date: Thu, 27 Jul 2017 10:16:46 +0200 Subject: [SyncEvolution] Sync on Debian Stretch References: <20170727074034.GA18421@eazy.amigager.de> Message-ID: 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 at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From tino.keitel+syncevolution at tikei.de Thu Jul 27 09:01:08 2017 From: tino.keitel+syncevolution at tikei.de (Tino Mettler) Date: Thu, 27 Jul 2017 11:01:08 +0200 Subject: [SyncEvolution] Sync on Debian Stretch In-Reply-To: References: <20170727074034.GA18421@eazy.amigager.de> Message-ID: <20170727090108.GA12166@eazy.amigager.de> 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 at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From deloptes at gmail.com Thu Jul 27 09:56:17 2017 From: deloptes at gmail.com (deloptes) Date: Thu, 27 Jul 2017 11:56:17 +0200 Subject: [SyncEvolution] Sync on Debian Stretch References: <20170727074034.GA18421@eazy.amigager.de> <20170727090108.GA12166@eazy.amigager.de> Message-ID: 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 at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From patrick.ohly at intel.com Thu Jul 27 10:28:13 2017 From: patrick.ohly at intel.com (Patrick Ohly) Date: Thu, 27 Jul 2017 12:28:13 +0200 Subject: [SyncEvolution] Sync on Debian Stretch In-Reply-To: References: <20170727074034.GA18421@eazy.amigager.de> Message-ID: <1501151293.26603.45.camel@intel.com> 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. From deloptes at gmail.com Thu Jul 27 12:23:03 2017 From: deloptes at gmail.com (deloptes) Date: Thu, 27 Jul 2017 14:23:03 +0200 Subject: [SyncEvolution] Sync on Debian Stretch References: <20170727074034.GA18421@eazy.amigager.de> <1501151293.26603.45.camel@intel.com> Message-ID: 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 at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From patrick.ohly at intel.com Thu Jul 27 12:35:00 2017 From: patrick.ohly at intel.com (Patrick Ohly) Date: Thu, 27 Jul 2017 14:35:00 +0200 Subject: [SyncEvolution] Sync on Debian Stretch In-Reply-To: References: <20170727074034.GA18421@eazy.amigager.de> <1501151293.26603.45.camel@intel.com> Message-ID: <1501158900.26603.48.camel@intel.com> 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.