#6739 BLOC Update.: Sharing failures with Write (and Read).

[Zarro Boogs per Child]

#6739: Sharing failures with Write (and Read).
-----------------------------+----------------------------------------------
 Reporter:  cjb              |       Owner:  Collabora
     Type:  defect           |      Status:  new      
 Priority:  blocker          |   Milestone:  Update.1 
Component:  telepathy-salut  |     Version:           
 Keywords:                   |    Verified:  0        
 Blocking:                   |   Blockedby:           
-----------------------------+----------------------------------------------
 Attached are logs from the joiner and sharer of a Write activity.  The
 joiner clicked on an "my neighborhood"-shared Write, Write launched, but
 the activity toolbar thought it was "Private", and the text in the
 sharer's Write didn't appear on the joiner's screen.  Build 699, connected
 to an access point with Salut.

 The error in the joiner's log is a duplicate of the error seen with Read
 yesterday, in #6722.  Namely:

 {{{
 1206139420.698640 DEBUG sugar.presence.activity: <proxy for
 /org/laptop/Sugar/Presence/Activities/1 at 842a2d4>: Join failed because:
 org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible
 causes include: the remote application did not send a reply, the message
 bus security policy blocked the reply, the reply timeout expired, or the
 network connection was broken.
 1206139420.701489 DEBUG root: Failed to join activity:
 org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible
 causes include: the remote application did not send a reply, the message
 bus security policy blocked the reply, the reply timeout expired, or the
 network connection was broken.
 }}}

 So, we think we have a generic sharing failure on build 699.  Could
 someone at Collabora help us start tracking this down?

-- 
Ticket URL: <http://dev.laptop.org/ticket/6739>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system