| Summary: | Gabble seems to misbehave on the empty codec intersection | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Will Thompson <will> |
| 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: | ||
| Attachments: |
.
empathy log |
||
Created attachment 25109 [details]
empathy log
-- 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.
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.