When owner leaves, shared activity does not always go away on his own view (link-local)

[erikos]

Upstream bug at SL: http://bugs.sugarlabs.org/ticket/2192 (has as well a tracking down of the issue).

Steps to reproduce:

- A: Share activity

- B: Join

- B: Leave activity

---> both neighborhood views are updated correctly (buddy leaves)

- A: Stop shared activity

---> activity goes not away from A's neighborhood view, but goes away from B's

---

Follow up test:

- A: share another activity

- B: join

---> on A the old shared activity goes away

[erikos]

Seems to be a link local issue "only".

[Quozl]

Reproduced easily.

This was previously reported here #9545 (icons persist in Neighborhood View after resources gone), #9560 (os33 - Neighborhood View unreliable), and possibly #9619 (Network View unstable after quitting shared chat activity) but had not been investigated to the level of detail of SL 2192. Good to see more focus on it.

[erikos]

diff --git a/src/activity.py b/src/activity.py
index 29ba1a5..6c5825c 100644
--- a/src/activity.py
+++ b/src/activity.py
@@ -1143,6 +1143,7 @@ class Activity(ExportedGObject):
         # we've joined.
         if self._joined:
             self._remove_buddies(removed_buddies)
+            self._claimed_buddies -= removed_buddies
 
         # if we were among those removed, we'll have to start believing
         # the spoofable PEP-based activity tracking again.

Looks like the fix is as "simple" as that. Testes for Salut and verified that it does not break anything on Gabble. (Mind that due to salut vs collaboration there might be occasions where we still see leftover sharing activities on some neighborhood views. To be 100% where the issue might be we need to first test with idle suspend disabled)

[erikos]

Fixed by: http://git.sugarlabs.org/projects/sugar-presence-service/repos/mainline/commits/fd0ee7110b32a06faa23375ade0a6d98b64ace81

Regression was introduced by: http://dev.laptop.org/ticket/9619

[erikos]

Did land in 351.

[greenfeld]

Verified that we no longer see the closed activity after following the reproduction steps above in 10.1.3 os352 with ad-hoc, AP-based salut, and mesh networks on both XO 1 & 1.5 machines (as appropriate).

[garycmartin]

Not sure if this should be a new ticket, but the reverse of this test case is still leaving the activity icon behind on the initiators neighbourhood view:

- A: Share activity

- B: Join

- A: Stop shared activity

- B: Stop shared activity

---> activity icon is left on A's neighbourhood view