http://bugzilla.moblin.org/show_bug.cgi?id=8879
--- Comment #6 from pohly <patrick.ohly(a)intel.com> 2010-02-21 23:38:01 PST ---
(In reply to comment #5)
This is not applicable from the UI (with presence detection).
You mean the UI will never run into this situation because it will only start
syncing when Bluetooth is enabled? I disagree. Some GUIs might not use presence
detection, there are race conditions, without ConnMan it doesn't work.
Whether we should
implement this in the command line is debatable: There is no distribution
independent way to query status of local BT adapater or HTTP Adapter without
depending on dbus service (connman or network manager).
I am inclined to leave this as it is and the command line will benefit from
presence detection once its implementation changed to use syncevo-dbus-server.
Thoughts?
I agree with this. But there's still one aspect of this issue which has to be
solved. When Bluetooth is unavailable, the error reporting is insufficient.
I get:
[ERROR] TransportException while sending SAN package
[ERROR] Server Alerted Sync init failed
fatal error (local, status 10500)
The TransportException should be reported back up to the top level. Instead it
seems that initSAN() catches it and then just reports back that it didn't
succeed. Why do you catch the exception instead of letting it propagate?
Because of that, we end up with two ERROR lines for the same thing and an
unspecific 500 status.
--
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.