Bug 312536 - get error when sending messages in jabber chatroom in lots of cases
Summary: get error when sending messages in jabber chatroom in lots of cases
Status: RESOLVED WORKSFORME
Alias: None
Product: telepathy
Classification: Unmaintained
Component: text-ui (show other bugs)
Version: 0.5.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: Future
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-03 12:56 UTC by Belomir
Modified: 2014-04-11 16:55 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
gabble dbg log greped by errors and tailed (710 bytes, application/octet-stream)
2013-01-17 05:47 UTC, Belomir
Details
gabble dbg log greped by errors (9.84 KB, application/octet-stream)
2013-01-17 05:47 UTC, Belomir
Details
gabble full dbg log (3.56 MB, application/octet-stream)
2013-01-17 05:53 UTC, Belomir
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Belomir 2013-01-03 12:56:49 UTC
When sending messages (russian for instance) in jabber conference chatroom I got error message like: Delivery of the message "Anybody hear me?" failed because it was too long

It was in 0.3 version from kubuntu 12.04 and the same in 0.5 from telepathy ppa

this happens not always. Time after time the message is send without error messages.

Reproducible: Sometimes

Steps to Reproduce:
1. Join any jabber conference
2. Type and send any message
3. Get the error
Actual Results:  
Get the error 'Delivery of the message "…" failed because it was too long'

Expected Results:  
Normal message sending with any unicode characters

kde-telepathy from ppa
I thought updated version haven't this issue.
Comment 1 David Edmundson 2013-01-16 01:44:13 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.
Comment 2 Martin Klapetek 2013-01-16 10:52:14 UTC
0.5.3 wasn't released yet, please try with 0.5.2 :)
Comment 3 Belomir 2013-01-17 05:47:17 UTC
Created attachment 76524 [details]
gabble dbg log greped by errors and tailed

I think something wrong with streams.
Comment 4 Belomir 2013-01-17 05:47:58 UTC
Created attachment 76525 [details]
gabble dbg log greped by errors
Comment 5 Belomir 2013-01-17 05:53:09 UTC
Created attachment 76526 [details]
gabble full dbg log
Comment 6 Belomir 2013-01-17 05:57:51 UTC
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.
Comment 7 Christoph Feck 2013-01-24 01:27:14 UTC
Do recent comments provide the requested information?
Comment 8 David Edmundson 2013-01-24 01:32:47 UTC
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.
Comment 9 Christoph Feck 2013-01-31 00:00:17 UTC
If you can provide the information requested in comment #8 (last paragraph), please add it.
Comment 10 Martin Klapetek 2013-02-05 12:42:35 UTC
Changing to waitingforinfo.
Comment 11 Martin Klapetek 2014-04-11 16:55:20 UTC
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.