I added some code to AbiCollab to let a collaborative Write session continue when the session initiator disconnects. However, I seem to have a problem rejoining an activity. This is what I do: 1. Start Write 2. Share it 3. Let someone join 4. Close write (the one that initiated the share) 5. Rejoin the still running session Now a "ListTubes"[1] call on the existing tube channel will return no tubes in the callback. Why is that? It's especially weird since it WILL return a tube when you fire up another jhbuild/XO and join that session. ListTubes just seems to turn into a 'no-op' when you join on a machine that was already part of the session before.
Created attachment 29168 [details] Log from the original initiator side This is the gabble log from the initiator/rejoining side. Before rejoining, I exitted the 'jhbuild environment' and re-started again. I did this because I did not see the shared Write in the neighborhood after closing it on the inititator's side. The attached log belongs to this 'session'.
Created attachment 29169 [details] Log from the original joiner side This is the log from the joining party, who remained in the session while the initiator left and tried to rejoin.
FYI: this does work correctly with salut, so the bug isn't an AbiCollab/Write bug.
Got it. Gabble wrongly assumes that muc D-Bus tubes are outgoing ones if we initiate them which is not true if you re-join a muc and one of your old tube is still there. Working on a fix.
Should be fixed in http://git.collabora.co.uk/?p=user/cassidy/telepathy-gabble;a=shortlog;h=refs/heads/list-tube-23678
Fixed in master (future 0.9) and the stable 0.8 branch (future 0.8.3).
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.