Summary: | In my jabber account almost always give me an error for 'too long message' por any length | ||
---|---|---|---|
Product: | [Unmaintained] telepathy | Reporter: | Pablo <elfio> |
Component: | text-ui | Assignee: | Telepathy Bugs <kde-telepathy-bugs> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | kde, rohan |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | 0.4.0 | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | telepathy-gabble-xmpp-console debug output screenshot |
Description
Pablo
2012-01-30 22:50:32 UTC
If this does happen it's almost certainly an issue in the jabber backend. Please make sure you have the latest version of telepathy-gabble. If so please attach a log from gabble the jabber backend, as explained here: http://martys.typepad.com/blog/2011/12/kde-telepathy-now-depends-on-telepathy-qt4-09-also-how-to-report-bugs.html A sure shot way of reproducing this is to start chats over 2 different XMPP networks for eg between jabber.org and gtalk. Usually after talking for the first 30 seconds, you can see the error and then can only send 3-4 characters at a time and not full sentences. Could be successfully reproduced on latest master. No errors could be seen in the gabble logs. David tells me there's a python script that reads the full XMPP stream which could help us debug this further. Narrowed it down to this : Jabber <-> Jabber : Works GTalk <-> GTalk : Works GTalk -> Jabber : Works Jabber -> GTalk : Does not work It seems like Google might be rejecting messages from other XMPP networks if they send them too quickly, would certainly be need to fixed at their end. Created attachment 69733 [details]
telepathy-gabble-xmpp-console debug output screenshot
A couple of XMPP stanzas that clearly show the error, just for future reference purposes. I'm also trying to track this bug down and fix it ... might take a while though.
|