Summary: | contact: should check if TP_CONNECTION_FEATURE_CAPABILITIES has actually be prepared | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Guillaume Desmottes <guillaume.desmottes> |
Component: | tp-glib | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | normal | ||
Priority: | medium | Keywords: | patch |
Version: | git master | ||
Hardware: | Other | ||
OS: | All | ||
URL: | http://git.collabora.co.uk/?p=user/cassidy/telepathy-glib;a=shortlog;h=refs/heads/caps-crash-27686 | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Guillaume Desmottes
2010-04-16 03:26:38 UTC
The patch looks good, but I wonder if a better way to handle this would be to have TpConnection "successfully" report an empty set of capabilities if the connection doesn't have Requests. Tricky semantic rationale: if the connection doesn't have Requests, then there is nothing you can pass to CreateChannel/EnsureChannel, so by definition the set of requestable channel classes is empty :-) Make sense. I added a patch doing that but I think the other one still make sense any way. I added some patches to your branch, what do you think of this? http://git.collabora.co.uk/?p=user/smcv/telepathy-glib-smcv.git;a=shortlog;h=refs/heads/caps-crash-27686 Fixed for 0.11.3 using a combination of our branches. Teamwork! :-) (This bug was in code that has never been in a release, so no need to backport.) |
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.