Opened 12 years ago

Closed 12 years ago

Last modified 4 years ago

#61 closed enhancement (fixed)

Collaboration: Seeing other users is Inconsistent

Reported by: CarolineM Owned by: morgs
Priority: Low Milestone:
Component: Sugar Version:
Severity: Minor Keywords:
Cc: caroline@…, guillaume.desmottes@… Distribution/OS: Ubuntu
Bug Status: Resolved

Description

There are 3 of us logged into a collaboration server.
The web page for eJabber says we are all online.
Last week we could all see each other.

Today one person can see one other person but the other 2 of us can't see anyone.

We are willing to help debug but we are not sure where to start.

Change History (17)

comment:1 Changed 12 years ago by CarolineM

  • Cc caroline@… added

This continues to be an issue. Sometimes we see each ohter sometimes we don't, rebooting the XOs a few times seems to help.

comment:2 Changed 12 years ago by CarolineM

My XO is not using automatic or extreme power management

comment:3 Changed 12 years ago by morgs

  • Owner changed from marcopg to morgs
  • Status changed from new to assigned
  • Summary changed from Collboration: Seing other users is Inconsident to Collaboration: Seeing other users is Inconsistent

Please follow http://wiki.laptop.org/go/Telepathy_debugging to enable logging on the XOs. Please provide presenceservice.log from each XO that has failed to see all the other XOs.

comment:4 Changed 12 years ago by overbyte

I'm having collaboration problems, too. I'm trying to collaborate among a real XO (updated yesterday to build 767), a desktop PC running latest LiveCD (XO-LiveCD_081201.iso), and a desktop PC running Ubuntu 8.04.1 up-to-date with latest Sugar from Ubuntu repository. Collaboration is inconsistent, doesn't detect when one computer goes offline (reboots or whatever), doesn't seem to link up invitations and joins, doesn't show a shared activity on Neighborhood view when it should, etc.

Is there a writeup of the collaboration protocols for making presence known, inviting, joining, detecting loss of one member (offline), and so on? Perhaps something like a UML sequence diagram would help so testers can run through the proper sequences and see what works and doesn't work, where things get stuck or lost, etc.

comment:5 Changed 12 years ago by morgs

overbyte, http://wiki.laptop.org/go/Presence_Service may help. It should link to all the relevant documentation we have.

It sounds like you are using serverless collaboration, which unfortunately is unreliable and difficult to debug. Furthermore, we have scalability problems and bugs in the server collaboration using ejabberd, including where a server's reliability degrades with the number of users registered on it.

Please provide presenceservice.log from each machine and we'll try to debug from that. See http://wiki.laptop.org/go/Telepathy_debugging to enable logging on the XO, and http://sugarlabs.org/go/Community/Distributions/Ubuntu to enable logging on Ubuntu.

comment:6 Changed 12 years ago by gregdek

  • Bug Status set to Needinfo
  • Distribution/OS set to Unspecified
  • Priority changed from major to Immediate
  • Severity set to Blocker

There have been changes to this part of the code. Are people still seeing this problem?

comment:7 Changed 12 years ago by gregdek

  • Milestone set to 0.84

comment:8 Changed 12 years ago by gregdek

  • Cc guillaume.desmottes@… added

cc:ing cassidy here. If we are still seeing these kinds of problems with the latest code drops, we'd like to knock them out for 0.84 if possible.

comment:9 Changed 12 years ago by gdesmott

Are you using Gadget or the shared roster?

comment:10 Changed 12 years ago by morgs

The reporters have not provided any log files, so there is nothing we can specifically work on.

comment:11 Changed 12 years ago by erikos

Please use these instructions on non XO http://sugarlabs.org/go/BugSquad/TelepathyDebugging

comment:12 Changed 12 years ago by tomeu

  • Bug Status changed from Needinfo to Resolved
  • Resolution set to fixed
  • Status changed from assigned to closed

Caroline says this got much better since the last updates, so we'll tentatively close this one and keep an eye open for inconsistencies.

comment:13 Changed 8 years ago by godiard

  • Milestone 0.84 deleted

Milestone 0.84 deleted

comment:13 Changed 4 years ago by Himanshu786

Since after the latest updates it is not continuing on. All things going properly

comment:14 Changed 4 years ago by Himanshu786

Since after the latest updates it is not continuing on. All things going properly.
My mail id:- himanshuwindows8.1@…

comment:15 Changed 4 years ago by Himanshu786

  • Priority changed from Immediate to Low
  • Type changed from defect to enhancement

comment:16 Changed 4 years ago by Himanshu786

  • Distribution/OS changed from Unspecified to Ubuntu
  • Severity changed from Blocker to Minor

All solved , we three friends also logged in collaboration server and nothing happened after the latest updates.

Note: See TracTickets for help on using tickets.