From pyz at brama.com Tue Nov 5 21:54:19 2019 From: pyz at brama.com (Max Pyziur) Date: Tue, 5 Nov 2019 16:54:19 -0500 Subject: [SyncEvolution] Sync failure - F31 Message-ID: Greetings, I'm not sure if this is the first time running sync since upgrading to F31. But through F30, Sync has worked flawlessly Syncing with memotoo and evolution. Now, using the gui interface, the following error message appears: The sync process died unexpectedly. I've tried slow sync, deleting the data on the server via the gui, but each time the process dies with some variant of the above message. So, I'm looking for some sort of log file to see if there any messages or other indications of where the flaw would be. Any advice appreciated in this matter, Thanks! Max pyz at brama.com _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From deloptes at gmail.com Tue Nov 5 22:28:13 2019 From: deloptes at gmail.com (deloptes) Date: Tue, 5 Nov 2019 23:28:13 +0100 Subject: [SyncEvolution] Re: Sync failure - F31 References: Message-ID: Max Pyziur wrote: > > Greetings, > > I'm not sure if this is the first time running sync since upgrading to > F31. > > But through F30, Sync has worked flawlessly Syncing with memotoo and > evolution. > I am on debian - don't know F. > Now, using the gui interface, the following error message appears: > The sync process died unexpectedly. > > I've tried slow sync, deleting the data on the server via the gui, but > each time the process dies with some variant of the above message. > > So, I'm looking for some sort of log file to see if there any messages or > other indications of where the flaw would be. > > Run it from the command line SYCNEVOLUTION_DEBUG=3 syncevolution -r loglevel=6 addressbook then in your ~/.cache/syncevolution you find the logs And can you check the openobex version? Here it is not working with anything recent. I still have libopenobex1 1.5. Changes in 1.7 aka libopenobex2 render it unusable _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From pyz at brama.com Tue Nov 5 22:59:54 2019 From: pyz at brama.com (Max Pyziur) Date: Tue, 5 Nov 2019 17:59:54 -0500 Subject: [SyncEvolution] Re: Sync failure - F31 In-Reply-To: References: Message-ID: On Tue, 5 Nov 2019, deloptes wrote: > Max Pyziur wrote: > >> >> Greetings, >> >> I'm not sure if this is the first time running sync since upgrading to >> F31. >> >> But through F30, Sync has worked flawlessly Syncing with memotoo and >> evolution. >> > > I am on debian - don't know F. > >> Now, using the gui interface, the following error message appears: >> The sync process died unexpectedly. >> >> I've tried slow sync, deleting the data on the server via the gui, but >> each time the process dies with some variant of the above message. >> >> So, I'm looking for some sort of log file to see if there any messages or >> other indications of where the flaw would be. >> >> > > Run it from the command line > > SYCNEVOLUTION_DEBUG=3 syncevolution -r loglevel=6 addressbook > > then in your ~/.cache/syncevolution you find the logs Much thanks for your quick reply. What parameters and syntax are required for ? Much thanks, Max > And can you check the openobex version? Here it is not working with anything > recent. I still have libopenobex1 1.5. Changes in 1.7 aka libopenobex2 > render it unusable > > > _______________________________________________ > SyncEvolution mailing list -- syncevolution at syncevolution.org > To unsubscribe send an email to syncevolution-leave at syncevolution.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From patrick.ohly at intel.com Wed Nov 6 08:37:42 2019 From: patrick.ohly at intel.com (Patrick Ohly) Date: Wed, 6 Nov 2019 09:37:42 +0100 Subject: [SyncEvolution] Re: Sync failure - F31 In-Reply-To: References: Message-ID: Max Pyziur writes: > On Tue, 5 Nov 2019, deloptes wrote: > >> Max Pyziur wrote: >> >>> >>> Greetings, >>> >>> I'm not sure if this is the first time running sync since upgrading to >>> F31. >>> >>> But through F30, Sync has worked flawlessly Syncing with memotoo and >>> evolution. I'm behind on updating SyncEvolution, sorry for that. I have to do a new release which is based on and tested with the current set of libraries available in modern distros. Milan does an excellent job with keeping the packages building, but this can't replace upstream testing. >> I am on debian - don't know F. >> >>> Now, using the gui interface, the following error message appears: >>> The sync process died unexpectedly. >>> >>> I've tried slow sync, deleting the data on the server via the gui, but >>> each time the process dies with some variant of the above message. >>> >>> So, I'm looking for some sort of log file to see if there any messages or >>> other indications of where the flaw would be. >>> >>> >> >> Run it from the command line >> >> SYCNEVOLUTION_DEBUG=3 syncevolution -r loglevel=6 addressbook >> >> then in your ~/.cache/syncevolution you find the logs > > Much thanks for your quick reply. > > What parameters and syntax are required for ? is the name of your configuration. See "syncevolution --print-configs". -- Best Regards Patrick Ohly Senior Software Engineer Intel GmbH Open Source Technology Center Usenerstr. 5a Phone: +49-228-2493652 53129 Bonn Germany _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From mcrha at redhat.com Wed Nov 6 16:09:04 2019 From: mcrha at redhat.com (Milan Crha) Date: Wed, 6 Nov 2019 17:09:04 +0100 Subject: [SyncEvolution] Re: Sync failure - F31 In-Reply-To: References: Message-ID: On Wed, 2019-11-06 at 09:37 +0100, Patrick Ohly wrote: > Milan does an excellent job with keeping > the packages building, but this can't replace upstream testing. Hi, in fact, it can be an issue specific to Fedora 31. I made changes to use python3 (not python2) where those can be wrong in some way (it was semi-blind change). In other words, it can be my fault. Hopefully the run from the command line will show where that "unexpected die" happened precisely. Max, could you check whether ABRT catch anything, please? Being it a crash, it may record it. Bye, Milan _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From pyz at brama.com Thu Nov 7 00:07:03 2019 From: pyz at brama.com (Max Pyziur) Date: Wed, 6 Nov 2019 19:07:03 -0500 Subject: [SyncEvolution] Re: Sync failure - F31 In-Reply-To: References: Message-ID: On Wed, 6 Nov 2019, Patrick Ohly wrote: > Max Pyziur writes: >> On Tue, 5 Nov 2019, deloptes wrote: >> >>> Max Pyziur wrote: >>> >>>> >>>> Greetings, >>>> >>>> I'm not sure if this is the first time running sync since upgrading to >>>> F31. >>>> >>>> But through F30, Sync has worked flawlessly Syncing with memotoo and >>>> evolution. > > I'm behind on updating SyncEvolution, sorry for that. I have to do a new > release which is based on and tested with the current set of libraries > available in modern distros. Milan does an excellent job with keeping > the packages building, but this can't replace upstream testing. > >>> I am on debian - don't know F. >>> >>>> Now, using the gui interface, the following error message appears: >>>> The sync process died unexpectedly. >>>> >>>> I've tried slow sync, deleting the data on the server via the gui, but >>>> each time the process dies with some variant of the above message. >>>> >>>> So, I'm looking for some sort of log file to see if there any messages or >>>> other indications of where the flaw would be. >>>> >>>> >>> >>> Run it from the command line >>> >>> SYCNEVOLUTION_DEBUG=3 syncevolution -r loglevel=6 addressbook >>> >>> then in your ~/.cache/syncevolution you find the logs >> >> Much thanks for your quick reply. >> >> What parameters and syntax are required for ? > > is the name of your configuration. See "syncevolution > --print-configs". Thank you. I get: memotoo = /home/pyz/.config/syncevolution/default/peers/memotoo How do I use it in the context of this command: SYCNEVOLUTION_DEBUG=3 syncevolution -r loglevel=6 addressbook Simply placing the specified directory (/home/pyz/.config/syncevolution/default/peers/memotoo) in the place of produces errors. Max pyz at brama.com From pyz at brama.com Thu Nov 7 03:09:53 2019 From: pyz at brama.com (Max Pyziur) Date: Wed, 6 Nov 2019 22:09:53 -0500 Subject: [SyncEvolution] Re: Sync failure - F31 In-Reply-To: References: Message-ID: On Wed, 6 Nov 2019, Max Pyziur wrote: > On Wed, 6 Nov 2019, Patrick Ohly wrote: > >> Max Pyziur writes: >>> On Tue, 5 Nov 2019, deloptes wrote: >>> >>>> Max Pyziur wrote: >>>> >>>>> >>>>> Greetings, >>>>> >>>>> I'm not sure if this is the first time running sync since upgrading to >>>>> F31. >>>>> >>>>> But through F30, Sync has worked flawlessly Syncing with memotoo and >>>>> evolution. >> >> I'm behind on updating SyncEvolution, sorry for that. I have to do a new >> release which is based on and tested with the current set of libraries >> available in modern distros. Milan does an excellent job with keeping >> the packages building, but this can't replace upstream testing. >> >>>> I am on debian - don't know F. >>>> >>>>> Now, using the gui interface, the following error message appears: >>>>> The sync process died unexpectedly. >>>>> >>>>> I've tried slow sync, deleting the data on the server via the gui, but >>>>> each time the process dies with some variant of the above message. >>>>> >>>>> So, I'm looking for some sort of log file to see if there any messages >>>>> or >>>>> other indications of where the flaw would be. >>>>> >>>>> >>>> >>>> Run it from the command line >>>> >>>> SYCNEVOLUTION_DEBUG=3 syncevolution -r loglevel=6 >>>> addressbook >>>> >>>> then in your ~/.cache/syncevolution you find the logs >>> >>> Much thanks for your quick reply. >>> >>> What parameters and syntax are required for ? >> >> is the name of your configuration. See "syncevolution >> --print-configs". > > Thank you. > > I get: > > memotoo = /home/pyz/.config/syncevolution/default/peers/memotoo > > How do I use it in the context of this command: > SYCNEVOLUTION_DEBUG=3 syncevolution -r loglevel=6 addressbook > > Simply placing the specified directory > (/home/pyz/.config/syncevolution/default/peers/memotoo) in the place of profile> produces errors. I've been trying different approaches to the syntax; is this valid? pyz at pegasus ~/.local/share/evolution> SYCNEVOLUTION_DEBUG=3 syncevolution -r loglevel=6 /home/pyz/.config/syncevolution/default/peers/memotoo/config.ini addressbook It gives the following result: [ERROR] error code from SyncEvolution fatal error (local, status 10500): no such datastore(s): addressbook > > Max > pyz at brama.com [recycle] _______________________________________________ > SyncEvolution mailing list -- syncevolution at syncevolution.org > To unsubscribe send an email to syncevolution-leave at syncevolution.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > From deloptes at gmail.com Thu Nov 7 06:42:16 2019 From: deloptes at gmail.com (deloptes) Date: Thu, 7 Nov 2019 07:42:16 +0100 Subject: [SyncEvolution] Re: Sync failure - F31 References: Message-ID: Max Pyziur wrote: > On Wed, 6 Nov 2019, Max Pyziur wrote: > >> On Wed, 6 Nov 2019, Patrick Ohly wrote: >> >>> Max Pyziur writes: >>>> On Tue, 5 Nov 2019, deloptes wrote: >>>> >>>>> Max Pyziur wrote: >>>>> >>>>>> >>>>>> Greetings, >>>>>> >>>>>> I'm not sure if this is the first time running sync since upgrading >>>>>> to F31. >>>>>> >>>>>> But through F30, Sync has worked flawlessly Syncing with memotoo and >>>>>> evolution. >>> >>> I'm behind on updating SyncEvolution, sorry for that. I have to do a new >>> release which is based on and tested with the current set of libraries >>> available in modern distros. Milan does an excellent job with keeping >>> the packages building, but this can't replace upstream testing. >>> >>>>> I am on debian - don't know F. >>>>> >>>>>> Now, using the gui interface, the following error message appears: >>>>>> The sync process died unexpectedly. >>>>>> >>>>>> I've tried slow sync, deleting the data on the server via the gui, >>>>>> but each time the process dies with some variant of the above >>>>>> message. >>>>>> >>>>>> So, I'm looking for some sort of log file to see if there any >>>>>> messages or >>>>>> other indications of where the flaw would be. >>>>>> >>>>>> >>>>> >>>>> Run it from the command line >>>>> >>>>> SYCNEVOLUTION_DEBUG=3 syncevolution -r loglevel=6 >>>>> addressbook >>>>> >>>>> then in your ~/.cache/syncevolution you find the logs >>>> >>>> Much thanks for your quick reply. >>>> >>>> What parameters and syntax are required for ? >>> >>> is the name of your configuration. See "syncevolution >>> --print-configs". >> >> Thank you. >> >> I get: >> >> memotoo = /home/pyz/.config/syncevolution/default/peers/memotoo >> >> How do I use it in the context of this command: >> SYCNEVOLUTION_DEBUG=3 syncevolution -r loglevel=6 >> addressbook >> >> Simply placing the specified directory >> (/home/pyz/.config/syncevolution/default/peers/memotoo) in the place of >> produces errors. > > I've been trying different approaches to the syntax; is this valid? > > pyz at pegasus ~/.local/share/evolution> SYCNEVOLUTION_DEBUG=3 syncevolution > -r loglevel=6 > /home/pyz/.config/syncevolution/default/peers/memotoo/config.ini > addressbook > > It gives the following result: > [ERROR] error code from SyncEvolution fatal error (local, status 10500): > [no such datastore(s): addressbook > you should try SYCNEVOLUTION_DEBUG=3 syncevolution -r loglevel=6 memotoo addressbook _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From patrick.ohly at intel.com Thu Nov 7 06:53:48 2019 From: patrick.ohly at intel.com (Patrick Ohly) Date: Thu, 7 Nov 2019 07:53:48 +0100 Subject: [SyncEvolution] Re: Sync failure - F31 In-Reply-To: References: Message-ID: Max Pyziur writes: > memotoo = /home/pyz/.config/syncevolution/default/peers/memotoo > > How do I use it in the context of this command: > SYCNEVOLUTION_DEBUG=3 syncevolution -r loglevel=6 addressbook > > Simply placing the specified directory > (/home/pyz/.config/syncevolution/default/peers/memotoo) in the place of > produces errors. Just use "memotoo": SYNCEVOLUTION_DEBUG=3 syncevolution -r loglevel=6 memotoo addressbook -- Best Regards Patrick Ohly _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From mail at ericberndt.de Sun Nov 10 13:05:16 2019 From: mail at ericberndt.de (mail at ericberndt.de) Date: Sun, 10 Nov 2019 13:05:16 +0000 Subject: [SyncEvolution] Re: Sync failure - F31 In-Reply-To: References: Message-ID: <20191110130516.2696.78637@new-ml01.vlan13.01.org> Hello Patrick i also updated to F31 and get some errors while syncronise my adresses and events. I'm working with an local installed funambol server (working on centos 7). Before upgrading to f31 everything works fine. For now i found out that only Events and Memos are not working. Adressbook and ToDo's dont deliver any Problems. Her is my output using your command above SYNCEVOLUTION_DEBUG=3 syncevolution -r loglevel=6 funambol calendar 1 [DEBUG 00:00:00] SuspendFlags: (re)activating, currently inactive 2 [DEBUG 00:00:00] SuspendFlags: activating signal handler(s) with fds 8->7 3 [DEBUG 00:00:00] SuspendFlags: catch signal 2 4 [DEBUG 00:00:00] SuspendFlags: catch signal 15 5 [INFO 00:00:00] addressbook: inactive 6 [INFO 00:00:00] calendar+todo: inactive 7 [INFO 00:00:00] memo: inactive 8 [INFO 00:00:00] todo: inactive 9 [ERROR 00:00:00] Verbindung ist geschlossen 10 [DEBUG 00:00:00] SuspendFlags: deactivating fds 8->7 11 [DEBUG 00:00:00] SuspendFlags: close m_receiverFD 7 12 [DEBUG 00:00:00] SuspendFlags: close m_senderFD 8 13 [DEBUG 00:00:00] SuspendFlags: done with deactivation Error is an closed Connection (line 9). In my log file i found the following https://paste.fedoraproject.org/paste/fqXYHwxS~A3sFzcrmq8baA Greets Eric _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From mcrha at redhat.com Mon Nov 11 08:48:48 2019 From: mcrha at redhat.com (Milan Crha) Date: Mon, 11 Nov 2019 09:48:48 +0100 Subject: [SyncEvolution] Re: Sync failure - F31 In-Reply-To: <20191110130516.2696.78637@new-ml01.vlan13.01.org> References: <20191110130516.2696.78637@new-ml01.vlan13.01.org> Message-ID: On Sun, 2019-11-10 at 13:05 +0000, mail at ericberndt.de wrote: > In my log file i found the following > > https://paste.fedoraproject.org/paste/fqXYHwxS~A3sFzcrmq8baA Hi, I see from the backtrace that it's my fault. I'm sorry. When porting syncevolution to libecal-2.0 I missed one place (maybe more), causing the crash. The attached patch will fix it. I made a scratch build for Fedora 31 here[1]. Could you give it a try, please? Just click the architecture you use, then download packages you've installed: $ rpm -qa | grep syncevolution then update them, from the directory you downloaded them to: $ sudo dnf update ./syncevolution*.rpm Ideally install also debuginfo and debugsource packages for syncevolution, thus any later backtraces will contain line numbers and such. The fix should make it work. Let me know if it helped, please, thus I could make an official release with it. Thanks and bye, Milan [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=38911383 -------------- next part -------------- A non-text attachment was scrubbed... Name: syncevolution-1.5.3-eds-libecal-2.0-b.patch Type: text/x-patch Size: 889 bytes Desc: not available URL: -------------- next part -------------- _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From mail at ericberndt.de Mon Nov 11 17:21:15 2019 From: mail at ericberndt.de (mail at ericberndt.de) Date: Mon, 11 Nov 2019 17:21:15 +0000 Subject: [SyncEvolution] Re: Sync failure - F31 In-Reply-To: References: Message-ID: <20191111172115.2696.16868@new-ml01.vlan13.01.org> Hello Milan you did your jobl!!! For me it is working now, thanks a lot. The only thing i have to look at is that the item 'memo&todo' is deactivated. Only the items Memo an Todo itself should be activated, otherwise all items are transferred on every sync. Greets Eric _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From mcrha at redhat.com Mon Nov 11 17:45:40 2019 From: mcrha at redhat.com (Milan Crha) Date: Mon, 11 Nov 2019 18:45:40 +0100 Subject: [SyncEvolution] Re: Sync failure - F31 In-Reply-To: <20191111172115.2696.16868@new-ml01.vlan13.01.org> References: <20191111172115.2696.16868@new-ml01.vlan13.01.org> Message-ID: <38108c216dc144e92865536189918ccf38c8d519.camel@redhat.com> On Mon, 2019-11-11 at 17:21 +0000, mail at ericberndt.de wrote: > For me it is working now, thanks a lot. Hi, thank you for a quick testing and confirmation. I'm working on an official update for Fedora 31. The version, in which the fix is included, is syncevolution-1.5.3-10. > The only thing i have to look at is that the item 'memo&todo' is > deactivated. > Only the items Memo an Todo itself should be activated, otherwise all > items are transferred on every sync. That might be question for Patrick, I do not know how to debug it. It's likely I made another mistake here, I only do not know how this works, thus cannot tell you whether or where I made such mistake. Thanks again and bye, Milan _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From pyz at brama.com Mon Nov 11 18:27:34 2019 From: pyz at brama.com (Max Pyziur) Date: Mon, 11 Nov 2019 13:27:34 -0500 Subject: [SyncEvolution] Re: Sync failure - F31 In-Reply-To: <38108c216dc144e92865536189918ccf38c8d519.camel@redhat.com> References: <20191111172115.2696.16868@new-ml01.vlan13.01.org> <38108c216dc144e92865536189918ccf38c8d519.camel@redhat.com> Message-ID: On Mon, 11 Nov 2019, Milan Crha wrote: > On Mon, 2019-11-11 at 17:21 +0000, mail at ericberndt.de wrote: >> For me it is working now, thanks a lot. > > Hi, > thank you for a quick testing and confirmation. I'm working on an > official update for Fedora 31. The version, in which the fix is > included, is syncevolution-1.5.3-10. > >> The only thing i have to look at is that the item 'memo&todo' is >> deactivated. >> Only the items Memo an Todo itself should be activated, otherwise all >> items are transferred on every sync. > > That might be question for Patrick, I do not know how to debug it. It's > likely I made another mistake here, I only do not know how this works, > thus cannot tell you whether or where I made such mistake. So this version will probably not be pushed out for distribution just yet. Is that correct? Thank you, Max > Thanks again and bye, > Milan > > _______________________________________________ > SyncEvolution mailing list -- syncevolution at syncevolution.org > To unsubscribe send an email to syncevolution-leave at syncevolution.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From mcrha at redhat.com Tue Nov 12 08:21:59 2019 From: mcrha at redhat.com (Milan Crha) Date: Tue, 12 Nov 2019 09:21:59 +0100 Subject: [SyncEvolution] Re: Sync failure - F31 In-Reply-To: References: <20191111172115.2696.16868@new-ml01.vlan13.01.org> <38108c216dc144e92865536189918ccf38c8d519.camel@redhat.com> Message-ID: On Mon, 2019-11-11 at 13:27 -0500, Max Pyziur wrote: > So this version will probably not be pushed out for distribution just > yet. > Is that correct? Hi, no, I filled that update yesterday. It's in updates-testing right now. You can find it here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-c07bce6764 I'll create a new update in case further changes will be needed. Bye, Milan _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From mail at ericberndt.de Tue Nov 12 05:14:58 2019 From: mail at ericberndt.de (mail at ericberndt.de) Date: Tue, 12 Nov 2019 05:14:58 +0000 Subject: [SyncEvolution] Re: Sync failure - F31 In-Reply-To: <38108c216dc144e92865536189918ccf38c8d519.camel@redhat.com> References: <38108c216dc144e92865536189918ccf38c8d519.camel@redhat.com> Message-ID: <20191112051458.2696.54502@new-ml01.vlan13.01.org> I have to correct my typing from yesterday. The item to deactivate is calendar&todo not memo&todo and i have activated calendar and todo as single items Sorry for my misstyping Eric _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From patrick.ohly at intel.com Tue Nov 12 06:33:32 2019 From: patrick.ohly at intel.com (Patrick Ohly) Date: Tue, 12 Nov 2019 07:33:32 +0100 Subject: [SyncEvolution] Re: Sync failure - F31 In-Reply-To: <20191112051458.2696.54502@new-ml01.vlan13.01.org> References: <38108c216dc144e92865536189918ccf38c8d519.camel@redhat.com> <20191112051458.2696.54502@new-ml01.vlan13.01.org> Message-ID: writes: > I have to correct my typing from yesterday. > > The item to deactivate is calendar&todo not memo&todo > > and i have activated > calendar and todo as single items You are synchronizing against Funambol, according to your command line from the previous email, right? The default for Funambol is to have separate stores for calendar, tasks and memos (https://cgit.freedesktop.org/SyncEvolution/syncevolution/tree/src/templates/servers/Funambol.ini). Are you saying that you configured that differently and that is no longer working? -- Best Regards Patrick Ohly _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From mail at ericberndt.de Wed Nov 13 06:16:31 2019 From: mail at ericberndt.de (mail at ericberndt.de) Date: Wed, 13 Nov 2019 06:16:31 +0000 Subject: [SyncEvolution] Re: Sync failure - F31 In-Reply-To: References: Message-ID: <20191113061631.2696.55799@new-ml01.vlan13.01.org> > Are you saying that you configured that differently and that is no > longer working? No everything is working fine. I only disabled syncing in home/user/.config/syncevolution/default/peers/funambol/sources/calendar+todo/config.ini --> sync = disabled The separated ini files for calendar and todo are activated. /home/user/.config/syncevolution/default/sources/calendar/config.ini --> sync = two-way /home/user/.config/syncevolution/default/sources/todo/config.ini --> sync = two-way Eric _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From pyz at brama.com Mon Nov 11 02:43:20 2019 From: pyz at brama.com (Max Pyziur) Date: Sun, 10 Nov 2019 21:43:20 -0500 Subject: [SyncEvolution] Sync Failure - post F31 upgrade Message-ID: Greetings, Apologies for not immediately following up. The following command, as recommended, works: SYNCEVOLUTION_DEBUG=3 syncevolution -r loglevel=6 memotoo addressbook The logs as printed out are extensive; since this command was a success, I won't include them. However, if someone would need them for diagnostics, I can pass them along. However, when modifying the command to sync the calendar: SYNCEVOLUTION_DEBUG=3 syncevolution -r loglevel=6 memotoo calendar The following output is produced: [DEBUG 00:00:00] SuspendFlags: (re)activating, currently inactive [DEBUG 00:00:00] SuspendFlags: activating signal handler(s) with fds 8->7 [DEBUG 00:00:00] SuspendFlags: catch signal 2 [DEBUG 00:00:00] SuspendFlags: catch signal 15 [INFO 00:00:00] addressbook: inactive [INFO 00:00:00] memo: inactive [INFO 00:00:00] todo: inactive [ERROR 00:00:01] The connection is closed [DEBUG 00:00:01] SuspendFlags: deactivating fds 8->7 [DEBUG 00:00:01] SuspendFlags: close m_receiverFD 7 [DEBUG 00:00:01] SuspendFlags: close m_senderFD 8 [DEBUG 00:00:01] SuspendFlags: done with deactivation When I use the gui interface and isolate the services (Contacts only), syncevolution works. However, if I specify the calendar to be sync'd, I get the message: "The sync process died unexpectedly." Much thanks for getting this far. Hopefully, the calendar issue (and whatever others) are resolvable. Max pyz at brama.com _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From pyz at brama.com Mon Nov 11 02:47:14 2019 From: pyz at brama.com (Max Pyziur) Date: Sun, 10 Nov 2019 21:47:14 -0500 Subject: [SyncEvolution] Re: Sync Failure - post F31 upgrade In-Reply-To: References: Message-ID: To add some more, please see below. On Sun, 10 Nov 2019, Max Pyziur wrote: > > Greetings, > > Apologies for not immediately following up. > > The following command, as recommended, works: > SYNCEVOLUTION_DEBUG=3 syncevolution -r loglevel=6 memotoo addressbook > > The logs as printed out are extensive; since this command was a success, I > won't include them. However, if someone would need them for diagnostics, I > can pass them along. > > However, when modifying the command to sync the calendar: > SYNCEVOLUTION_DEBUG=3 syncevolution -r loglevel=6 memotoo calendar > > The following output is produced: > [DEBUG 00:00:00] SuspendFlags: (re)activating, currently inactive > [DEBUG 00:00:00] SuspendFlags: activating signal handler(s) with fds 8->7 > [DEBUG 00:00:00] SuspendFlags: catch signal 2 > [DEBUG 00:00:00] SuspendFlags: catch signal 15 > [INFO 00:00:00] addressbook: inactive > [INFO 00:00:00] memo: inactive > [INFO 00:00:00] todo: inactive > [ERROR 00:00:01] The connection is closed > [DEBUG 00:00:01] SuspendFlags: deactivating fds 8->7 > [DEBUG 00:00:01] SuspendFlags: close m_receiverFD 7 > [DEBUG 00:00:01] SuspendFlags: close m_senderFD 8 > [DEBUG 00:00:01] SuspendFlags: done with deactivation > > > When I use the gui interface and isolate the services (Contacts only), > syncevolution works. > > However, if I specify the calendar to be sync'd, I get the message: > "The sync process died unexpectedly." > > Much thanks for getting this far. Hopefully, the calendar issue (and whatever > others) are resolvable. > > Max > pyz at brama.com The following is the contents of syncevolution-log.html when syncing for the calendar SySync SyncML Engine 3.4.0.47 Log (p1 of 2) Start of log - SySync SyncML Engine 3.4.0.47 [-- collapse all --][++ expand all ++] + ? [2019-11-10 21:36:41.484] 'loadSystemZoneDefinitions' - Linux system time zones [--][++] [->end] ?[2019-11-10 21:36:41.765] End of 'loadSystemZoneDefinitions' [->top] [2019-11-10 21:36:41.765] SyncML server account: pyziur [2019-11-10 21:36:41.765] client: SyncEvolution 1.5.3 for workstation [2019-11-10 21:36:41.765] device ID: syncevolution-7f2775e9-8678-4baa-9324-5ec5d784b68c [2019-11-10 21:36:41.765] Scanning backend libraries in /usr/lib64/syncevolution/backends/ Loaded backend library syncxmlrpc Loaded backend library synctdepimnotes Loaded backend library synctdepimcal Loaded backend library synctdepimabc Loaded backend library syncsqlite Loaded backend library syncqtcontacts Loaded backend library syncpbap Loaded backend library syncmaemocal Loaded backend library synckcalextended Loaded backend library syncfile Loaded backend library syncecal Loaded backend library syncebook Loaded backend library syncdav Loaded backend library syncactivesync Loaded backend library providergoa Loaded backend library platformtde Loaded backend library platformkde Loaded backend library platformgnome [2019-11-10 21:36:41.767] addressbook: inactive [2019-11-10 21:36:41.767] memo: inactive [2019-11-10 21:36:41.768] todo: inactive [2019-11-10 21:36:41.769] checking password property 'password' in config 'memotoo' with user identity 'pyziur' [2019-11-10 21:36:41.769] loading password from keyring with key user=pyziur server=sync.memotoo.com/syncML [2019-11-10 21:36:41.785] sync password for memotoo: loaded password from GNOME keyring using user=pyziur server=sync.memotoo.com/syncML [2019-11-10 21:36:41.785] checking password property 'databasePassword' in datastore 'calendar' of config 'memotoo' with user identity '' [2019-11-10 21:36:41.790] GLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ?gsettings-backend? [2019-11-10 21:36:42.000] sync is starting, catch signals [2019-11-10 21:36:42.000] SuspendFlags: (re)activating, currently active [2019-11-10 21:36:42.000] ready to sync -------------- next part -------------- _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From deloptes at gmail.com Sun Nov 3 10:16:53 2019 From: deloptes at gmail.com (deloptes) Date: Sun, 3 Nov 2019 11:16:53 +0100 Subject: [SyncEvolution] Problem syncing some accounts Message-ID: Hi Patrik, all, I am testing BT sync with Sailfish OS (successor to N9/meego) There is some strange issue with some Accounts/Contacts. My problem is that I can not edit/modify the contact on the phone, but locally it looks fine What does following mean exactly? When I modify contact locally and sync [2019-11-03 11:13:43.425] Created command 'Status' (incoming) ? [2019-11-03 11:13:43.425] 'processStatus' - Processing incoming Status [-- [++] [->end] [->enclosing] [2019-11-03 11:13:43.425] Started processing Command 'Status' (incoming MsgID=3, CmdID=3) [2019-11-03 11:13:43.425] WARNING: RECEIVED NON-OK STATUS 500 for command 'Replace' (outgoing MsgID=2, CmdID=5) [2019-11-03 11:13:43.425] - TargetRef (remoteID) = '140' [2019-11-03 11:13:43.425] Found matching command 'Replace' for Status [2019-11-03 11:13:43.425] dsConfirmItemOp completed, syncop=replace, localID='', remoteID='140', FAILURE, errorstatus=500 [2019-11-03 11:13:43.425] Status: General error 500 (original op was wants-replace) -> aborting sync with this datastore ? [2019-11-03 11:13:43.425] 'DSAbort' - Aborting datastore sync, abortStatusCode=500, localProblem=no, resumable=yes [--][++] [->end] [->enclosing] [2019-11-03 11:13:43.425] addressbook: testState=TRUE - expected state>='sync_set_ready', found state=='sync_gen_done' [2019-11-03 11:13:43.425] SaveSuspendState not possible (SyncML<1.2 or not supported by DB) [2019-11-03 11:13:43.425] *************** Warning: Datastore flagged aborted (after 0 sec. request processing, 4 sec. total) with REMOTE Status 500 ?[2019-11-03 11:13:43.425] End of 'DSAbort' [->top] [->enclosing] [2019-11-03 11:13:43.425] Status: processed, removed command 'Replace' from status wait queue [2019-11-03 11:13:43.425] Status: command 'Replace' has handled status and allows to be deleted [2019-11-03 11:13:43.425] Deleted command 'Replace' (outgoing MsgID=2, CmdID=5) [2019-11-03 11:13:43.425] Deleted command 'Status' (incoming MsgID=3, CmdID=3) ?[2019-11-03 11:13:43.425] End of 'processStatus' [->top] [->enclosing] [2019-11-03 11:13:43.425] after SessionStep: STEPCMD_OK [2019-11-03 11:13:43.425] before SessionStep: STEPCMD_STEP [2019-11-03 11:13:43.425] after SessionStep: STEPCMD_PROGRESS [2019-11-03 11:13:43.425] addressbook: normal sync done unsuccessfully [2019-11-03 11:13:43.425] addressbook: fatal error (remote, status 500) [2019-11-03 11:13:43.425] before SessionStep: STEPCMD_STEP [2019-11-03 11:13:43.425] after SessionStep: STEPCMD_OK [2019-11-03 11:13:43.425] before SessionStep: STEPCMD_STEP [2019-11-03 11:13:43.425] Calling smlProcessData(NEXT_COMMAND) [2019-11-03 11:13:43.425] Created command 'Status' (incoming) After this sync is a slow sync - there I find [2019-11-03 10:52:27.999] Compared [LOC=bUzWoqkqlB,REM=] with [LOC=,REM=140] (eqMode=3), cmpres=0 [2019-11-03 10:52:27.999] TStdLogicDS::getMatchingItem, found remoteID='140' is equal in content with localID='bUzWoqkqlB' [2019-11-03 10:52:27.999] Slow Sync Match detected - localID='bUzWoqkqlB' matches incoming item [2019-11-03 10:52:27.999] Compared [LOC=,REM=140] with [LOC=bUzWoqkqlB,REM=] (eqMode=5), cmpres=-1 [2019-11-03 10:52:27.999] Newer item determined: Server item is newer and wins [2019-11-03 10:52:27.999] Trying to merge some data from loosing client item into winning server item + [2019-11-03 10:52:27.999] 'ScriptExecute' - Start executing Script, name=mergescript [--][++] [->end] [->enclosing] [2019-11-03 10:52:28.007] mergeWith() final status: thisitem: changed, otheritem: changed (relevant; eqm_none field changes are not indicated) [2019-11-03 10:52:28.007] addressbook: testState=TRUE - expected state>='sync_mode_stable', found state=='sync_set_ready' [2019-11-03 10:52:28.007] ModifyMap called: aEntryType=normal, aLocalID='bUzWoqkqlB, aRemoteid='140', aMapflags=0x0, aDelete=0 [2019-11-03 10:52:28.007] - found entry by entrytype/localID='bUzWoqkqlB' - remoteid='140', mapflags=0x0, changed=0, deleted=1, added=0, markforresume=0, savedmark=0 [2019-11-03 10:52:28.007] - matching entry found - re-activating deleted and/or updating contents if needed [2019-11-03 10:52:28.007] Map entry updated: LocalID='bUzWoqkqlB', RemoteID='140' [2019-11-03 10:52:28.007] Server data was updated by record sent by client, but server updates during non-firsttime slowsyncs are disabled [2019-11-03 10:52:28.007] Record sent by client was updated, but client updates during non-firsttime slowsyncs are disabled [2019-11-03 10:52:28.007] Preventing localID='bUzWoqkqlB' to be sent to client [2019-11-03 10:52:28.007] Item with localID='bUzWoqkqlB' will NOT be sent to client (slowsync match / duplicate prevention) ?[2019-11-03 10:52:28.007] End of 'Process_Item' [->top] [->enclosing] ? [2019-11-03 10:52:28.007] 'issue' - issuing command, Cmd=Status [--][++] [->end] [->enclosing] [2019-11-03 10:52:28.007] Command 'Status': is 2-th counted cmd, cmdsize(+tags needed to end msg)=40, available=16126 (maxfree=262015, freeaftersend=261975, notUsableBufferBytes()=245889) [2019-11-03 10:52:28.007] Status Code 201 issued for Cmd=Add, (incoming MsgID=3, CmdID=4) [2019-11-03 10:52:28.007] - SourceRef (remoteID) = '140' [2019-11-03 10:52:28.007] Status: issued as (outgoing MsgID=3, CmdID=4), not waiting for status [2019-11-03 10:52:28.007] Status: issue finished and not waiting for status -> deleting command [2019-11-03 10:52:28.007] Deleted command 'Status' (outgoing MsgID=3, CmdID=4) [2019-11-03 10:52:28.007] Outgoing Message size is now 296 bytes Thank you in advance regards _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s From patrick.ohly at intel.com Mon Nov 4 15:18:56 2019 From: patrick.ohly at intel.com (Patrick Ohly) Date: Mon, 4 Nov 2019 16:18:56 +0100 Subject: [SyncEvolution] Re: Problem syncing some accounts In-Reply-To: References: Message-ID: deloptes writes: > Hi Patrik, all, > I am testing BT sync with Sailfish OS (successor to N9/meego) > > There is some strange issue with some Accounts/Contacts. > > My problem is that I can not edit/modify the contact on the phone, but > locally it looks fine > > What does following mean exactly? > > When I modify contact locally and sync > > [2019-11-03 11:13:43.425] Created command 'Status' (incoming) > ? > [2019-11-03 11:13:43.425] 'processStatus' - Processing incoming Status [-- > [++] [->end] [->enclosing] > > [2019-11-03 11:13:43.425] Started processing Command 'Status' (incoming > MsgID=3, CmdID=3) > [2019-11-03 11:13:43.425] WARNING: RECEIVED NON-OK STATUS 500 for > command 'Replace' (outgoing MsgID=2, CmdID=5) > [2019-11-03 11:13:43.425] - TargetRef (remoteID) = '140' > [2019-11-03 11:13:43.425] Found matching command 'Replace' for Status > [2019-11-03 11:13:43.425] dsConfirmItemOp completed, syncop=replace, > localID='', remoteID='140', FAILURE, errorstatus=500 > [2019-11-03 11:13:43.425] Status: General error 500 (original op was > wants-replace) -> aborting sync with this datastore This is for a contact modified locally (= your computer?) and then sent to the phone, right? It's impossible to tell from the information found here why the phone refused to update the contact. You'll have to look at sync logs on the phone to determine the reason for the 500 error. Or do trial-and-error runs where you make some educated guess about which change is causing the issue and then trying just that in isolation. -- Best Regards Patrick Ohly _______________________________________________ SyncEvolution mailing list -- syncevolution at syncevolution.org To unsubscribe send an email to syncevolution-leave at syncevolution.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s