From patrick.ohly at intel.com Tue Apr 26 07:17:27 2016 From: patrick.ohly at intel.com (Patrick Ohly) Date: Tue, 26 Apr 2016 09:17:27 +0200 Subject: [SyncEvolution] Help needed In-Reply-To: <1638499257.781812.1458129112688.JavaMail.yahoo@mail.yahoo.com> References: <1638499257.781812.1458129112688.JavaMail.yahoo@mail.yahoo.com> Message-ID: <1461655047.24271.24.camel@intel.com> On Wed, 2016-03-16 at 11:51 +0000, Emanoil Kotsev wrote: > Hi > I have found a resolution to the problem with the blocked parent/child > in sync. After thinking for while about what you said in your previous > postings, I inspected the configure options and configure output. I > found out that gio-gdbus was enabled by default together with dbus. So > I added > --without-gio-gdbus > to the configure options and now it runs without blocking. Good that you found a workaround, but there's still something fishy about this interaction between TDEPIM and gdbus. I was hoping to remove support for libdbus at some point; if you depend on it, I'll have to keep maintaining two D-Bus bindings. Not that I am changing much at the moment, so don't worry ;-} -- 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 Tue Apr 26 19:29:34 2016 From: deloptes at gmail.com (deloptes) Date: Tue, 26 Apr 2016 21:29:34 +0200 Subject: [SyncEvolution] Help needed References: <1638499257.781812.1458129112688.JavaMail.yahoo@mail.yahoo.com> <1461655047.24271.24.camel@intel.com> Message-ID: Patrick Ohly wrote: > Good that you found a workaround, but there's still something fishy > about this interaction between TDEPIM and gdbus. I was hoping to remove > support for libdbus at some point; if you depend on it, I'll have to > keep maintaining two D-Bus bindings. Not that I am changing much at the > moment, so don't worry ;-} Thanks, what would be the "desirable" way to configure? I looked into the options but have no idea how dbus can be disabled and gio-gdbus enabled. regards _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From patrick.ohly at intel.com Tue Apr 26 20:01:34 2016 From: patrick.ohly at intel.com (Patrick Ohly) Date: Tue, 26 Apr 2016 22:01:34 +0200 Subject: [SyncEvolution] Help needed In-Reply-To: References: <1638499257.781812.1458129112688.JavaMail.yahoo@mail.yahoo.com> <1461655047.24271.24.camel@intel.com> Message-ID: <1461700894.4820.7.camel@intel.com> On Tue, 2016-04-26 at 21:29 +0200, deloptes wrote: > Patrick Ohly wrote: > > > Good that you found a workaround, but there's still something fishy > > about this interaction between TDEPIM and gdbus. I was hoping to remove > > support for libdbus at some point; if you depend on it, I'll have to > > keep maintaining two D-Bus bindings. Not that I am changing much at the > > moment, so don't worry ;-} > > Thanks, what would be the "desirable" way to configure? The default that you were using before is the desirable one, with gdbus picked by default instead of libdbus. Unfortunately it is the one which didn't work for you :-/ -- 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 Tue Apr 26 22:59:33 2016 From: deloptes at gmail.com (deloptes) Date: Wed, 27 Apr 2016 00:59:33 +0200 Subject: [SyncEvolution] Help needed References: <1638499257.781812.1458129112688.JavaMail.yahoo@mail.yahoo.com> <1461655047.24271.24.camel@intel.com> <1461700894.4820.7.camel@intel.com> Message-ID: Patrick Ohly wrote: > On Tue, 2016-04-26 at 21:29 +0200, deloptes wrote: >> Patrick Ohly wrote: >> >> > Good that you found a workaround, but there's still something fishy >> > about this interaction between TDEPIM and gdbus. I was hoping to remove >> > support for libdbus at some point; if you depend on it, I'll have to >> > keep maintaining two D-Bus bindings. Not that I am changing much at the >> > moment, so don't worry ;-} >> >> Thanks, what would be the "desirable" way to configure? > > The default that you were using before is the desirable one, with gdbus > picked by default instead of libdbus. Unfortunately it is the one which > didn't work for you :-/ > I understand, thanks. As you said, lets put it on hold for the moment, though I think I know where it might be coming from. I just need to prove it, but I think tqt automatically links to dbus as it seems to be using the interface for who knows what. At least I do not see a reason for libvcard being linked to dbus. Just let me know upfront when you are planning to remove the dbus support. I would need to raise this question with the TDE team. However at the moment with syncevolution 1.5.1 it seems to work fine for me. There are couple of difficulties on the TDE side, but with few additional steps I am able to sync my phone again almost without issues for the first time since 2006, the time I had a Palm III. This is great - thank you once again! For the record I have following installed at the moment $ dpkg -l | grep dbus | grep dev ii libdbus-1-dev:amd64 1.8.20-0+deb8u1 amd64 simple interprocess messaging system (development headers) ii libdbus-1-tqt-dev 4:14.0.3-0debian8.0.0+0 amd64 dbus bindings for the Trinity Qt [TQt] interface ii libdbus-glib-1-dev 0.102-1 amd64 simple interprocess messaging system (GLib interface) ii python-dbus-dev 1.2.0-2 all main loop integration development files for python-dbus and this is basic check $ ldd /opt/trinity/lib/libvcard.so | grep libdbus libdbus-1-tqt.so.0 => /usr/lib/libdbus-1-tqt.so.0 (0x00007f14bc67a000) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007f14b9877000) $ ldd /opt/trinity/lib/libkaddressbook.so | grep libdbus libdbus-1-tqt.so.0 => /usr/lib/libdbus-1-tqt.so.0 (0x00007f69dcfef000) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007f69db88f000) $ ldd /opt/trinity/lib/libtdeabc.so | grep dbus libdbus-1-tqt.so.0 => /usr/lib/libdbus-1-tqt.so.0 (0x00007f02ffcc9000) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007f02fd8d2000) _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From deloptes at gmail.com Sat Apr 2 21:04:59 2016 From: deloptes at gmail.com (deloptes) Date: Sat, 2 Apr 2016 23:04:59 +0200 Subject: [SyncEvolution] Calendar+Todo and Memo Message-ID: Hi all, I apologize for disturbing you once again, however I found out that the older Nokia 5530 has Calendar+Todo and Memo in one. So when I use following configuration I get everything to the TDE Calendar when just syncing the calendar part. This is great, however I can not push back Todo or Memo items for obvious reasons. How can I modify the configuration such that I am able to use all of it. I read about the virtual, but could not come up with a decision what I should put where in the config. syncevolution --configure \ --template ${template} \ syncURL=obex-bt://${deviceAddress} \ peerIsClient=1 \ dumpData=0 \ printChanges=0 \ addressbook/backend=tdepim-contacts \ addressbook/database="kxXrRFzP9c" \ addressbook/databaseFormat="text/vcard" \ calendar/uri="Calendar" \ calendar/backend=tdepim-calendar \ calendar/database="ZsPZokpoTg" \ calendar/databaseFormat="text/calendar" \ todo/backend=tdepim-tasks \ todo/database="ZsPZokpoTg" \ todo/databaseFormat="text/calendar" \ memo/backend=tdepim-memos \ memo/database="ZsPZokpoTg" \ memo/databaseFormat="text/calendar" \ ${server} addressbook calendar todo memo *template is N900 The plugins work great so far address book and calendar sync up well with this Nokia 5530. I'm getting confidence to try it out on the N9 next. Thanks for your support so far. regards _______________________________________________ SyncEvolution mailing list SyncEvolution at syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution From patrick.ohly at intel.com Tue Apr 26 06:36:54 2016 From: patrick.ohly at intel.com (Patrick Ohly) Date: Tue, 26 Apr 2016 08:36:54 +0200 Subject: [SyncEvolution] Calendar+Todo and Memo In-Reply-To: References: Message-ID: <1461652614.24271.16.camel@intel.com> On Sat, 2016-04-02 at 23:04 +0200, deloptes wrote: > Hi all, > > I apologize for disturbing you once again, however I found out that the > older Nokia 5530 has Calendar+Todo and Memo in one. > So when I use following configuration I get everything to the TDE Calendar > when just syncing the calendar part. This is great, however I can not push > back Todo or Memo items for obvious reasons. > > How can I modify the configuration such that I am able to use all of it. I > read about the virtual, but could not come up with a decision what I should > put where in the config. The easiest approach would be to do something as in https://syncevolution.org/wiki/kde-akonadi: first configure your local databases, then add peers as described elsewhere. That means: syncevolution --configure \ addressbook/backend=tdepim-contacts \ addressbook/database="kxXrRFzP9c" \ addressbook/databaseFormat="text/vcard" \ calendar/uri="Calendar" \ calendar/backend=tdepim-calendar \ calendar/database="ZsPZokpoTg" \ calendar/databaseFormat="text/calendar" \ todo/backend=tdepim-tasks \ todo/database="ZsPZokpoTg" \ todo/databaseFormat="text/calendar" \ memo/backend=tdepim-memos \ memo/database="ZsPZokpoTg" \ memo/databaseFormat="text/calendar" \ @default addressbook calendar todo memo And then add the phone (https://syncevolution.org/wiki/sync-your-phone-bluetooth): syncevolution --configure \ --template nokia \ --sync-property syncURL=obex-bt://${deviceAddress} \ nokia_5530 Because "nokia_5530" = "nokia_5530 at default", it will use the addressbook/calendar/todo/memo databases defined in that context earlier. The template has a calendar+todo entry that matches the data on the phone and splits it locally into calendar and todo. -- 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.