pidgin disconnects one of my ICQ numbers constantly

[kdizz]

Binary package hint: pidgin

I have 2 ICQ numbers, and one of them always disconnects and is 'connection reset by peer' error'd. When I boot into windows they both work fine, and this error just popped up out of nowhere a few weeks ago.. i didnt change any settings or alter the pword and so forth. If anyone else can offer suggestions or point me in the right direction to ppl with a similar problem that'd be great.

I'm on Ubuntu 8.04.1
Pidgin 2.4.1

ProblemType: Bug
Architecture: amd64
Date: Wed Jun 11 02:24:27 2008
DistroRelease: Ubuntu 8.04.1
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: fglrx
Package: pidgin 1:2.4.1-1ubuntu2
PackageArchitecture: amd64
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pidgin
Uname: Linux 2.6.24-19-generic x86_64

[persi (xander-stepanov)]

Same problem here, only that I have just 1 UIN. By always I mean every 1-3 minutes.
Here is log: http://pidgin.im/nopaste/456
This description looks similar: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/216616
There was also a similar bug in pidgin base that was "resolved" with version 2.4.2, which I`m using.

[kolen (incredible-angst)]

I think, it happens when libpurple tries to change status or set idle time.

[Venkatraman.S (blizzardz)]

Can you look at Bug #244591 and check whether the problem persists after the change.

[kolen (incredible-angst)]

> Can you look at Bug #244591 and check whether the problem persists after the change.
Problem persists after updating to 2.4.3.

[kolen (incredible-angst)]

I found out that this problem occurs when using 5190 port, after I switched to 443, disconnects stopped to occur. Maybe, this is problem with network or ICQ server, but other clients I used in this network was not disconnecting.

[persi (xander-stepanov)]

Thanks, port 443 works for me. Though google talk still disconnects, is there a port for it as well?

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.