Maintenance release with various bug fixes.
* syncevo-dbus-server + ConnMan: fixed "online" detection (BMC #21541, BMC #24587)
SyncEvolution did not recognize any cellular connectivity as
suitable for syncing. The strict check for certain "connected
technology" is unnecessary, anything which makes the computer
"online" should be good enough. So now it just uses the ConnMan
Additional benefit: will continue to work with ConnMan 1.0, which
won't have the "ConnectedTechnologies" property anymore.
The Bluetooth available check was also (incorrectly) using the
ConnMan API. Now asssume that OBEX/Bluetooth is always available.
* automatic backups: added INFO messages and fixed dumpData/printChanges (BMC #24619)
Point out that backups are created (user might be unaware otherwise
and wonder about the delay), explain why (so that users know how to
turn it off).
Turning these backups off with dumpData=0 printChanges=0 had to be
fixed, backups were always written previously.
* EDS compatibility: bumped version check for EDS 3.2
SyncEvolution is known to work with EDS 3.2. Therefore use the
libebook/ecal/edataserver libs from 3.2 if available, without
warnings in the --version output. Also happens with inconsistent
distro setups where the old libs are available and would have been
prefered by SyncEvolution 1.2.1 even though the old libs no longer
work with EDS 3.2.
* GTK-UI: do not accept service config without a username (BMC#23106)
Instead of creating such a config, an error dialog is shown.
* GTK-UI: updated translations
* fixed various compile issues, primarily on Fedora Core 17
(unistd.h/ssize_t, invoking syncevolution during compilation,
SyncEvolution is known to not compile with Bluez 4.97. A patch
for Bluez header files is needed to make them work in C++ again,
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. Release 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
Source snapshots are in
i386, lpia and amd64 binaries for Debian-based distributions are
available via the "stable" syncevolution.org repository. Add the
following entry to your /apt/source.list, then install
deb http://downloads.syncevolution.org/apt unstable main
These binaries include the "sync-ui" GTK GUI and were compiled for
Ubuntu 8.04 LTS (Hardy). 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
The same binaries are also available as .tar.gz and .rpm archives in
http://downloads.syncevolution.org/syncevolution/evolution. 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
After installation, follow the
Patrick Ohly, on behalf of everyone who has helped
to make SyncEvolution possible:
On Mi, 2011-12-14 at 15:44 +0100, Chris Kühl wrote:
> >> Ok, I'm looking into this. The original plan was that Step 1 was a
> >> dependency of Step 2 but I've been reconsidering my approach. I'll
> >> look into what you're asking and get back to you soon.
> > I can also do that part myself, if you give me some pointers to
> > technical documentation. I was looking for information on
> > a D-Bus connection over a pair of connected file descriptors,
> > much luck.
> Well, in GIO GDBus you can create a connection using a GIOStream using
> g_dbus_connection_new_sync(). Not sure if that would really work the
> way you want, though.
How about the same thing for libdbus?
> I've no problem doing this, though.
I don't care either way, as long as we can get it done soon, like this
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.
I'm trying to sync several CalDAV calendar to my phone and would like to
reuse the peer/accounts. If I use the general syncURL and use specific
databases, only the initial sync for the calendar is working. But when I
use the path to the database on the server as syncURL and leave the
database-param empty, initial and normal synchronization is working. Am
I missing something in my syncevolution config?
##configuration for default calenar
syncevolution --configure --template webdav
syncURL=https://domain.com/SOGo/dav/%u/ username=foo password=bar
#explicitly configure addressbook source on CardDAV-Server
#explicitly configure calendar source on CalDAV-Server
syncevolution --configure --template SyncEvolution_Client
syncURL=local://@sogopersonal username= password= n900personal@default
#calendar initial sync works
syncevolution --sync slow n900personal calendar
#, but not normal sync after delete of event (path to ics file wrong)
syncevolution n900personal calendar
"DELETE /735.ics HTTP/1.1" 405 378 "-
#addressbook sync does not work
syncevolution --sync slow n900personal addressbook
[INFO @sogopersonal] @sogopersonal/addressbook: starting first time
[ERROR @sogopersonal] @sogopersonal/addressbook: error code from
SyncEvolution object not found (remote, status 404): GET: bad HTTP
status: <status 1.1, code 404, class 4, Not Found>
Thanks for review!
We have some interest in using SyncEvolution to synchronize the
phonebook through Bluetooth, using the PBAP profile (one-way
synchronization). This has already been proposed in
Could somebody tell what the status of this development is?
Just wanted to let you know I got a Nokia N9 to sync succesfully with a
private Funambol 9 server using Ove Kåven's repository.
For reference my notes below (some superfluous but better too much than
Thanks a lot, Patrick, Ove and Justus for writing syncevolution, the N9
port and the message with details.
Install syncevolution on Nokia N9
Backed up contacts and calendar from thunderbird
# Requirements: developer mode
# create and edit syncevolution.list using the nano editor.
# use vi or something if you're smarter than me ;)
# development version of Ove's syncevolution package
deb http://people.debian.org/~ovek/harmattan/ ./
deb-src http://people.debian.org/~ovek/harmattan/ ./
apt-get install syncevolution
exit #back to normal user
syncevolution --help # as normal user
mkcal = KCalExtended = MeeGo Calendar:
Personal (/home/user/.calendar/db) <default>
#show existing templates
syncevolution --template ?
#create config based on myfunambol
syncevolution --configure funambol
#find out which file to edit for settings:
grep -r -i syncurl *
syncURL = http://my.funambol.com/sync
syncurl = http://<hostname private funambol server>/sync
username <my username>
password <my password>
### *** todo: if we get timeouts look at disabling printChanges and
dumpData (based on syncevolution mailing list January 2012)
#don't fill up system with logs:
# maxlogdirs = 10
# don't fill up the system, 5 is ok:
maxlogdirs = 5
#list local items just for info:
syncevolution --print-items funambol addressbook
syncevolution --print-items funambol calendar
#delete existing local calendar (I had some rubbish there)
# of course, don't do this if your phone contacts should overrule your
# did not seem to work with
#syncevolution --delete-items funambol calendar *
# we'll deal with it later
# Delete local phone contacts using phone's Contacts GUI
# First sync:
[INFO] todo: inactive
[INFO] memo: inactive
[INFO] addressbook: starting first time sync, two-way
[INFO] calendar: starting first time sync, two-way
[INFO] addressbook: first time sync done unsuccessfully
[ERROR] addressbook: unexpected slow sync (local, status 22000)
[INFO] calendar: first time sync done unsuccessfully
[ERROR] calendar: unexpected slow sync (local, status 22000)
[ERROR] error code from Synthesis engine local, status 20048
Synchronization failed, see
Changes applied during synchronization:
| | LOCAL | REMOTE | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
| addressbook | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| slow, 0 KB sent by client, 0 KB received |
| unexpected slow sync (local, status 22000) |
| calendar | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| slow, 0 KB sent by client, 0 KB received |
| unexpected slow sync (local, status 22000) |
| start Fri 13 Jan 2012 12:06:13 PM CET, duration 0:07min |
| unexpected slow sync (local, status 22000) |
First ERROR encountered: unexpected slow sync (local, status 22000)
Doing a slow synchronization may lead to duplicated items or
lost data when the server merges items incorrectly. Choosing
a different synchronization mode may be the better alternative.
Restart synchronization of affected source(s) with one of the
following sync modes to recover from this problem:
slow, refresh-from-server, refresh-from-client
Analyzing the current state:
syncevolution --status funambol addressbook calendar
Running with one of the three modes:
syncevolution --sync [slow|refresh-from-server|refresh-from-client]
funambol addressbook calendar
# so, do a forced sync from server (note: I didn't have important stuff
in phone calendar/addressbook)
syncevolution --sync refresh-from-server funambol addressbook calendar
#check log in ~/.cache/syncevolution; seems ok
# check normal sync:
#second sync after modifying calendar, contact remotely: works
#went into funambol admin tool and explicitly set timezone and
conversion for N9 client. Don't know if that is necessary
I am having trouble getting my N9 to sync with my Linux box, probably at
least partially due to my limited understanding of how the N9 is set up
I first tried syncml-ds-tool, which allows me to shuffle data back and
forth via USB/OBEX or Bluetooth/OBEX, but no real record-wise sync.
I then tried opensync over bluetooth, but am having persistent bluetooth
problems (I cannot browes files on the N9 over obexftp using any tool,
for example), so I gave up on this front for now. Any advice would be
I have not tried opensync over USB. Perhaps this would be a promising
route. Any advice would be appreciated.
I tried syncevolution over bluetooth, but persistently got transport
errors (presumably for the same reasons as the opensync troubles), and
gave up for now.
I then installed
on the N9, and set up syncevolution with syncevo-http-server on the
laptop. This produced first success: I can sync contacts and multiple
caledars over an IP connection. However:
- There appears to be no way to sync memos and todos using this setup.
Both are apparently stored inside /home/user/.calendar/db on the N9,
along with the calendar data, but from inspecting the source code of
this Harmattan syncevolution build it appears that these cannot
currently be sync'ed because this has simply not yet been implemented.
- Sync is extremely slow. My 1000+ contacts take more than 10 minutes
to sync, even if there are no changes on either side. (On my Palm
this takes about 1 second, even if there are records to be sync'ed.)
The N9 syncevolution client fully charges the CPU for much of this
- I had trouble getting all of my data onto the N9 because of timeouts
and other issues. I was completely unable to transfer my 13 years
worth of appointments ("D-Bus peer has disconnected" after many
minutes and transferring 212/5955 appointments), and had to resort to
moving the entire past into an unsync'ed calendar on the laptop.
Thus, I am interested in trying out the N9's built-in sync facilities
instead of the custom Harmattan syncevolution client, but I have found
no way to do this:
- Is there a way to use syncevolution on the laptop to initiate a sync
with the N9 using OBEX over USB?
- I have not found a way initiate on the N9 a sync with the laptop
(short of installing Funambol or something, which I'd prefer to
- The latter should work via bluetooth, but I have not found a way to
get my laptop to advertise OPP, so the N9 does not offer the (paired)
laptop as a sync peer. Any hints?
Given this experience, I am puzzled by Fredrik's announcement of success:
On Tue, 2011-10-25 at 12:59 +0200, Frederik Elwert wrote:
> I recently got a Nokia N9, and I am now experimenting with
> SyncEvolution to get my Desktop and the N9 in sync.
> It started fairly promising: I could add the N9 with the Nokia
> template in sync-ui. In general, sync works quite fine. So the N9
> seems to be capable enough by default to get this kind of things
Perhaps I am missing something obvious? Any suggestions are welcome.
Running Debian Wheezy
Synchronising Evolution 3.2.2 with Memotoo.
Using Sycevolution from Wheezy - 126.96.36.199a
Worked fine until last upgrade from Wheezy.
Now I get this screen:
Syncevolution status.ini reads
status = 10500
error = (syncevo-dbus-server:11779): libecal-WARNING **: Cannot get cal
from factory: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The
name org.gnome.evolution.dataserver.Calendar0 was not provided by
any .service files
start = 1325406304, 2012-01-01 16:25:04 +0800
end = 1325406304, 2012-01-01 16:25:04 +0800
source-addressbook-mode = disabled
source-addressbook-first = false
source-addressbook-resume = false
source-addressbook-status = 0
source-addressbook-backup-before = -1
source-addressbook-backup-after = -1
source-calendar-mode = disabled
source-calendar-first = false
source-calendar-resume = false
source-calendar-status = 0
source-calendar-backup-before = -1
source-calendar-backup-after = -1
source-memo-mode = disabled
source-memo-first = false
source-memo-resume = false
source-memo-status = 0
source-memo-backup-before = -1
source-memo-backup-after = -1
source-todo-mode = disabled
source-todo-first = false
source-todo-resume = false
source-todo-status = 0
source-todo-backup-before = -1
source-todo-backup-after = -1
And the log file is attached.
I have gone into the peers/memotoo/source files to set it to synchronise
it two way...
Still no reaction....
Any ideas where I should be hunting around? I have purged off
syncevolution and reinstalled - same problem.
I've started to setup syncevolution on my Notebook. My goal is to
sync. my Samsung-Android to Evolution via Bluetooth oder LAN.
First I paired my Phone with my Notebook. To put this option to the
test I tried to send an Picture in bouth directions. To get this
working I needed to install and setup gnome-user-share.
Does syncevolution also depent on this Package?
I'm tring to run it on Ubuntu 10.10 and on LinuxMint-DebianEdition.
Currently I'm using version 188.8.131.52 from the archives.