Summary: | invisible status crashes gabble on recent ejabberd | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Simon McVittie <smcv> |
Component: | gabble | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | major | ||
Priority: | medium | CC: | kkszysiu |
Version: | 0.9 | Keywords: | NEEDINFO |
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Log from Gabble
Log from Gabble with wocky debug |
Description
Simon McVittie
2010-08-11 06:53:04 UTC
Works for me (I opened a new jabbim.com account). Can you reproduce this and provide a log? Ok, I attached log whats gabble doing when I change status to invisible. Created attachment 37789 [details]
Log from Gabble
This looks like a disconnection, not a crash. This bit looks suspicious: (telepathy-gabble:28724): gabble-DEBUG: remote_error_cb: remote error: xmlns: 'http://www.xmpp.org/extensions/xep-0084.html#ns-data ' is not a valid URI (telepathy-gabble:28724): gabble-DEBUG: remote_error_cb: Force closing of the connection 0x8459010 (telepathy-gabble:28724): tp-glib/connection-DEBUG: tp_base_connection_change_status: was 0, now 2, for reason 0 I conjecture that someone has sent you a wrong XEP-0084 avatar (not well-formed XML), and Wocky has tried to reply, but refused to send the reply because it's not well-formed XML? A debug log with Wocky debug enabled too (WOCKY_DEBUG=xmpp) would be useful. Created attachment 37790 [details]
Log from Gabble with wocky debug
Since telepathy-gabble 0.10.2, Wocky's had a workaround for these kinds of invalid namespaces in PEP nodes. |
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.