[Bugs] #928 HIGH: Salut: Sharing activities not working
Sugar Labs Bugs
bugtracker-noreply at sugarlabs.org
Sat Oct 3 13:31:05 EDT 2009
#928: Salut: Sharing activities not working
--------------------------+-------------------------------------------------
Reporter: erikos | Owner: gdesmott
Type: defect | Status: new
Priority: High | Milestone: 0.86
Component: telepathy | Version: 0.84.x
Severity: Blocker | Keywords: GPA
Distribution: Fedora | Status_field: New
--------------------------+-------------------------------------------------
Comment(by Jose Icaza):
Very sorry to reply this late - somehow comments to this ticket did not
get to my gmail address, when other ticket's comments did.
Replying to [comment:13 gdesmott]:
> From my understanding of this bug, the logs attached by Erikos were
because of A (firewall issue); right?
>
Yes I think so; but turning off the firewall did not work for us.
>
> Jose: When you say "can't share", what do you mean exactly? The shared
activity doesn't appear in the peer's mesh view? It appears but when
trying to join it nothing happen (data are not exchanged between the 2
laptops)?
>
Correct, the shared activity does not appear in neighborhood view of the
other machine... sometimes! Couldn't reproduce bug reliably
> Is this problem specific to a set of laptops (classmate?)? That could be
a network driver issue (buggy multicast implementation).
Perhaps... It didn't happen between an older model Dell laptop and a
Toshiba. But it did happen between two Dells for Caroline...
> Did you observe this bug only on SoaS or did you reproduce it using
sugar-jhbuild as well (using the same hardware in both cases)?
>
Just with plain Strawberry. Should try it with jhbuild
> Could you reproduce this issue and attach telepathy-salut log when it
happens? http://wiki.laptop.org/go/Telepathy-debug uses to contain
instructions about how to enable Telepathy debugging but I don't know if
that still apply for SoaS. Sugar guys would probably be able to help you
for this.
Sure, I will... For the moment we have solved the problem by installing a
local ejabberd server running Xubuntu on a Classmate serving as server.
The student classmates are addressed to the local IP of the jabber server.
But in some other deployment without server (just an access point to set
up the wireless net) the problem will likely appear.
--
Ticket URL: <http://bugs.sugarlabs.org/ticket/928#comment:19>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list