[SyncEvolution] SyncEvolution 1.1 pre-release
by Patrick Ohly
Hello!
I've made binaries of the current SyncEvolution development snapshot
available. You can get them from the "experimental" apt repository
(.deb) and http://downloads.syncevolution.org/syncevolution/evolution/
(.rpm).
Instead of the previous "alpha" or "beta" denominators as part of the
version name, I've switched to the rpm method of "next version minus 1
in the last position". So this snapshot is version 1.0.99.6 (> 1.0.x for
any kind of realistic x, < 1.1). The .6 stems from the fact that there
have been earlier snapshots in MeeGo.
This release should be pretty stable, but is not yet quite feature
complete for 1.1.
Full NEWS file below. If possible, I'd like to get feedback from
nudelzebra(a)web.de on issue 4026 and from Frederik on the implementation
of the various D-Bus API improvements.
* Nokia phones: avoid data loss in two-way sync due to X-EVOLUTION-UI-SLOT (MBC #2566)
* Nokia phones: alarm times in UTC, sending PHOTO (BMC #1657, #5860)
* included all phone templates submitted to syncevolution.org Wiki (BMC #5727)
* syncevo-phone-config: set consumerReady in output, more useful for Wiki (BMC #3803)
* workaround for D-Bus timeouts in EDS libecal/libebook (MBC #4026)
* sync-ui (GTK version): app is now listed as "SyncEvolution (GTK)" under "Office"
* added generic command line options for importing, exporting, updating, listing
and deleting items in the different backends (http://syncevolution.org/blogs/pohly/2010/manipulate-evolution-kcalextend...)
* added backends for mKCal and QtContacts (MeeGo PIM storage),
meant to be used for manipulating this data on the command line
* enhanced D-Bus interface (BMC #3558, #3559, #3560, #3562, #3563)
* the command line tool now warns when running against a different D-Bus daemon (BMC #3563)
* creating and configuring sources in a context (without peer-specific
properties) is now supported
* improved documentation: README.rst, man page, and --help output
* fixed some compile issues (MBC #6367), improved nightly testing
--
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.
10 years, 1 month
[SyncEvolution] [Fwd: HTTP server demo not yet running]
by richard
Hallo ,
I am trying to configure my local HHTP server for my notebook and
desktop. However I did not yet reach first sync. What shall I do better
to test it on my Desktop machine?
1)Do I need to setup server configuration and client configuration.
2)How to setup /simulate two clients?
3)What are source directories of clients?
Thank you a lot
darkanry
10 years, 2 months
[SyncEvolution] SonyEricsson Elm
by Ansgar Machalický
Hello everybody!
I'm trying to sync my SonyEricsson Elm with Evolution and therefore
would love to find a working configuration first.
After updating the phone's firmware I used syncevo-phone-config but it's
painfully slow:
The first 54 configs need roughly 2 seconds each for testing; the phone
says "synchronizing" for a blink, then beeps (like "no success") and
does the next test.
With test 55/1188 it seems to actually work. The following message is
printed on the display: "Synchronizing, sending contacts" and afterwards
the phone beeps like "success".
But from that point on, on the phone nothing happens. The script seems
to freeze, but goes on awefully slowly: It takes about 5 minutes to test
each configuration, i.e. to print the line "Start 56/1188 test" and so
on.
5000 minutes are 3.5 days - can anyone think of a workaround, or will I
have to leave my phone next to my laptop for half a week....? :-(
Where should the successfully (?) tested configuration go? I can't find
any file with the name I specified on the command line yet, probably
because the script hasn't finished but was interrupted by pressing
CTRL-C.
Regards,
Ansgar
10 years, 2 months
[SyncEvolution] Error 500 and 406 when syncing with Nokia E50
by Simon Siemens
Hi,
I can successfully synchronise my address book with my mobile phone.
When I synchronise my calendar+todo, I get – after quite some time – the
error 500 and 406. I appended a snippet of the log file. The messages
with a non-OK status are at the end. What is the best way of debugging
this? Can I find out what element makes problems? (Maybe I can simply
delete it.)
Thank you very much for your help,
Simon
[2010-09-23 18:13:48.026] 'SyncML_Outgoing' - preparing for response before starting to analyze new incoming message [--][++] [->end]
□ +
–
[2010-09-23 18:13:48.026] 'SyncML_Incoming' - Starting to analyze incoming message, RequestNo=0, SySyncVers=3.4.0.8 [--][++] [->end] [->enclosing]
☆ [2010-09-23 18:13:48.026] =================> Starting to analyze incoming message, SySync V3.4.0.8, RequestNo=0
☆ [2010-09-23 18:13:48.026] Created command 'SyncHdr' (incoming)
☆ +
–
[2010-09-23 18:13:48.026] 'processHdr' - Processing incoming SyncHdr [--][++] [->end] [->enclosing]
○ +
–
[2010-09-23 18:13:48.026] 'SyncHdr' - Processing incoming SyncHdr, IncomingMsgID=6 [--][++] [->end] [->enclosing]
■ [2010-09-23 18:13:48.027] Started Processing of message #6 (SyncML/1.1)
■ [2010-09-23 18:13:48.027] MaxMsgSize for outgoing msgs set to 65535
■ [2010-09-23 18:13:48.027] Created command 'Status' (outgoing)
■ [2010-09-23 18:13:48.027] Authorization ok from previous request: 200
■ [2010-09-23 18:13:48.027] Created command 'SyncHdr' (outgoing)
■ [2010-09-23 18:13:48.027] Target (Remote URI) = 'IMEI:351893012204114'
■ +
–
[2010-09-23 18:13:48.027] 'SyncHdr' - SyncHdr generation, SyncMLVers=1.1, OutgoingMsgID=6 [--][++] [->end] [->enclosing]
★ [2010-09-23 18:13:48.027] SyncHdr: issued in MsgID=6, now queueing for status
★ [2010-09-23 18:13:48.027] Outgoing Message size is now 107 bytes
–[2010-09-23 18:13:48.028] End of 'SyncHdr' [->top] [->enclosing]
■ +
–
[2010-09-23 18:13:48.028] 'issue' - issuing command, Cmd=Status [--][++] [->end] [->enclosing]
★ [2010-09-23 18:13:48.028] Status Code 200 issued for Cmd=SyncHdr, (incoming MsgID=6, CmdID=0)
★ [2010-09-23 18:13:48.028] - TargetRef (localID) = 'PC Suite'
★ [2010-09-23 18:13:48.028] - SourceRef (remoteID) = 'IMEI:351893012204114'
★ [2010-09-23 18:13:48.028] Status: issued as (outgoing MsgID=6, CmdID=1), not waiting for status
★ [2010-09-23 18:13:48.028] Deleted command 'Status' (outgoing MsgID=6, CmdID=1)
★ [2010-09-23 18:13:48.028] Outgoing Message size is now 178 bytes
–[2010-09-23 18:13:48.028] End of 'issue' [->top] [->enclosing]
■ [2010-09-23 18:13:48.029] Incoming SyncHdr processed, incomingMsgID=6, SyncMLVers=1.1
■ [2010-09-23 18:13:48.029] - Session ID='1'
■ [2010-09-23 18:13:48.029] - Source (Remote party): URI='IMEI:351893012204114' DisplayName=''
■ [2010-09-23 18:13:48.029] - Response to be sent to URI='[none specified, back to source]'
■ [2010-09-23 18:13:48.029] - Target (Local party) : URI='PC Suite' DisplayName=''
■ [2010-09-23 18:13:48.029] Deleted command 'SyncHdr' (incoming MsgID=6, CmdID=0)
–[2010-09-23 18:13:48.029] End of 'SyncHdr' [->top] [->enclosing]
–[2010-09-23 18:13:48.029] End of 'processHdr' [->top] [->enclosing]
☆ [2010-09-23 18:13:48.029] Created command 'Status' (incoming)
☆ +
–
[2010-09-23 18:13:48.029] 'processStatus' - Processing incoming Status [--][++] [->end] [->enclosing]
○ [2010-09-23 18:13:48.030] Started processing Command 'Status' (incoming MsgID=6, CmdID=1)
○ [2010-09-23 18:13:48.030] RECEIVED STATUS 200 for for command 'SyncHdr' (outgoing MsgID=5, CmdID=0)
○ [2010-09-23 18:13:48.030] - TargetRef (remoteID) = 'IMEI:351893012204114'
○ [2010-09-23 18:13:48.030] - SourceRef (localID) = 'PC Suite'
○ [2010-09-23 18:13:48.030] Found matching command 'SyncHdr' for Status
○ [2010-09-23 18:13:48.030] Status: 200: successful --> accept as ok
○ [2010-09-23 18:13:48.030] Deleted command 'SyncHdr' (outgoing MsgID=5, CmdID=0)
○ [2010-09-23 18:13:48.030] Deleted command 'Status' (incoming MsgID=6, CmdID=1)
–[2010-09-23 18:13:48.030] End of 'processStatus' [->top] [->enclosing]
☆ [2010-09-23 18:13:48.031] Created command 'Status' (incoming)
☆ +
–
[2010-09-23 18:13:48.031] 'processStatus' - Processing incoming Status [--][++] [->end] [->enclosing]
○ [2010-09-23 18:13:48.031] Started processing Command 'Status' (incoming MsgID=6, CmdID=2)
○ [2010-09-23 18:13:48.031] RECEIVED STATUS 200 for for command 'Sync' (outgoing MsgID=5, CmdID=176)
○ [2010-09-23 18:13:48.031] - TargetRef (remoteID) = './C:Calendar'
○ [2010-09-23 18:13:48.031] - SourceRef (localID) = './Calendar'
○ [2010-09-23 18:13:48.031] Found matching command 'Sync' for Status
○ [2010-09-23 18:13:48.031] Status: 200: successful --> accept as ok
○ [2010-09-23 18:13:48.031] Deleted command 'Sync' (outgoing MsgID=5, CmdID=176)
○ [2010-09-23 18:13:48.032] Deleted command 'Status' (incoming MsgID=6, CmdID=2)
–[2010-09-23 18:13:48.032] End of 'processStatus' [->top] [->enclosing]
☆ [2010-09-23 18:13:48.032] Created command 'Status' (incoming)
☆ +
–
[2010-09-23 18:13:48.032] 'processStatus' - Processing incoming Status [--][++] [->end] [->enclosing]
○ [2010-09-23 18:13:48.032] Started processing Command 'Status' (incoming MsgID=6, CmdID=3)
○ [2010-09-23 18:13:48.032] WARNING: RECEIVED NON-OK STATUS 500 for command 'Replace' (outgoing MsgID=5, CmdID=177)
○ [2010-09-23 18:13:48.032] - TargetRef (remoteID) = '922'
○ [2010-09-23 18:13:48.032] Found matching command 'Replace' for Status
○ [2010-09-23 18:13:48.032] Status: General error 500 (original op was replace) -> marking item for resend in next session
○ [2010-09-23 18:13:48.033] Deleted command 'Replace' (outgoing MsgID=5, CmdID=177)
○ [2010-09-23 18:13:48.033] Deleted command 'Status' (incoming MsgID=6, CmdID=3)
–[2010-09-23 18:13:48.033] End of 'processStatus' [->top] [->enclosing]
☆ [2010-09-23 18:13:48.033] Created command 'Status' (incoming)
☆ +
–
[2010-09-23 18:13:48.033] 'processStatus' - Processing incoming Status [--][++] [->end] [->enclosing]
○ [2010-09-23 18:13:48.033] Started processing Command 'Status' (incoming MsgID=6, CmdID=4)
○ [2010-09-23 18:13:48.033] WARNING: RECEIVED NON-OK STATUS 406 for command 'Replace' (outgoing MsgID=5, CmdID=178)
○ [2010-09-23 18:13:48.033] - TargetRef (remoteID) = '935'
○ [2010-09-23 18:13:48.033] Found matching command 'Replace' for Status
○ [2010-09-23 18:13:48.034] Status: 406: originator exception
○ +
–
[2010-09-23 18:13:48.034] 'SessionAbort' - Aborting Session, Status=406, ProblemSource=REMOTE [--][++] [->end] [->enclosing]
■ [2010-09-23 18:13:48.034] WARNING: Aborting Session with Reason Status 406 (REMOTE problem) ***
■ [2010-09-23 18:13:48.034] --------------- Ignoring all commands in this message (after 0 sec. request processing, 70 sec. total) with Status 514 (0=none) from here on
10 years, 2 months
[SyncEvolution] nokia 2700
by luciopineda
Hi,
I want to use syncevolution but I've the following problem
At each synchronization for the calendar the same content
grow of 1
for example if I'd marked for the 1st of October 2010 at 15,00 Dentist
and sync I'll have in Evolution end in the mobile.
At the following sync I will have two
of 1st of October 2010 at 15,00 Dentist
at following sync 3 of 1st of October 2010 at 15,00 Dentist
Is that clear ?
Do you have any tips ?
Does any body have the same problem ?
Thank you
10 years, 2 months
Re: [SyncEvolution] N900+funambol+zimbra todo and calendar
by Aaron Krebs
On Sun, Sep 12, 2010 at 7:20 AM, Patrick Ohly <patrick.ohly(a)intel.com> wrote:
<snip>
> Try
> type = todo:text/x-vcalendar!
> type = calendar:text/x-vcalendar!
>
> That will tell the server that vCalendar 1.0. If that doesn't help, then
> you'll have to ask the Zimbra guys for help regarding that error message
> above.
>
>> Anyone have zimbra and an N900 syncing?
>
> Don't know.
>
> --
> 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.
>
>
>
Thanks Patrick!
Setting
type = calendar:text/x-vcalendar!
works for calendar. (On a side note, what's the significance of the
exclamation mark? The comments in config.ini don't include this in the
available types, which is why I didn't try it.)
Tasks sync is not working yet, but that's a problem with the Funambol
Zimbra Connector. I'll explain here for the benefit of anyone looking
for this in the future.
Zimbra by default sets task status to "not started" which Funambol
can't translate into vCal format. Changing the status to "In Progress"
on the Zimbra web interface gets rid of that error. However, Funambol
then chokes on populating the task with data from the server, giving
com.funambol.framework.core.Sync4jException: Error retriving data of
the item with key: { keyValue: 3718 }
My java isn't good enough right now to trace through the source code
to see why it's not working. If I have time at a later date I may work
in it, but for now I can live without tasks sync.
Thanks for the help Patrick
Aaron Krebs
10 years, 2 months
[SyncEvolution] N900+funambol+zimbra todo and calendar
by Aaron Krebs
Hello
I'm having some problems getting syncevolution on the Nokia N900 to sync
with my funambol server and Zimbra. Contacts work fine, but tasks and
calendar don't sync down from the server (but from phone to server is
OK). I'm getting the following error:
[event] Status:'UNSUPPORTED MEDIA TYPE' for a 'Add' for this items
on funambol, while syncevolution reports a successful sync.
The more I look in to this, the more I think my syncevolution
configuration may not in fact be the problem, but the only real hints
I've been able to dig up point at the 'type =' parameter in config.ini
here:
http://forums.internettablettalk.com/showthread.php?p=546066#post546066
type is currently set to type = todo:text/calendar! for tasks (as per
the configuration template) and type = calendar:text/calendar! for
calendar events. I've tried the other maemo backends with various levels
of success (all error out on the funambol side).
Anyone have any further tips where I could look? Anyone have zimbra and
an N900 syncing?
Thanks,
Aaron Krebs
10 years, 2 months
[SyncEvolution] More recent version for Maemo/N900?
by Nils Faerber
Hello!
Is anyone working on a more recent version for Maemo-N900?
The last version in the extra repo is pretty old by now:
SyncEvolution 0.9.2
Loading backend library /usr/lib/syncevolution/backends/syncmaemocal.so
Loading backend library /usr/lib/syncevolution/backends/syncsqlite.so
Loading backend library /usr/lib/syncevolution/backends/syncebook.so
Loading backend library /usr/lib/syncevolution/backends/syncecal.so
Loading backend library /usr/lib/syncevolution/backends/syncfile.so
Loading backend library /usr/lib/syncevolution/backends/syncxmlrpc.so
Loading backend library /usr/lib/syncevolution/backends/syncaddressbook.so
If no one is working on it I would give it a try - but if I do not have
to, well, I would appreciate it ;)
Cheers
nils
--
kernel concepts GbR Tel: +49-271-771091-12
Sieghuetter Hauptweg 48
D-57072 Siegen Mob: +49-176-21024535
http://www.kernelconcepts.de
10 years, 2 months
[SyncEvolution] "Comment" in sync.desktop
by Pietro Battiston
Hello,
the files
src/gtk-ui/sync.desktop.in
src/gtk-ui/sync-gtk.desktop.in
contain as comment "Up to date".
I fear this is not particularly appropriate...
Moreover, I would ensure that the words "Syncevolution", or at least
"Evolution", appear in "Name" or "Comment", since currently if one has a
crowded applications menu it can be non-trivial to find it.
(by the way: under every other aspect, syncevolution is now really
great)
cheers
Pietro Battiston
10 years, 2 months
