Summary: | get error when sending messages in jabber chatroom in lots of cases | ||
---|---|---|---|
Product: | [Unmaintained] telepathy | Reporter: | Belomir <leggis> |
Component: | text-ui | Assignee: | Telepathy Bugs <kde-telepathy-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | kde, mklapetek |
Priority: | NOR | ||
Version First Reported In: | 0.5.1 | ||
Target Milestone: | Future | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
gabble dbg log greped by errors and tailed
gabble dbg log greped by errors gabble full dbg log |
Description
Belomir
2013-01-03 12:56:49 UTC
Do you still get this in 0.5.3? Could you run ktp-debugger and attach the output from the tab marked "gabble" when this is occurring. 0.5.3 wasn't released yet, please try with 0.5.2 :) Created attachment 76524 [details]
gabble dbg log greped by errors and tailed
I think something wrong with streams.
Created attachment 76525 [details]
gabble dbg log greped by errors
Created attachment 76526 [details]
gabble full dbg log
I am sorry, it updated automatically and I have 0.5.2 version now. The error is stillpresent. But I got another trouble and unable to investigate further: telepathy disconnect me twice/trice per second from jabber after I try to join chat room. Logs are attached. Strange but kopete do the same. Do recent comments provide the requested information? Re-opening due to attached gabble logs. "17.01.2013 12:15:08.473053 - [wocky] handle_stream_error: wocky-c2s-porter.c:444: Received stream error; consider the remote connection to be closed" It's definitely not our KDE code at fault, but it could still be a problem in the telepathy framework. I would say that if Kopete also has issues connecting, the problem may well lie in the servers involved. For example GTalk cannot connect to a chat room on conferences.jabber.org under any client. Are you able to connect in any client? PSI is a very good Qt pure Jabber client, if that can't connect, nothing will and there's nothing we can do. Otherwise we will investigate further. If you can provide the information requested in comment #8 (last paragraph), please add it. Changing to waitingforinfo. More than a year without activity, so closing this report as the whole stack got many updates in the meantime. Please retest with newest versions of KTp and Telepathy and if problem still persists, please reopen with new info. |