Bug 37897 - telepathy-gabble assumes that jabber server should send muc#roomconfig_allowinvites
Summary: telepathy-gabble assumes that jabber server should send muc#roomconfig_allowi...
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: 0.12
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-03 15:28 UTC by Aleksey Lim
Modified: 2019-12-03 19:52 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
telepathy-gabble error log (39.63 KB, text/x-log)
2011-06-03 15:28 UTC, Aleksey Lim
Details

Description Aleksey Lim 2011-06-03 15:28:47 UTC
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.
Comment 1 Will Thompson 2011-09-06 10:11:30 UTC
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 …
Comment 2 GitLab Migration User 2019-12-03 19:52:23 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/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.