Bug 21386 - Gabble seems to misbehave on the empty codec intersection
Summary: Gabble seems to misbehave on the empty codec intersection
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-24 08:28 UTC by Will Thompson
Modified: 2019-12-03 19:19 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
. (29.86 KB, application/octet-stream)
2009-04-24 08:28 UTC, Will Thompson 		Details
empathy log (8.68 KB, application/octet-stream)
2009-04-24 08:28 UTC, Will Thompson 		Details
View All

Description Will Thompson 2009-04-24 08:28:13 UTC 
Created attachment 25108 [details]
.

Guillaume called his N810 from Empathy on his laptop, which only speaks Theora. Gabble on the N810 sends back a content-accept with no codecs!

Modern Gabble is okay with this, and afaict should just emit SetRemoteCodecs([]). TpFs should respond to that by calling Error() on the stream. But it doesn't seem to.

I initially thought this was a bug in TpFs, but Olivier reminded me that his code is perfect, so perhaps it is a bug in Gabble. :-)

Attaching Guillaume's logs.
Comment 1 Will Thompson 2009-04-24 08:28:55 UTC 
Created attachment 25109 [details]
empathy log
Comment 2 GitLab Migration User 2019-12-03 19:19:09 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/30.

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.