Hi Patrick,
I do not seem to be able to turn off the exhaustive dumps. I did:
/home/user $ syncevolution --configure printChanges=false client-for-laptop
/home/user $ syncevolution --configure dumpData=false client-for-laptop
which caused
printChanges = 0
dumpData = 0
to appear in
/home/user/.config/syncevolution/default/peers/client-for-laptop/config.ini.
However, the dumps still appear. Here is a related excerpt from the N9
client log (followed by some scary stuff that is probably not directly
related but may contribute to the slow dump):
[2012-01-06 18:03:18.778] addressbook: starting normal sync, two-way
[2012-01-06 18:03:18.780] =================> Finished processing incoming
message #1 (final), request=0
[2012-01-06 18:03:18.781] MessageEnded finishes : new outgoing state='sync',
new incoming state='sync', NeedToAnswer
[2012-01-06 18:03:18.782] Local Datastore 'addressbook':
State=sync_mode_stable, normal sync, two-way
[2012-01-06 18:03:18.783] Local Datastore 'addressbook' - Types: tx to remote:
'vCard21': text/x-vcard (2.1), rx from remote: 'vCard30': text/vcard (3.0)
–
[2012-01-06 18:03:18.784] 'DSStateChange' - Datastore changes state,
datastore=addressbook, oldstate=sync_mode_stable, newstate=data_access_started
[--][++] [->end] [->enclosing]
[2012-01-06 18:03:18.785] TStdLogicDS::startDataAccessForClient
[2012-01-06 18:03:18.785] Executing Script 'datastoreinitscript'
–
[2012-01-06 18:03:18.786] 'ReadSyncSet' - Reading Sync Set from Database,
datastore=addressbook [--][++] [->end] [->enclosing]
[2012-01-06 18:03:18.787] 'addressbook' dev='anydevice'
usr='singleuser' err=0
[2012-01-06 18:03:18.788] FilterSupport staticfilter:
dynamicfilter:
invisiblefilter:
[2012-01-06 18:03:18.789] Executing Script 'initscript'
[2012-01-06 18:03:18.790] Now reading local sync set: report changes
since reference1 at 2012-01-06 16:43:34.517, and since reference2 at 2012-01-06
16:43:34.517
[2012-01-06 18:03:18.807] creating
/home/user/.cache/syncevolution/client_+for_+laptop-2012-01-06-18-03/addressbook.before
[2012-01-06 18:08:00.843] libqtcontacts-tracker: engine.cpp:1873:
=============================================================================
WARNING /!\ - NEVER EVER CALL THIS FUNCTION FROM PRODUCTION CODE!!!
=============================================================================
QContactAbstractRequest::waitForFinished(), respectively
QContactManagerEngine::waitForRequestFinished() must spin your
application's event loop. Doing so will cause HAVOC AND PAIN for
any non-trivial program.
So please refactor your asynchronious code, or use the synchronious
API if blocking your application is acceptable.
WE MEAN IT!!!
Offending application is /usr/bin/syncevolution [9256].
=============================================================================
[repeated many times]
...
[2012-01-06 18:08:00.926]
/home/user/.cache/syncevolution/client_+for_+laptop-2012-01-06-18-03/addressbook.before
created
[2012-01-06 18:08:00.933] using full item scan to detect changes
[2012-01-06 18:08:01.519] StartDataRead last='1' resume='1' res=0
[2012-01-06 18:08:01.520] ReadNextItemAsKey aStatus=2 aID=(138216,(null)) res=0
[2012-01-06 18:08:01.520] ReadNextItemAsKey aStatus=2 aID=(138222,(null)) res=0
[repeated many times]
Another question: Instead of sync'ing over USB with syncevo-http-server
on the laptop, can I sync over Bluetooth? I have not found an obvious
way to do this:
- Trying to configure syncevolution as an OBEX server results in
"[ERROR] unsupported transport type is specified in the
configuration".
- I found some vague pointers towards hooking up syncevolution with
obexd (the one commonly packaged as obexd-server, I gather) but it
conflicts with bluedevil (I use KDE) and other packages.
And a final, unrelated question: running KDE, it would be more natural
for me to use KOrganizer instead of Evolution. The logs say "Loading
backend library syncakonadi.so." I have not found conclusive
information about this backend. Is this a production-ready backend that
would allow me to sync with KOrganizer?
Many thanks,
Justus
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
