Bug 22337 (nloko)

Summary:	Closed signal not raised if contact A closes tube before contact B accepts/closes
Product:	Telepathy	Reporter:	Neil Loknath <neil.loknath>
Component:	gabble	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED MOVED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium	CC:	neil.loknath
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Neil Loknath 2009-06-17 13:10:56 UTC

Overview: 

    If contact A offers a tube to contact B, and contact A closes before contact B accepts/closes, contact B should get the closed signal and not be allowed to accept the tube.

Steps to Reproduce: 

    1) Use Requests.CreateChannel to create a DBusTube with contact B's handle as TargetHandle

    2) Offer tube on NewChannels signal

    3) Contact B get's Requests.NewChannels signal for the tube, but does not respond immediately.

    4) Contact A closes the tube.


Actual Results: What the application did after performing the above steps.

     No closed signal is raised on contact B's side and contact B can still accept the tube.

Expected Results: What the application should have done, were the bug not present.

    Contact B should get the closed signal and not be allowed to accept the tube.

Build Date & Platform: 

    Ubuntu Jaunty 9.04
    telepathy-gabble 0.7.28

Comment 1 GitLab Migration User 2019-12-03 19:20:13 UTC

-- 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-gabble/issues/44.

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.