Bug 287575 - Telepathy continuously disconnect and reconnect to all my accounts
Summary: Telepathy continuously disconnect and reconnect to all my accounts
Status: RESOLVED UPSTREAM
Alias: None
Product: telepathy
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: git-latest
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: 0.4.0
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-25 20:38 UTC by Robby Engelmann
Modified: 2012-07-06 12:47 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
my bash script to get all sources (1.65 KB, application/x-shellscript)
2011-11-25 20:38 UTC, Robby Engelmann
Details
my bash script to build and install all components (3.99 KB, application/x-shellscript)
2011-11-25 20:39 UTC, Robby Engelmann
Details
requested log (314.11 KB, text/x-log)
2011-11-25 21:03 UTC, Robby Engelmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robby Engelmann 2011-11-25 20:38:49 UTC
Created attachment 66080 [details]
my bash script to get all sources

Version:           git-latest (using KDE 4.7.3) 
OS:                Linux

dis-reconnect cycles repeat <1min, thus at the moment it is impossible to use

Reproducible: Always

Steps to Reproduce:
-compile all telepathy-kde components from source
-add presence applet to system tray
-setup jabber/facebook/skype account
-set presence to online

Actual Results:  
-all three account dis- and reconnect continuously


Expected Results:  
-stable connection
Comment 1 Robby Engelmann 2011-11-25 20:39:38 UTC
Created attachment 66081 [details]
my bash script to build and install all components
Comment 2 Martin Klapetek 2011-11-25 20:51:08 UTC
Ok, we'll need a little debug from you.

First, please disconnect all accounts and close all Telepathy related components. Then open up a terminal and paste this command:

GABBLE_PERSIST=1 GABBLE_DEBUG=all /usr/libexec/telepathy-gabble > ~/gabble.log

This will create a logfile in your home directory. Open it and check if it contains any sensitive data, if so, replace them with 'X' and then please paste the log here.

Also note, that your telepathy-gabble might be in different path, so if that command above says it cannot find telepathy-gabble, you'll have to find it first (use locate for example, ie. 'locate telepathy-gabble').

Thanks.
Comment 3 Robby Engelmann 2011-11-25 21:03:03 UTC
here the log. I removed presence applet after setting all account to offline, then I did
~$ GABBLE_PERSIST=1 GABBLE_DEBUG=all /usr/lib/telepathy/telepathy-gabble > ~/gabble.log

After that, I readded the applet and set all accounts to online, waited short (two dis and reconnect messages)

And here to (quite long) log:
Comment 4 Robby Engelmann 2011-11-25 21:03:53 UTC
Created attachment 66083 [details]
requested log
Comment 5 David Edmundson 2011-11-25 21:29:56 UTC
the important line.
** (telepathy-gabble:8287): DEBUG: send_iq_async failed: Error sending data: Connection reset by peer

I think this is the avatar too big bug, but I'd need to check the log report from that bug.

This explains Gmail/Facebook going down, but not Skype - could you check that one actually connected by leaving the accounts KCM open when you connect and seeing which ones come online/offline.
Comment 6 Robby Engelmann 2011-11-25 21:46:28 UTC
indeed, is seems to be related to the avatar. I just changed it to a smaller png and the reconnects are gone. Originally, I associated it with my latest compilation from sources. But now I remembered that I have change my avatar too.

Thanks for your help.
Comment 7 Martin Klapetek 2011-11-25 21:47:47 UTC
So it is solved then? Btw. this is supposed to be fixed in gabble already, try updating your telepathy-gabble package ;)
Comment 8 David Edmundson 2011-11-25 21:49:52 UTC
I think this is the fixed version, the old gabble crashed.
Comment 9 Robby Engelmann 2011-11-25 21:58:25 UTC
Yes, for me it is fixed :-). If I understood correct it is/was an upstream problem, thus I switched this report to resolved as upstream. feel free to change :-)