Gabble: when B joins a shared session it is not grouped right on A

[erikos]

- A shares an activity (e.g. Memorize)

- B joins it

---> on machine A member B is not grouped around the activity (nb view), on machine B member A is grouped around the activity (nb view)

[erikos]

As well a 10.1.3 machine (C) connected to the same network only sees the active activity change of A but not of B. A is grouped around the shared activity B is not on C's nb view.

[erikos]

The log does show that we do not have a connection when we want to set the current activity:

1310912354.641366 DEBUG root: launch bundle_id=org.laptop.Chat activity_id=69e88ec65ca493c6e6999c1e4693fd26fb0c2b07 object_id=None uri=None
1310912354.700312 DEBUG root: launching: ['sugar-activity', 'activity.Chat', '-b', 'org.laptop.Chat', '-a', dbus.String(u'69e88ec65ca493c6e6999c1e4693fd26fb0c2b07')]
1310912354.745627 DEBUG root: __activity_added_cb: <Activity object at 0xac65b6c (SugarHomeActivity at 0xa76be10)>
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/jarabe/model/neighborhood.py", line 392, in __active_activity_changed_cb
    connection = self._connection[CONNECTION_INTERFACE_BUDDY_INFO]
TypeError: 'NoneType' object is not subscriptable
1310912354.755791 DEBUG root: __activity_changed_cb: <Activity object at 0xac65b6c (SugarHomeActivity at 0xa76be10)>
1310912354.757156 DEBUG root: FriendsTray.__active_activity_changed_cb
1310912354.817738 DEBUG root: FriendsTray._set_current_activity

[erikos]

full shell log that shows the case

[erikos]

There is another case that has the same trace in the log:

A and B connected to Gabble:

- A shares Memorize

- B joins

- B leaves

---> A does not get notified about it, the frame is not updated, the buddy in the activity is not removed

[erikos]

When the server connection is established we do disable the Salut account. We do as well set self._connection to None, but this is the current server connection. Hence when we do join the activity and try to call SetCurrentActivity on the current connection it fails.

I did remove the 'self._connection = None' and we can call SetCurrentActivity on the connection now. However in the case when we join an activity we get the following traceback when calling SetCurrentActivity.

311096726.183528 DEBUG root: _Account.__set_current_activity__error_cb DBusException(dbus.String(u"Can't set an activity as current if you're not announcing it"),)

[erikos]

This is the link to the tp-gabble debug message.

Maybe it is a similar issue then the one discovered in Salut, where when B jois the activity we do not announce that, A is then not knowing about the new state of B (ActivitiesChanged). At least the outcome is the same on gabble: when B joins no 'ActivitiesChanged' signal is received on A.