Re: [SyncEvolution] syncevolution and a radicale caldev server
by Patrick Ohly
On Fri, 2012-02-17 at 15:14 +0100, Gregor Horvath wrote:
> Am Fri, 17 Feb 2012 11:12:52 +0100
> schrieb Patrick Ohly <patrick.ohly(a)intel.com>:
>
> > On Tue, 2012-02-14 at 15:57 +0100, Patrick Ohly wrote:
> > > But as Radicale is an example where multiple databases are possible
> > > (in
> > > contrast to Google), it's worth spelling out explicitly how such a
> > > config can be created:
> >
> > [...]
> >
> > William, did this work?
> >
> > Perhaps you (or someone else) has the time to turn the instructions
> > into a proper HOWTO? I created a place holder Wiki page for it here:
> > http://syncevolution.org/wiki/synchronizing-radicale
> >
> >
William sent me some debug logs, but then ran out of time. So I've
installed Radicale myself and found an issue that'll break
SyncEvolution: items reported by the server include double slashes in
the path.
<multistatus xmlns="DAV:" xmlns:C="urn:ietf:params:xml:ns:caldav">
<response>
<href>/public_user/calendar/calendar_1//1234567890(a)dummy.ics</href>
^^
SyncEvolution will then use /1234567890(a)dummy.ics as path in future
requests, which Radicale rejects with either 404 or 401 errors.
I'll work around that in SyncEvolution. I'm not sure whether there is a
solution with 1.2.2.
Have you considered Calypso (http://keithp.com/blogs/calypso/)? I don't
know yet whether it works with SyncEvolution; if there is interest, then
I will try it.
> I am trying to do the same thing (with one calender to start with)
> N900 <-> radicale but it did not work, because it seems the Maemo
> calendar is not found:
>
> http://pastebin.com/huMXDsEx
>
> What I am doing wrong?
You have additional spaces after your \ character. The slash must be at
the end of each line.
--
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.
5 years, 6 months
[SyncEvolution] Best way to start the server
by NeonJohn
Hi all,
I have SyncEvolution and my DroidX happily chatting with each other but
now I have another question. How to start the server automatically at
boot time.
I made an /etc/rc.d script that started the server just fine but it
starts the server in the root context. I found that out by watching
SyncML on my Droid delete everything because, of course, there are no
Evolution databases for root.
I tried starting it using Gnome's start-up tasks options. That also
started the server but it could not access access tasks nor notes
(access denied).
So now I start it manually after reboot with
nohup sudo syncevo-http-server -d http://localhost:9000/syncevolution &
Which works perfectly but requires me to remember to do it each time I boot.
Any suggestions on how to automate this?
Thanks,
John
--
John DeArmond
Tellico Plains, Occupied TN
http://www.fluxeon.com <-- THE source for induction heaters
http://www.neon-john.com <-- email from here
http://www.johndearmond.com <-- Best damned Blog on the net
PGP key: wwwkeys.pgp.net: BCB68D77
5 years, 11 months
[SyncEvolution] MS Exchange and KDE synchronization: Colleague's calendar?
by Stefanie Dargel
Hi,
I tried the MS Exchange and KDE synchronization as described in the wiki. It works with my calendar, but I would like to see my colleague's in KDE kmail as well. Is there any way to do that? I tried to use my colleague's email address as user(a)example.com in the wiki and my username and password for "*workdomain\username*". But that gave me my calendar once again.
Thank you for any help or hints!
Stefanie
(I'm not subscribed to this list, please keep me in cc)
6 years
[SyncEvolution] documentation update, enhanced command line
by Patrick Ohly
Hello!
The "Getting the concepts clear" mail thread and a private email
exchange with Todd identified several shortcomings in the documentation
and/or implementation. This is my attempt to address those. A diff and
the full modified README.rst are attached.
Some of these changes will require changes in the implementation.
In short, what I am trying to achieve is:
* Better explain what local sync is and how it involves two sync
configs. "originating config" gets introduces instead of just
"sync config".
* Better explain the relationship between contexts, sync configs,
and source configs ("a sync config can use the source configs in
the same context").
* An entire section on config properties in the terminology
section.
* Less focus on conflict resolution, as suggested by Graham.
* Remove the hard-coded "target-config" name. It still needs to be
there as fallback for existing configs or users continuing to
use the current instructions.
* Fix examples that became invalid when fixing the password
storage/lookup mechanism for GNOME keyring in 1.4. I noticed
that the username=email-address part should be handled without
additional properties.
* Fix WebDAV with DNS auto-discovery. Few servers support it, so
this hasn't been noticed before.
* Fix the implicit command line magic where it does some
consistency checks when creating new configs. Not exactly sure
yet how.
I ran out of stream after updating the terminology section, the "command
line conventions", "Synchronization beyond SyncML" and "CalDAV and
CardDAV". It's possible that the other sections also contain slightly
incorrect usage of the terminology or are simply out-dated.
--
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.
6 years
[SyncEvolution] Problems when auth to google carddav
by Emfox Zhou
Hello, I've try to sync google contacts to my debian box.
The syncevolution version is 1.4-1.1, I did according to the manual:
emfox@XXXX:~$ syncevolution --configure --template WebDAV username=
XXXXX(a)gmail.com password=XXXX database=
https://google.com:443/carddav/v1/principals/XXXX%40gmail.com/lists/default/
target-config@webdav
[INFO] addressbook: looking for databases...
[INFO] addressbook: okay
[INFO] calendar: looking for databases...
[INFO] calendar: no database to synchronize
[INFO] memo: looking for databases...
[INFO] memo: no database to synchronize
[INFO] todo: looking for databases...
[INFO] todo: no database to synchronize
emfox@XXXX:~$ syncevolution --configure --template SyncEvolution_Client
syncURL=local://@webdav sslverifyserver=0 username= password= webdav
addressbook
[INFO] addressbook: looking for databases...
[INFO] addressbook: backend failed: error code from SyncEvolution
authorization failed (remote, status 401): PROPFIND: Neon error code 3 =
NE_AUTH, HTTP status 401: Could not authenticate to server: ignored
GoogleLogin challenge
[ERROR] addressbook: backend failed: error code from SyncEvolution
authorization failed (remote, status 401): PROPFIND: Neon error code 3 =
NE_AUTH, HTTP status 401: Could not authenticate to server: ignored
GoogleLogin challenge
I searched the maillist, and realised it may be an ssl issue, so I add the
sslverifyserver=0 option.
What could be the problem?
--
Emfox Zhou
GnuPG Public Key: 0xF7142EC2
6 years
[SyncEvolution] SyncEvolution 1.4.99.3
by Patrick Ohly
About 1.4.99.3
==============
This release enhances CalDAV/CardDAV and PBAP syncing and fixes some
problems. The enhanced conflict handling introduced 1.4.99.2 was
unintentionally limited to syncs with EDS on the server side; it is
now also available for example in WebDAV<->SyncML bridge setups.
Details:
* CardDAV: implement read-ahead
Instead of downloading contacts one-by-one with GET, SyncEvolution now
looks at contacts that are most likely going to be needed soon and
gets all of them at once with addressbook-multiget REPORT.
The number of contacts per REPORT is 50 by default, configurable by
setting the SYNCEVOLUTION_CARDDAV_BATCH_SIZE env variable.
This has two advantages:
- It avoids round-trips to the server and thus speeds up a large
download (100 small contacts with individual GETs took 28s on
a fast connection, 3s with two REPORTs).
- It reduces the overall number of requests. Google CardDAV is known
to start issuing intermittent 401 authentication errors when the
number of contacts retrieved via GET is too large. Perhaps this
can be avoided with addressbook-multiget.
* Google Calendar: remove child hack, improve alarm hack (FDO #63881)
Google recently enhanced support for RECURRENCE-ID, so SyncEvolution
no longer needs to replace the property when uploading a single
detached event with RECURRENCE-ID. However, several things are still
broken in the server, with no workaround in SyncEvolution:
- Removing individual events gets ignored by the server;
a full "wipe out server data" might work (untested).
- When updating the parent event, all child events also get
updated even though they were included unchanged in the data
sent by SyncEvolution.
- The RECURRENCE-ID of a child event of an all-day recurring event
does not get stored properly.
- The update hack seems to fail for complex meetings: uploading them
once and then deleting them seems to make uploading them again
impossible.
All of these issues were reported to Google and are worked on there,
so perhaps the situation will improve. In the meantime, syncing with
Google CalDAV should better be limited to:
- Downloading a Google calendar in one-way mode.
- Two-way syncing of simple calendars without complex meeting
serieses.
While updating the Google workarounds, the alarm hack (sending a
new event without alarms twice to avoid the automatic server side
alarm) was simplified. Now the new event gets sent only once with a
pseudo-alarm.
* ephemeral sync: don't write binfile client files (FDO #55921)
When doing PBAP caching, we don't want any meta data written because
the next sync would not use it anyway. With the latest libsynthesis
we can configure "/dev/null" as datadir for the client's binfiles and
libsynthesis will avoid writing them.
The PIM manager uses this for PBAP syncing automatically. For testing
it can be enabled by setting the SYNCEVOLUTION_EPHEMERAL env variable.
* PBAP: avoid empty field filter
Empty field filter is supposed to mean "return all supported
fields". This used to work and stopped working with Android phones
after an update to 4.3 (seen on Galaxy S3); now the phone only
returns the mandatory TEL, FN, N fields.
The workaround is to replace the empty filter list with the list of
known and supported properties. This means we only pull data we really
need, but it also means we won't get to see any additional properties
that the phone might support.
* PBAP: transfer in chunks (FDO #77272)
If enabled via env variables, PullAll transfers will be limited to
a certain numbers contacts at different offsets until all data got
pulled. See PBAP README for details.
When transfering in chunks, the enumeration of contacts for the engine
no longer matches the PBAP enumeration. Debug output uses "offset #x"
for PBAP and "ID y" for the engine.
* PBAP: remove transfer via pipe
Using a pipe was never fully supported by obexd (blocks
obexd). Transfering in suitably sized chunks (FDO #77272) will be a
more obexd friendly solution with a similar effect (not having to
buffer the entire address book in memory).
* engine: enable batching by default (FDO #52669)
This reverts commit c435e937cd406e904c437eec51a32a6ec6163102.
Commit 7b636720a in libsynthesis fixes an unitialized memory read in
the asynchronous item update code path.
Testing confirms that we can now used batched writes reliably with EDS
(the only backend currently supporting asynchronous writes +
batching), so this change enables it again also for local and
SyncEvolution<->SyncEvolution sync (with asynchronous execution of
contact add/update overlapped with SyncML message exchanges) and other
SyncML syncs (with changes combined into batches and executed at the
end of each message).
* datatypes: fix contact caching
Adding grouping to the contact datatype in 1.4.99.2 broke PBAP caching: when
sending an empty URL, for example, during the sync, the parsed contact
had different field arrays than the locally stored contact, because the
latter was saved without the empty URL.
This caused the field-based comparison to detect a difference even when
the final, reencoded contact wasn't different at all.
To solve this, syncing now uses the same "don't send empty properties"
configuration as local storages. Testing shows that this resolves
the difference for EDS.
A more resilient solution would be to add a check based on the encoded
data, but that's more costly performance wise.
* datatypes: fix vCard handling
The new "preserve repeating properties during conflict resolution"
feature from 1.4.99.2 was only active when using EDS as storage. The relevant
merge script must be applied to all datatypes, not just the EDS
flavor.
The feature was also unintentionally active when running in
caching mode. This caused two problems:
- The cached item was updated even though only the
ordering of repeating properties had been modified during
merging.
- The merged item was sent back to the client side, which
was undesirable (caching is supposed to be one-way) or even
impossible (PBAP is read-only, causing sync failures eith error 20030).
We must check for caching mode and disable merging when it is active.
We also must not tell the engine that we updated the photo property
in the winning item, because then that item would get sent to the
read-only side of the sync.
Perhaps a better solution would be to actually tell the engine
that the remote side is read-only when we activate caching mode.
* datatypes: avoid PHOTO corruption during merge (FDO #77065)
When handling an update/update conflict (both sides of the sync have an
updated contact) and photo data was moved into a local file by EDS, the engine
merged the file path and the photo data together and thus corrupted the photo.
The engine does not know about the special role of the photo property.
This needs to be handled by the merge script, and that script did not
cover this particular situation. Now the loosing side is cleared,
causing the engine to then copy the winning side over into the loosing
one.
Found by Renato Filho/Canonical when testing SyncEvolution for Ubuntu 14.04.
* PBAP syncing: updated photo not always stored
Because photo data was treated like a C string, changes after any
embedded null byte were ignored during a comparison.
* PIM: fix phone number normalization
The parsed number always has a country code, whereas SyncEvolution expected it
to be zero for strings without an explicit country code. This caused a caller
ID lookup of numbers like "089788899" in DE to find only telephone numbers in
the current default country, instead of being more permissive and also finding
"+189788899". The corresponding unit test was broken and checked for the wrong
result. Found while investigating an unrelated test failure when updating
libphonenumber.
* Various compiler problems and warnings fixed; compiles with
--with-warnings=fatal on current Debian Testing and Ubuntu Trusty
(FDO #79316).
Upgrading from releases <= 1.3.99.4:
------------------------------------
If the value of "username/databaseUser/proxyUser" contains a colon,
the "user:" prefix must be added to the value, to continue treating it
like a plain user name and not some reference to an unknown identity
provider (like "id:", "goa:", "signon:", etc.).
The lookup of passwords in GNOME Keyring was updated slightly in
1.3.99.5. It may be necessary to set passwords anew if the old one is
no longer found.
Upgrading from release 1.2.x:
-----------------------------
The sync format of existing configurations for Mobical (aka Everdroid)
must be updated manually, because the server has encoding problems when
using vCard 3.0 (now the default for Evolution contacts):
syncevolution --configure \
syncFormat=text/x-vcard \
mobical addressbook
The Funambol template explicitly enables usage of the
"refresh-from-server" sync mode to avoid getting throttled with 417
'retry later' errors. The same must be added to existing configs
manually:
syncevolution --configure \
enableRefreshSync=TRUE \
funambol
Upgrading from releases before 1.2:
-----------------------------------
Old configurations can still be read. But writing, as it happens
during a sync, must migrate the configuration first. Releases >= 1.2
automatically migrates configurations. The old configurations
will still be available (see "syncevolution --print-configs") but must
be renamed manually to use them again under their original names with
older SyncEvolution releases.
Source, Installation, Further information
=========================================
http://syncevolution.org/blogs/pohly/2014/syncevolution-14992-released
Source code bundles for users are available in
http://downloads.syncevolution.org/syncevolution/sources
and the original source is in the git repositories
http://cgit.freedesktop.org/SyncEvolution/
i386, lpia and amd64 binaries for Debian-based distributions are
available via the "unstable" syncevolution.org repository. Add the
following entry to your /apt/source.list:
deb http://downloads.syncevolution.org/apt unstable main
Then install "syncevolution-evolution", "syncevolution-kde" and/or
"syncevolution-activesync".
These binaries include the "sync-ui" GTK GUI and were compiled for
Ubuntu 10.04 LTS (Lucid), except for ActiveSync binaries which were
compiled for Debian Wheezy, Ubuntu Saucy and Ubuntu Trusty. A backend
for Ubuntu Online Accounts was compiled on Ubuntu Saucy. The packages
mentioned above are meta-packages which pull in suitable packages
matching the distro during installation.
Older distributions like Debian 4.0 (Etch) can no longer be supported
with precompiled binaries because of missing libraries, but the source
still compiles when not enabling the GUI (the default).
The same binaries are also available as .tar.gz and .rpm archives in
http://downloads.syncevolution.org/syncevolution/. In contrast
to 0.8.x archives, the 1.x .tar.gz archives have to be unpacked and the
content must be moved to /usr, because several files would not be found
otherwise.
After installation, follow the
http://syncevolution.org/documentation/getting-started steps.
--
Patrick Ohly, on behalf of everyone who has helped
to make SyncEvolution possible:
http://syncevolution.org/about/contributors
6 years
[SyncEvolution] Encoding problems
by Leszek Piątek jr
Hi!
I'm trying to set up a SyncML server to sync old mobiles through
Zimbra server. I manage to set up such thing using configuration:
syncevolution --configure \
--template webdav \
--sync-property syncURL= \
--sync-property peerIsClient=1 \
--sync-property remoteDeviceId=${deviceID} \
--sync-property username=${peer} \
--sync-property password=${pass} \
--sync-property keyring=false \
--source-property sync=two-way \
--source-property addressbook/database=${URL}/Contacts/ \
--source-property addressbook/backend=carddav \
--source-property addressbook/databaseUser=${peer} \
--source-property addressbook/databasePassword=${pass} \
--source-property calendar/database=${URL}/Calendar/ \
--source-property calendar/backend=caldav \
--source-property calendar/databaseUser=${peer} \
--source-property calendar/databasePassword=${pass} \
--source-property memo/database=${URL}/Tasks/ \
--source-property todo/database=${URL}/Tasks/ \
${peer}
The problem I get is that all calendar/contact entries written in non
ASCII are changed to underscore "_" sign. Have anyone any idea what
could be wrong?
I've just check if:
--source-property addressbook/syncFormat=text/x-vcard \
--source-property addressbook/forceSyncFormat=true \
Doesn't help but unfortunately no...
root@zimbra:~/sync# syncevolution --version
SyncEvolution 1.4.99.2 (pre-release)
using libedataserver-1.2.so.15
using libebook-1.2.so.12
using libebook-1.2.so.12
using libecal-1.2.so.10
using libecal-1.2.so.10
using libbluetooth.so.3
Loading backend library /usr/lib/syncevolution/backends/syncxmlrpc.so
Loading backend library /usr/lib/syncevolution/backends/syncsqlite.so
Loading backend library /usr/lib/syncevolution/backends/syncqtcontacts.so
Loading backend library /usr/lib/syncevolution/backends/syncpbap.so
Loading backend library /usr/lib/syncevolution/backends/syncmaemocal.so
Loading backend library /usr/lib/syncevolution/backends/synckcalextended.so
Loading backend library /usr/lib/syncevolution/backends/syncfile.so
Loading backend library /usr/lib/syncevolution/backends/syncecal.so
Loading backend library /usr/lib/syncevolution/backends/syncebook.so
Loading backend library /usr/lib/syncevolution/backends/syncdav.so
Loading backend library /usr/lib/syncevolution/backends/syncaddressbook.so
Loading backend library /usr/lib/syncevolution/backends/providergoa.so
Loading backend library /usr/lib/syncevolution/backends/platformgnome.so
---
Pozdrawiam
Leszek Piątek jr
6 years
[SyncEvolution] Droid X/syncevolution problems
by NeonJohn
Back again. I had everything working using SyncML on the Droid and then
Canonical did an update.... Broke everything.
Ubuntu 14.04LTS on the server side.
SyncEvolution 1.4.1, updated from this page
https://syncevolution.org/documentation/installation
Incidentally, this procedure does not work for Ubuntu. What DOES work
is to put the
deb http://downloads.syncevolution.org/apt stable main
in
/etc/apt/sources.list
And then fire off the Snynaptics package manager. Do an update and the
new version will appear. It automatically de-installs the old version.
I used this page
https://syncevolution.org/wiki/synchronizing-evolution-http-howto
For my initial, first setup. My version of the configure command is
syncevolution --configure --template SyncEvolution_Client \
--sync-property remoteDeviceId=f87b7a5a6b3c-A000002278B6A4_pro \
--sync-property username=fredandjake \
--sync-property password=xxxxxxxx \
--source-property addressbook/uri=contacts \
--source-property calendar/uri=events \
--source-property todo/uri=tasks \
--source-property memo/uri=notes \
default
When I ran that command, it outputted the following:
[INFO] addressbook: looking for databases...
[INFO] addressbook: okay
[INFO] calendar: looking for databases...
[INFO] calendar: okay
[INFO] memo: looking for databases...
[INFO] memo: okay
[INFO] todo: looking for databases...
[INFO] todo: okay
After the above config, the connection would time out after several
minutes. Using a packet sniffer, I saw SyncML send the userid and the
MD5 password hash but no response from the server.
Prowling through the actual config files and found that in
~/.config/syncevolution/default/peers/default/config.ini
--config had set the password to -. - tells syncevolution to stop and
prompt for a password, something it obviously can't do since it's
running as a daemon. I put the correct password in the "password = "
field and the address and calendar synced properly.
Tasks and notes remain broken, even after several days of troubleshooting.
With the todo list, SyncML syncs with SOMETHING, just not Evolution. On
the initial run I got a successful sync but 0 contents. There are about
30 in Evolution. I made a dummy entry on the Droid and that was
transmitted to the server and SyncML now shows 1 task. I haven't been
able to find out where the syncevolution is putting this data.
Notes is simply dead. I've tried every name I can think of but get the
"not found" error message. Here's the console output on an unsuccessful
notes run
[DEBUG 2014-07-14 14:33:48,404] twisted: Log opened.
[DEBUG 2014-07-14 14:33:48,404] syncevo-http: connecting to D-Bus
session with DISPLAY=:0.0 DBUS_SESSION_BUS_ADDRESS=
[DEBUG 2014-07-14 14:33:48,409] twisted: Site starting on 9000
[DEBUG 2014-07-14 14:33:48,409] twisted: Starting factory
<twisted.web.server.Site instance at 0xa55494c>
[INFO 2014-07-14 14:33:48,409] syncevo-http: listening on port 9000
[DEBUG 2014-07-14 14:34:04,429] syncevo-http: POST from 192.168.1.100
config type application/vnd.syncml+wbxml session None args {} length 777
[INFO 2014-07-14 14:34:04,429] syncevo-http: new SyncML session for
192.168.1.100
[DEBUG 2014-07-14 14:34:04,429] syncevo-http: processing incoming
message of type application/vnd.syncml+wbxml and length 777, binary data
[DEBUG 2014-07-14 14:34:04,429] syncevo-http: requesting new session
[DEBUG 2014-07-14 14:34:04,492] syncevo-http: started new connection
/org/syncevolution/Connection/18546568281405362845
[DEBUG 2014-07-14 14:34:04,538] syncevo-http: added new SyncML session
<__main__.SyncMLSession instance at 0xa55a7ec>
[INFO 2014-07-14 14:34:04,538] syncevo-dbus-server:
/org/syncevolution/Server: ready to run
[INFO 2014-07-14 14:34:04,539] syncevo-dbus-server:
/org/syncevolution/Server: matched deviceID
f87b7a5a6b3c-A000002278B6A4_pro against config default
(/home/jgd/.config/syncevolution/default/peers/default)
[DEBUG 2014-07-14 14:34:04,706] syncevo-http: reply session
18546568281405362845 connection
/org/syncevolution/Connection/18546568281405362845 (active
/org/syncevolution/Connection/18546568281405362845) final 0 data len
9584 dbus.Dictionary({dbus.UTF8String('URL'): dbus.UTF8String('')},
signature=dbus.Signature('ss'))
[DEBUG 2014-07-14 14:34:04,707] syncevo-http: processing outgoing
message of type application/vnd.syncml+wbxml and length 9584, binary data
[DEBUG 2014-07-14 14:34:04,707] twisted: 192.168.1.100 - -
[14/Jul/2014:18:34:04 +0000] "POST /syncevolution HTTP/1.1" 200 9584 "-"
"SySync Client PocketPC PRO/V3.0.1 V3.4.0.72 Android/2.3.4 Android DROIDX"
[DEBUG 2014-07-14 14:34:04,707] syncevo-http: done with request in
session None, error None
-------------------------------
Running
$ syncevolution --print-databases
I get:
CalDAV:
select database via absolute URL, set username/password to scan, set
syncURL to base URL if server does not support auto-discovery (<path>)
CalDAVTodo:
select database via absolute URL, set username/password to scan, set
syncURL to base URL if server does not support auto-discovery (<path>)
CalDAVJournal:
select database via absolute URL, set username/password to scan, set
syncURL to base URL if server does not support auto-discovery (<path>)
CardDAV:
select database via absolute URL, set username/password to scan, set
syncURL to base URL if server does not support auto-discovery (<path>)
Evolution Address Book = Evolution Contacts = evolution-contacts:
Personal (local:system) <default>
Evolution Calendar = evolution-calendar:
Personal (local:system) <default>
Evolution Task List = Evolution Tasks = evolution-tasks:
Personal (local:system) <default>
Evolution Memos = evolution-memos:
[ERROR] KDE Address Book = KDE Contacts = kde-contacts:
[ERROR] accessing databases failed
[ERROR] Akonadi is not running. It can be started with 'akonadictl start'.
[ERROR] KDE Calendar = kde-calendar:
[ERROR] accessing databases failed
[ERROR] Akonadi is not running. It can be started with 'akonadictl start'.
[ERROR] KDE Task List = KDE Tasks = kde-tasks:
[ERROR] accessing databases failed
[ERROR] Akonadi is not running. It can be started with 'akonadictl start'.
[ERROR] KDE Memos = kde-memos:
[ERROR] accessing databases failed
[ERROR] Akonadi is not running. It can be started with 'akonadictl start'.
------------------
I've tried every combination of "memo, memos, note, notes and
evolution-memos in the SyncML Notes URL field but nothing works.
I've been working with Beat Forster at Synthesis (best tech support I've
ever gotten!). We're both stumped. Patrick, he said that you might be
able to help with this.
Todo list I can kinda live without but I gotta have Memos. I have a ton
of both personal and work-related stuff in there.
Any help will be most gratefully appreciated.
John
--
John DeArmond
Tellico Plains, Occupied TN
http://www.fluxeon.com <-- THE source for induction heaters
http://www.neon-john.com <-- email from here
http://www.johndearmond.com <-- Best damned Blog on the net
PGP key: wwwkeys.pgp.net: BCB68D77
6 years
[SyncEvolution] Will activesyncd work with Exchange 2007?
by Yury Vidineev
Hello
I'm trying to set up contacts sync with Exchange 2007 as described in this
manual: https://syncevolution.org/wiki/ms-exchange-and-kde-synchronization
print-databases works as expected:
$ syncevolution --print-databases username=my.email(a)domain.com backend=eas-
contacts
eas-contacts:
Contacts (2) <default>
But I can't export any contact (export return nothing):
$ syncevolution --export - target-config@Work contacts
$ EAS_DEBUG=3 /usr/libexec/activesyncd
(process:30138:0x10db850): libeas-WARNING **:Found password in GConf, writing
it to Gnome Keyring
(process:30138:0x10db850): libeas-Message:parent_name[Collection] status = [1]
(process:30138:0x10db850): libeas-WARNING **:Found no <Responses> element or
<Commands> element>
(process:30138:0x10db850): libeas-WARNING **:folder_sync response XML is empty
(process:30138:0x10db850): libeas-WARNING **:folder_sync response XML is empty
Calendar sync with the same credentials works (well, partially).
$ syncevolution --version
SyncEvolution 1.4.1
using libical.so.1
using libical.so.1
using libbluetooth.so.3
Is there some solution that I can try? Thanks in advance!
P.S. Sorry for my English
6 years
