| Summary: | telepathy-gabble assumes that jabber server should send muc#roomconfig_allowinvites | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Aleksey Lim <alsroot> |
| Component: | gabble | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | 0.12 | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | telepathy-gabble error log | ||
Interesting, thank you for the report. I've actually removed invite-restricted entirely in a branch I'm working on (given that you could only ever set that property, not read it, it seems a little useless…) … and actually I removed Telepathy.Properties entirely, replacing it with an API that sucks less. I guess this means that your client (Sugar?) uses Telepathy.Properties, and someone will have to update it … -- 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/153. |
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 47497 [details] telepathy-gabble error log Rposody (from git Fri Jun 3 05:36:44 2011 and looks like stable versions as well) doesn't return muc#roomconfig_allowinvites setting but gabble assumes receiving it and fails with creating muc.