[SyncEvolution] Fuambol Login denied
by Christof Gaenzler
Hi,
I cannot login to a Funambol server, I get an "Authentication failed" -
the server works well for my mobile phone:
Funambol Data Synchronization Server v.8.2.1
Man=Funambol
Mod=DS Server CarEd
SwV=8.2.1
HwV=-
FwV=-
OEM=-
DevID=funambol
DevTyp=server
VerDTD=1.2
UTC=true
SupportLargeObjs=true
SupportNumberOfChanges=true
Ext=X-funambol-smartslow
I am using syncevolution 1.0.1 from the repo under Ubuntu 10.10
The log file tells me:
Synthesis SyncML Engine 3.4.0.8
client: SyncEvolution 1.0.1 for workstation
PLATFORM:Linux
DLL:true
MINVERSION:V1.0.6.0
MANUFACTURER:SyncEvolution
DESCRIPTION:SyncEvolution Synthesis DB Plugin
plugin_datastore_str:no
plugin_datastore_key:yes
ITEM_AS_KEY:yes
plugin_datablob:no
...
# [2010-10-15 15:46:15.671] =================> Starting new client
session
#
+
–
[2010-10-15 15:46:15.671] 'SyncML_Outgoing' - start of new outgoing
message [--][++] [->end]
* [2010-10-15 15:46:15.671] =================> Started new outgoing
message
* [2010-10-15 15:46:15.671] Created command 'SyncHdr' (outgoing)
* [2010-10-15 15:46:15.671] Target (Remote URI) = 'https://***/sync'
* [2010-10-15 15:46:15.671] Authenticating with server as user '***'
* [2010-10-15 15:46:15.671] - using nonce '***'
*
+
–
[2010-10-15 15:46:15.671] 'SyncHdr' - SyncHdr generation,
SyncMLVers=1.2, OutgoingMsgID=1 [--][++] [->end] [->enclosing]
o [2010-10-15 15:46:15.672] SyncHdr: issued in MsgID=1, now
queueing for status
o [2010-10-15 15:46:15.672] Outgoing Message size is now 243
bytes
...
[2010-10-15 15:46:17.711] 'processStatus' - Processing incoming Status
[--][++] [->end] [->enclosing]
* [2010-10-15 15:46:17.711] Started processing Command
'Status' (incoming MsgID=1, CmdID=1)
* [2010-10-15 15:46:17.711] WARNING: RECEIVED NON-OK STATUS 401 for
command 'SyncHdr' (outgoing MsgID=1, CmdID=0)
* [2010-10-15 15:46:17.711] - TargetRef (remoteID) =
'https://***/sync'
* [2010-10-15 15:46:17.711] - SourceRef (localID) =
'syncevolution-****'
* [2010-10-15 15:46:17.711] Found matching command 'SyncHdr' for
Status
* [2010-10-15 15:46:17.711] Remote requests auth
type='syncml:auth-md5'
* [2010-10-15 15:46:17.711] Next Cred will have type='md5' and
format='base64' and use nonce='***'
* [2010-10-15 15:46:17.711] Authentication failed (status=401) with
remote server
What's going wrong here?
any help appreciated!
Christof
--
10 years, 3 months
[SyncEvolution] Synchronising Nokia E71 with Evolution - various minor issues and questions
by Chris G
I have just installed the 1.0.99.7 release candidate to see if it has
cleared up issues I had with earlier versions (I think I tried 1.0 when
it first appeared).
I'm running it on an xubuntu 10.04 system with a Nokia E71.
It looks pretty good so far, definitely usable, but I have a couple of
issues/questions:-
When I first installed it just offered me 'Nokia', this was before
I'd even turned my E71 on, was it picking up a previous profile? If
so would it be worth deleting the profile and starting 'clean'?
The contacts/addresses synchronisation gets the first name/family
name configuration on the Nokia wrong. Entries in Evolution like
"Chris Green" are sorted by the family name 'Green' but the entries
in the Nokia are sorted under first name 'Chris', is there any way
to get this to work properly?
--
Chris Green
10 years, 3 months
Re: [SyncEvolution] [os-libsynthesis] Syncing Nokia 6303 using Syncevolution
by Patrick Ohly
On Thu, 2010-09-09 at 19:31 +0100, Dave Jury wrote:
> I am trying to sync a Nokia 6303 using the Syncevolution GUI, but when
> I click the Select Sync Service button and scroll down to Direct Sync
> I cannot see my device listed.
>
> I have paired my phone using bluetooth, and when I open a terminal and
> type:
> $ sdptool browse 5C:57:C8:0D:FB:53 (being the correct MAC address),
> I get:
>
> Service Name: SyncML Client
> Service RecHandle: 0x10009
> Service Class ID List:
> UUID 128: 00000002-0000-1000-8000-0002ee000002
> Protocol Descriptor List:
> "L2CAP" (0x0100)
> "RFCOMM" (0x0003)
> Channel: 11
> "OBEX" (0x0008)
> Language Base Attr List:
> code_ISO639: 0x656e
> encoding: 0x6a
> base_offset: 0x100
>
> On this basis I can only assume that it's paired correctly and that it
> is advertising the SyncML service over bluetooth, so I could really do
> with your expertise as to why I can't see it in Syncevolution.
Which desktop are you running? Does the "bluetooth-properties" tool
(invoke from command line or via Bluetooth applet) list your phone as
paired?
I'm not entirely sure, but I could imagine that sdptool works even if
not paired.
--
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, 3 months
[SyncEvolution] Suspect "PRODID:-//Synthesis AG//NONSGML SyncML Engine V3.4.0.6//EN" messing sync with BT car audio
by Oscar A. Valdez
I have succesfully synced my Evolution contacts to a Nokia E63.
Now, when I try to re-sync the E63's contacts over to a Pioneer
DEH-P7100BT car audio, I can't. Unfortunately, neither the phone nor the
car audio provide helpful logs.
Looking into Evolution's addressbook (a Berkeley DB), I notice every
contact has a line with the following:
PRODID:-//Synthesis AG//NONSGML SyncML Engine V3.4.0.6//EN
Everything else looks OK. Could this line (inserted by Syncevolution) be
messing up the syncs with the BT car audio? Can it be safely removed?
---
Oscar A. Valdez
10 years, 3 months
[SyncEvolution] Suspect "PRODID:-//Synthesis AG//NONSGML SyncML Engine V3.4.0.6//EN" messing sync with BT car audio
by Oscar A. Valdez
I have succesfully synced my Evolution contacts to a Nokia E63.
Now, when I try to re-sync the E63's contacts over to a Pioneer
DEH-P7100BT car audio, I can't. Unfortunately, neither the phone nor the
car audio provide helpful logs.
Looking into Evolution's addressbook (a Berkeley DB), I notice every
contact has a line with the following:
PRODID:-//Synthesis AG//NONSGML SyncML Engine V3.4.0.6//EN
Everything else looks OK. Could this line (inserted by Syncevolution) be
messing up the syncs with the BT car audio? Can it be safely removed?
---
Oscar A. Valdez
10 years, 3 months
[SyncEvolution] Syncing SonyEricsson T700 over bluetooth
by Karl Richter-Trummer
Hi there,
Syncevolution seems to be a nice tool, together with genesis, but i
couldnt make it work for my mobilephone yet!
I have installed the 1.0.99 beta from the unstable apt-repository for
ubuntu 10.04, there i selected the sonyericsson profile, this didnt work,
so i tried the older 1.1 profile too. This is from the error.html file:
# [2010-10-03 17:40:26.185] Connecting Bluetooth device with address
00:23:F1:C9:7E:9D and channel 10
# [2010-10-03 17:40:26.429] connect failed with error code 111
# [2010-10-03 17:40:26.430] ObexTransport: Transport Exception in
sdp_callback_impl
# [2010-10-03 17:40:26.430] ObexTransport: connect request failed with
error
# [2010-10-03 17:40:26.431] TransportException thrown at
/work/runtests/head/syncevolution/src/syncevo/ObexTransportAgent.cpp:376
# [2010-10-03 17:40:26.432] ObexTransprotAgent: Underlying transport error
Bluetooth is working, i regularly use this phone as a remote-control over
bt, and on the phone, i see it gets connected when syncevolution is trying
to sync.
Thanks for your help, i hope this it the appropriate mailing-list. I
attached the whole error log.
10 years, 3 months
[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, 3 months
[SyncEvolution] SyncEvolution status update + 1.0.99.7 available
by Patrick Ohly
Hello!
SyncEvolution 1.0.99.7, the release candidate for 1.1, is available for
testing. Company supported development shifts towards other areas like
local synchronization [1] and non-SyncML protocols, so now would be a
good time for contributors to step in and help improve the SyncML part
or work on non-SyncML protocols.
For those not familiar with the project, SyncEvolution synchronizes
personal information management (PIM) data like contacts, calenders,
tasks, and memos using the SyncML information synchronization standard.
Up to and including 0.9.2, a third-party SyncML server was required. In
1.0, SyncEvolution itself is able to act as a SyncML server, both via
HTTP and Bluetooth (direct sync with phones).
SyncEvolution partly spare time project again
=============================================
Before talking about the next release(s), first a word from our
sponsors... ;-) Although Intel continues to support the development and
is still interested in some things that it has to offer, some part of
the work now has to be done in spare time activities again.
After Moblin and Maemo merged into MeeGo, Nokia made the code they had
developed for the upcoming Maemo Harmattan release available as open
source (Buteo, see http://wiki.meego.com/Buteo). For various, mostly
non-technical reasons, this Buteo framework was chosen for MeeGo. This
was announced by Sunil Saxena at OSCON
(http://meego.com/community/events/presentations/meego-technical-overview-...). More information about Buteo and a technical comparison with SyncEvolution can be found in my LinuxCon 2010 talk (http://meego.com/community/events/presentations/data-synchronization-in-n...).
MeeGo Netbook continues to use Evolution and SyncEvolution, but this is
considered legacy code which needs to be replaced at some point.
Therefore everything related to the GTK sync-ui and SyncML is in
maintenance mode.
On the other hand, thanks to the generous contributions by Intel and
Synthesis, the existing code already supports local synchronization with
phones and arguably is in a very usable state. It is up to the open
source community to make use of this functionality. There isn't that
much left to do: continue testing with additional phones, some
workarounds for known issues with peers, etc.
If you are a developer who was holding back because everything seemed to
move forward automatically anyway, now is a good time to become active.
The issue tracker contains more than enough ideas for features and
improvements which currently don't have an owner:
http://bugs.meego.com/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&b...
KDE + Akonadi
=============
Most relevant for those users who didn't want to use Evolution is
certainly the progress made in the Google Summer of Code project by
Dinesh Said (student) and Sascha Peilicke (mentor). I reviewed the first
set of patches and look forward to merging them:
http://meego.gitorious.org/~saidinesh5/meego-middleware/saidinesh5-syncev...
SyncEvolution 1.1
=================
SyncEvolution 1.0.1 was strictly a bug fix release. For 1.1, the goal is
to include some features that may be relevant for KDE and Genesis (D-Bus
interface improvements) and address as much of the issues reported by
users for direct synchronization with some phones.
1.1 also happens to add backends for QtContacts and KCalExtended (now
called mkcal). These are the core PIM storage engines in MeeGo. The goal
is not to synchronize them (that's what Buteo is for), but rather offer
a command line tool for manipulating PIM data automatically. New
command line options (--import/export/print-items/delete-items) were
added for that. They also work with most other backends, in particular
Evolution and the Maemo 5 calendar.
Prerelease 1.0.99.7 is available for testing. It is considered a release
candidate for 1.1. The rpm-style x.99.y numbering scheme replaces the
"beta" and "alpha" parts in older version numbers. 1.0.99.7 can be
downloaded from
http://downloads.syncevolution.org/syncevolution/evolution/ as .rpm
or .tar.gz and installed as .deb from the unstable repository (see
http://syncevolution.org/documentation/installation).
Details:
* bug fix in sync-ui: wrong direction of one-way data transfers with devices (BMC #7091)
* sync-ui (GTK version): app is now listed as "SyncEvolution (GTK)" under "Office"
* 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)
* 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, #7761, #7766)
* 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
SyncEvolution after 1.1
=======================
Local synchronization between two SyncEvolution backends [1] is already
available on a branch. It'll allow synchronization with peers which do
not support SyncML. My pet project will be to add support for the AVM
FritzBox's address book.
Others have expressed an interest in adding CalDAV and Exchange Web
Service support. The future improvements in core SyncEvolution are meant
to make that possible.
[1] http://bugs.meego.com/show_bug.cgi?id=712
--
Bye, Patrick Ohly
--
Patrick.Ohly(a)gmx.de
http://www.estamos.de/
10 years, 3 months
