#8808 NORM Not Tri: 8.2-767: Collaboration failure

[Zarro Boogs per Child]

#8808: 8.2-767: Collaboration failure
--------------------------------+-------------------------------------------
   Reporter:  joe               |       Owner:  joe          
       Type:  defect            |      Status:  new          
   Priority:  normal            |   Milestone:  Not Triaged  
  Component:  presence-service  |     Version:  not specified
 Resolution:                    |    Keywords:               
Next_action:  reproduce         |    Verified:  0            
  Blockedby:                    |    Blocking:               
--------------------------------+-------------------------------------------

Comment(by joe):

 Replying to [comment:1 morgs]:
 > Joe,
 >
 > The log files didn't have debug messages enabled. Please follow
 http://wiki.laptop.org/go/Attaching_Sugar_Logs_to_Tickets to enable
 SUGAR_LOGGER_LEVEL=debug for every laptop you do any kind of testing with,
 as we are never sure that we can reproduce a scenario after the fact. You
 should probably always enable
 http://wiki.laptop.org/go/Telepathy_debugging if you are testing
 collaboration, as we may need the telepathy log files too.
 >
 > What I can tell though, even without logs, is that it's not Chat at
 fault here, and no amount of closing it and reopening it will help.
 Presence Service maintains the state of who you can see and collaborate
 with, and if we get debug logs we will probably be able to determine what
 happened by looking at presenceservice.log - so I'm assigning to that
 component. I'm also changing the subject line, because relaunching Chat
 could never fix Presence Service or network state.
 >
 > Please reassign to Collabora when you can reproduce this with debug
 logs.
 ------------
 Will do. With 62+ laptops in the testbed, this may be a time-consuming
 exercise. ;-)

 Joe

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