- open an activity on machine A - invite machine B to it - quit activity in machine A ---> a new invitation on machine B is launched, a chat activity in the color of machine B and the invitation is not removed I would expect that the previous invitation is removed on B as A did close the activity.
Created attachment 48466 [details] tp-salut logs from machine A
Created attachment 48467 [details] tp-salut logs from machine B
In B's log: ** (telepathy-salut:2224): DEBUG: uninvite_stanza_callback: room ca6e5f59@laptop unknown So it gets the uninvite stanza but for some reason the handle has been lost somewhere. The SalutOlpcActivity is supposed to keep the ref on the handle. Can you add some debug in olpc-activity.c to check if the object created when receiving the invitation stays alive?
(In reply to comment #3) > In B's log: > > ** (telepathy-salut:2224): DEBUG: uninvite_stanza_callback: room > ca6e5f59@laptop unknown > > > So it gets the uninvite stanza but for some reason the handle has been lost > somewhere. The SalutOlpcActivity is supposed to keep the ref on the handle. Can > you add some debug in olpc-activity.c to check if the object created when > receiving the invitation stays alive? What I tried is to set the room_handle there to '1' and this does then finally remove the invitation activity. So, the room is still there and either the list of handles is not right anymore or what we get from the stanza 'gibber_xmpp_node_get_attribute (node, "room");' is faulty.
You can use tp_handle_set_dump() to dump all the known handles.
(In reply to comment #5) > You can use tp_handle_set_dump() to dump all the known handles. In telepathy-glib-0.11.16-1 which we use on this fc14 based build we do not seem to have tp_handle_set_dump if my greps are correct. Anything else I can use to quickly find out?
Outch that's very old. You should really consider upgrading to tp-glib 0.14.x (stable branch).
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-salut/issues/29.
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.