Summary: | Media channel: need better error reporting | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Guillaume Desmottes <guillaume.desmottes> |
Component: | tp-spec | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED MOVED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | major | ||
Priority: | high | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Guillaume Desmottes
2009-06-22 03:22:23 UTC
We could add a bunch of new Media_Stream_Errors, but indeed we can't say *which* codecs were missing. Here's a bad idea: maybe Empathy could secretly listen to the StreamHandlers' signals so it knows what codecs the peer supports, and infer from Media_Stream_Error_No_Supported_Codecs that the error message should list them? The solution for "need codec" problems is to implement Gst Missing plugins in Farstream. Is this still a problem in Call? If not, let's WONTFIX it. This bug has made the default GNOME desktop unusable for video conference for me for 6 years. -- 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-spec/issues/26. |
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.