8:51 p.m.
http://bugzilla.moblin.org/show_bug.cgi?id=10121
Summary: Triggered on client side, "Direct syncevolution via
OBEX" will fail
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Netbook
OS/Version: Moblin Linux
Status: NEW
Severity: major
Priority: Undecided
Component: SyncEvolution
AssignedTo: congwu.chen(a)intel.com
ReportedBy: jingke.zhang(a)intel.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution(a)lists.intel.com
syncevolution: 0.9.99.11
openobex: 1.5-4.1
Description:
====================
This bug is following bug#9902 . Syncevolution via OBEX between two netbooks
can pass, triggered on server side. But triggering syncevolution command client
side will meet error.
Steps:
====================
1. Get two netbook paired.
2. On server side, make config1 for client with SyncEvolutionClient template.
3. On client side, make config2 for server with SyncEvolution template.
4. To avoid slow-sync affect, set preventSlowSync=0 on both sides.
5. Trigger on Server, PASS. 'syncevolution --run -s two-way config1
addressbook'
6. Trigger on Client, FAIL. 'syncevolution --run -s two-way config2
addressbook'
Expectation:
====================
Syncevolution process should pass, triggered by both client and server sides.
Root Cause:
====================
Tracked in comments.
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
8:57 p.m.
New subject: [Bug 10121] Triggered on client side, "Direct syncevolution via OBEX" will fail
http://bugzilla.moblin.org/show_bug.cgi?id=10121
--- Comment #1 from ZhangJingke <jingke.zhang(a)intel.com> 2010-03-09 01:57:18 PST
---
Use this issue to track client sync. When meeting new error, I will file new
issue.
I got some error information.
On client side, syncevolution command line error:
=========
[ERROR] connect failed with error code 111
[ERROR] ObexTransport: Transport Exception in sdp_callback_impl
[ERROR] ObexTransport: connect request failed with error
[ERROR] ObexTransprotAgent: Underlying transport error
On server side, obexd error:
===========
obexd[889]: New connection from: 00:0A:94:03:ED:8B, channel 16
obexd[889]: FindAdapter(00:22:43:DF:6F:B3)
obexd[889]: FindAdapter -> /org/bluez/699/hci0
obexd[889]: RequestAuthorization(00:0A:94:03:ED:8B, 10000)
obexd[889]: RequestAuthorization error: org.bluez.Error.NotAuthorized, Not
Authorized
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
8:57 p.m.
New subject: [Bug 10121] Triggered on client side, "Direct syncevolution via OBEX" will fail
http://bugzilla.moblin.org/show_bug.cgi?id=10121
ZhangJingke <jingke.zhang(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |10120
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
9:10 p.m.
New subject: [Bug 10121] Triggered on client side, "Direct syncevolution via OBEX" will fail
http://bugzilla.moblin.org/show_bug.cgi?id=10121
--- Comment #2 from Chen Congwu <congwu.chen(a)intel.com> 2010-03-09 02:10:05 PST
---
(In reply to comment #1)
Ah, this is caused by bluez, most likely the pairing process is not OK (you
need to reverse the hack you did for server initiated sync).
obexd[889]: RequestAuthorization error:
org.bluez.Error.NotAuthorized, Not
Authorized
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
2:20 a.m.
New subject: [Bug 10121] Triggered on client side, "Direct syncevolution via OBEX" will fail
http://bugzilla.moblin.org/show_bug.cgi?id=10121
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |patrick.ohly(a)intel.com
--- Comment #3 from pohly <patrick.ohly(a)intel.com> 2010-03-09 07:20:56 PST ---
(In reply to comment #2)
Ah, this is caused by bluez, most likely the pairing process is not
OK (you
need to reverse the hack you did for server initiated sync).
Which hack is that?
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
4:48 a.m.
New subject: [Bug 10121] Triggered on client side, "Direct syncevolution via OBEX" will fail
http://bugzilla.moblin.org/show_bug.cgi?id=10121
Bug 10121 depends on bug 10120, which changed state.
Bug 10120 Summary: SAN parsing regression introduced by SAN 1.1 support
http://bugzilla.moblin.org/show_bug.cgi?id=10120
What |Old Value |New Value
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
5:05 p.m.
New subject: [Bug 10121] Triggered on client side, "Direct syncevolution via OBEX" will fail
http://bugzilla.moblin.org/show_bug.cgi?id=10121
--- Comment #4 from ZhangJingke <jingke.zhang(a)intel.com> 2010-03-09 22:05:28 PST
---
The 'hack' is for two netbooks pairing:
1. On client machine, do './simple-agent hci0'
2. On server machine, do './simple-agent hci0 <client BT MAC>'
3. Input the PIN code, then the BT pairing could be done.
I checked Bluetooth FTP after pairing setup, both directions were good.
As Chongwu suggested, I deleted the pairing and re-pair again in different
direction: let client to do './simple-agent hci0 <server BT MAC>', then
syncevolution initiated from client can pass. Now, server cannot.
I will go on investigating the bluez authorization issue. BTW, I feel my
scenario is much like the planning 'push sync' feature (client tells server to
initial sync, which cannot be seen by user).
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
7:32 p.m.
New subject: [Bug 10121] Triggered on client side, "Direct syncevolution via OBEX" will fail
http://bugzilla.moblin.org/show_bug.cgi?id=10121
ZhangJingke <jingke.zhang(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |6871
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
7:42 p.m.
New subject: [Bug 10121] Triggered on client side, "Direct syncevolution via OBEX" will fail
http://bugzilla.moblin.org/show_bug.cgi?id=10121
--- Comment #5 from ZhangJingke <jingke.zhang(a)intel.com> 2010-03-10 00:42:01 PST
---
During my validation, we still have some things to be fixed in bluetooth
supporting:
1. Netbook bluetooth device is set invisibale by default. (should run
'hciconfig hci0 piscan' in root account).
2. Netbook does not integrate bluetooth-applet to support the authorization
between netbooks. see bug#6871
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
1:21 a.m.
New subject: [Bug 10121] Triggered on client side, "Direct syncevolution via OBEX" will fail
http://bugzilla.moblin.org/show_bug.cgi?id=10121
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |Waiting for upstream
Blocks| |7873
--- Comment #6 from pohly <patrick.ohly(a)intel.com> 2010-03-10 06:21:13 PST ---
(In reply to comment #5)
During my validation, we still have some things to be fixed in
bluetooth
supporting:
1. Netbook bluetooth device is set invisibale by default. (should run
'hciconfig hci0 piscan' in root account).
It can be made visible for a short period of time in the Netbook Bluetooth
applet.
2. Netbook does not integrate bluetooth-applet to support the
authorization
between netbooks. see bug#6871
There is a Bluetooth icon in my installation of a recent image. When I click
that, I get a dialog that contains scanning for devices and pairing them. It is
true that I had problems getting that to work, but it is not like it is missing
completely.
I think as far as SyncEvolution is concerned, we have done everything that we
can, right?
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
4:31 p.m.
New subject: [Bug 10121] Triggered on client side, "Direct syncevolution via OBEX" will fail
http://bugzilla.moblin.org/show_bug.cgi?id=10121
--- Comment #7 from ZhangJingke <jingke.zhang(a)intel.com> 2010-03-10 21:31:54 PST
---
(In reply to comment #6)
I think as far as SyncEvolution is concerned, we have done everything
that we
can, right?
I think so. To the feature, syncevolution has full support.
But for usability, I feel we need to consider how to combine "SyncEvolution"
and "SyncEvolutionClient" templates. They are a little confused for user: On
server side, we need to use "SyncEvolutionClient" to make config. It is better
to make it easier (we can check another issue for it). :)
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
6:15 p.m.
New subject: [Bug 10121] Triggered on client side, "Direct syncevolution via OBEX" will fail
http://bugzilla.moblin.org/show_bug.cgi?id=10121
ZhangJingke <jingke.zhang(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|major |normal
--- Comment #8 from ZhangJingke <jingke.zhang(a)intel.com> 2010-03-22 00:15:29 PST
---
For it has no fix by syncevolution, I downgrade the severity to normal.
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
1:13 a.m.
New subject: [Bug 10121] Triggered on client side, "Direct syncevolution via OBEX" will fail
http://bugzilla.moblin.org/show_bug.cgi?id=10121
--- Comment #9 from pohly <patrick.ohly(a)intel.com> 2010-03-22 07:13:58 PST ---
(In reply to comment #8)
For it has no fix by syncevolution, I downgrade the severity to
normal.
Who are we waiting for to do what? Do we have pointers to active issues about
that work?
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
2:24 a.m.
New subject: [Bug 10121] Triggered on client side, "Direct syncevolution via OBEX" will fail
http://bugzilla.moblin.org/show_bug.cgi?id=10121
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks|7873 |
AssignedTo|congwu.chen(a)intel.com |syncevolution(a)lists.intel.c
| |om
Severity|normal |enhancement
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
8:07 p.m.
New subject: [Bug 10121] Triggered on client side, "Direct syncevolution via OBEX" will fail
http://bugzilla.moblin.org/show_bug.cgi?id=10121
--- Comment #10 from pohly <patrick.ohly(a)intel.com> 2010-04-21 03:07:04 PST ---
(In reply to comment #0)
syncevolution: 0.9.99.11
openobex: 1.5-4.1
Description:
====================
This bug is following bug#9902 . Syncevolution via OBEX between two netbooks
can pass, triggered on server side. But triggering syncevolution command client
side will meet error.
Steps:
====================
1. Get two netbook paired.
2. On server side, make config1 for client with SyncEvolutionClient template.
3. On client side, make config2 for server with SyncEvolution template.
4. To avoid slow-sync affect, set preventSlowSync=0 on both sides.
5. Trigger on Server, PASS. 'syncevolution --run -s two-way config1
addressbook'
6. Trigger on Client, FAIL. 'syncevolution --run -s two-way config2
addressbook'
Expectation:
====================
Syncevolution process should pass, triggered by both client and server sides.
Root Cause:
====================
Tracked in comments.
This should work for "Netbook <-> Laptop" scenarios where the Netbook is
the
SyncML server and initiates the pairing, assuming that the laptop runs some
Linux distro which accepts pairing requests.
I've been told that once such a pairing completes, files can be pushed onto the
Netbook by the Laptop via Bluetooth. So I would expect SyncEvolution as client
on the Laptop to also be able to initiate a connection.
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
12:58 a.m.
New subject: [Bug 10121] Triggered on client side, "Direct syncevolution via OBEX" will fail
http://bugzilla.moblin.org/show_bug.cgi?id=10121
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|Waiting for upstream |RESOLVED
Resolution| |WORKSFORME
--- Comment #11 from pohly <patrick.ohly(a)intel.com> 2010-04-26 07:58:30 PST ---
(In reply to comment #10)
This should work for "Netbook <-> Laptop" scenarios
where the Netbook is the
SyncML server and initiates the pairing, assuming that the laptop runs some
Linux distro which accepts pairing requests.
I've been told that once such a pairing completes, files can be pushed onto the
Netbook by the Laptop via Bluetooth. So I would expect SyncEvolution as client
on the Laptop to also be able to initiate a connection.
And that does indeed work for me. I tried with a recent MeeGo netbook image and
a Debian desktop.
Whatever the issue is that Jingke had, it is more likely to be related to the
"pairing hack" and not the problem mentioned in the issue title. Therefore
I'm
closing this.
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
3:31 p.m.
New subject: [Bug 10121] Triggered on client side, "Direct syncevolution via OBEX" will fail
http://bugzilla.moblin.org/show_bug.cgi?id=10121
ZhangJingke <jingke.zhang(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Resolution|WORKSFORME |INVALID
--- Comment #12 from ZhangJingke <jingke.zhang(a)intel.com> 2010-04-26 22:31:55 PST
---
(In reply to comment #11)
(In reply to comment #10)
> This should work for "Netbook <-> Laptop" scenarios where the
Netbook is the
> SyncML server and initiates the pairing, assuming that the laptop runs some
> Linux distro which accepts pairing requests.
>
> I've been told that once such a pairing completes, files can be pushed onto the
> Netbook by the Laptop via Bluetooth. So I would expect SyncEvolution as client
> on the Laptop to also be able to initiate a connection.
And that does indeed work for me. I tried with a recent MeeGo netbook image and
a Debian desktop.
Whatever the issue is that Jingke had, it is more likely to be related to the
"pairing hack" and not the problem mentioned in the issue title. Therefore
I'm
closing this.
Our direct sync validation suffered much from bluetooth. I believe
syncevolution should have no issue (possibility should be 99.99% I think) but I
cannot prove it for pairing hacking. :(
Currently, I would like to close this as invalid for sync. Once BT pairing is
smooth enough, I will re-try this case and file new bug if there is. Thanks!
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
4527
days inactive
4576
days old
syncevolution-issues@syncevolution.org
16 comments
1 participants
participants (1)
-
bugzilla＠moblin.org