Opened 10 years ago

Closed 10 years ago

Last modified 21 months ago

#1955 closed defect (fixed)

Can't always see other XOs in Neighborhood/Groups view

Reported by: jfuhrer Owned by: morgs
Priority: blocker Milestone:
Component: presence-service Version:
Keywords: Cc:
Blocked By: Blocking:
Deployments affected: Action Needed:
Verified: no


OFW: Q2C18 for both
Build: 488 for both

I have two XOs (one B3, one B2) that are on the same channel and are able to ping each other, and are also able to detect and display at least one common XO. But they do not appear on each other's Neighborhood views. Also, the latter cannot detect the Connect activity that the former was sharing, either. I've attached the shell log from the B2.

Attachments (2)

shell.log (6.9 KB) - added by jfuhrer 10 years ago.
presenceservice.log (40.0 KB) - added by jfuhrer 10 years ago.
Pretty sure this is a presence service problem.

Download all attachments as: .zip

Change History (8)

Changed 10 years ago by jfuhrer

comment:1 Changed 10 years ago by jfuhrer

  • Priority changed from high to blocker

This problem's a lot worse than I had originally thought and, in fact, happens almost all the time. It's very rare that I can see any other XOs, regardless of whether I'm using an access point or the mesh network, and when I do it is 1-2 tops (and never the few that are sitting around me in close proximity to each other). They can still always ping each other just fine though, it's just very rare that they show up.

comment:2 Changed 10 years ago by jfuhrer

Here's what I've found is the case, testing on a B3.

On the FIRST boot after installing the image, finding other XOs works great. I consistently found 5-6, including the ones that were right next to me. On boots after that, it rapidly deteriorates, finding only 1-2, and eventually none (sometimes even having trouble connecting to the mesh in the first place). I tested this four times, in sets of four boots (each set starting with a reinstall) and the pattern was pretty clear. After EVERY reinstall of the image, XO detection was fine for one boot. (Finding activities still doesn't work, though).

The B2 in general seems to be much worse at finding and displaying XOs for whatever reason, but it also seemed to follow the pattern (just slightly less noticeably, starting with consistently finding 2-3 XOs and going down to none).

comment:3 Changed 10 years ago by morgs

  • Component changed from network manager to presence-service
  • Owner changed from dcbw to morgs
  • Status changed from new to assigned

I will follow up with Sjoerd Simons, who works on telepathy-salut. I presume your testing was basically on the link local mesh (since the PS server was mostly down). Sjoerd did mention that he found and fixed a problem on the weekend... could be related.

Changed 10 years ago by jfuhrer

Pretty sure this is a presence service problem.

comment:4 Changed 10 years ago by smcv

I'm pretty sure this is, in fact, a telepathy-salut problem - the presence service log shows disconnections for reason 5, which is Connection_Status_Reason_Name_In_Use. morgs, we need to check under what circumstances Salut uses that reason - does that sound like the bug sjoerd fixed?

comment:5 Changed 10 years ago by jfuhrer

  • Resolution set to fixed
  • Status changed from assigned to closed

I think 514 finally fixed this. I'm able to see all XOs consistently, even after reboots.

comment:6 Changed 21 months ago by Quozl

  • Milestone Trial-2 deleted

Milestone Trial-2 deleted

Note: See TracTickets for help on using tickets.