This appears similar to my results here with an XO-1 /VM and Soas Mirabelle: from: [email protected] > I just connected wirelessly > > 1- ) Mirabelle USB > Started Chat as shared in Mirabelle > 2- )Blueberry.vmx > Joined > 3- ) XO-1 os230py (Sugar 0.88.0) > Joined > > > XO-1 saw all connections colors and text > Blueberry saw 1/2 of connections with color balance were ???? plus text > Mirabelle saw only its own broadcasts in color all others were ?????plus > text > > Is Mirabelle configured to require the Gadget Service? > > Tom Gilliard > satellit > > Telepathy log: > > 1275085638.929632 WARNING s-p-s.presenceservice: Error fetching buddy > properties for handle 99 keyid/db81d25ebff2f9e8c47c792b86c9584af31c601e: > org.freedesktop.Telepathy.Error.NetworkError: Server does not provide > Gadget Buddy service > > There was no collaboration available using the "adhoc" network connection,
or the link-local (no jabber listed on CP Network screen) I could see the avitar of originating user and his application icon on the second computer and join but was not able to get a working cursor on either chat or write. There must be a bug in collaboration when not using the Jabber presence connection. Tom Gilliard satellit Mikus Grinbergs wrote: > Simple test of collaboration using two Sugar-0.88_on_F11 XO-1 systems: > > I don't know why os240py has three 'Mesh' icons in Neighborhood View. > The systems connected automatically on Mesh channel 1 -- they showed > each other in Neighborhood View, and I could 'ping' between them. > > BUT, Activities seemed unable to use this 'Mesh' connection. [For > instance, Chat-66 came up as "off-line" - and I appeared to have NO WAY > to change that status.] I was able to make the two systems "Friends" of > each other; I was able to extend invitations via Friends View between > systems -- but although the invitee could launch the indicated Activity, > there was no collaboration - the respective Activities were not in > communication with each other - very frustrating. [When "Neighborhood" > sharing was activated for an Activity, the "Join this" icon did NOT > appear in the Neighborhood View of the other system.] > > > I then, on one system, clicked on 'Create new wireless network' in the > palette on the gray circle in Frame bottom -- that assigned the same IP > address (on the new network) as was being shown on the 'Mesh' icon in > Frame -- and set up a NEW network icon in the Neighborhood Views of both > systems. On the other system I clicked on this new icon in Neighborhood > View - that assigned the same IP address (on the new network) as was > being shown (on that other system) on the 'Mesh' icon in Frame. > > Now, Activities were able to make use of this "new" network connection. > I tested Chat-66 and Write-67. Collaboration worked as I expected. > > > Given that system-to-system collaboration works on the "new" wireless > network, and appears NOT to work on the 'Mesh' network -- why provide an > obsolete interface that serves primarily to cause frustration in users ? > > > mikus > > _______________________________________________ > Testing mailing list > [email protected] > http://lists.laptop.org/listinfo/testing > > _______________________________________________ Testing mailing list [email protected] http://lists.laptop.org/listinfo/testing
