Bug 20421

Summary:	Terminate the call when receiving messages referring to a stream that doesn't exist
Product:	Telepathy	Reporter:	Sjoerd Simons <sjoerd>
Component:	gabble	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED MOVED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Sjoerd Simons 2009-03-02 06:32:31 UTC

I haven't tested it very extensively, but in a few of my tests after removing a content that just sprang to live the call got terminated. From a quick look it seems that Gabble received a transport-info referring to the content it just removed from the other side and decides to terminate the call because of that

Comment 1 Will Thompson 2009-06-25 04:03:11 UTC

I think this may have been a side-effect of the buggy code to replace contents with the same name?

Comment 2 GitLab Migration User 2019-12-03 19:18:31 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/22.

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.