Bug 107036 - spurious disconnects while using ICQ or AIM
Summary: spurious disconnects while using ICQ or AIM
Status: RESOLVED DUPLICATE of bug 107023
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: 0.10.2
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-08 15:57 UTC by Ken Zalewski
Modified: 2005-06-08 18:51 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ken Zalewski 2005-06-08 15:57:04 UTC
Version:           0.10.2 (using KDE KDE 3.4.1)
Installed from:    Compiled From Sources
Compiler:          gcc 3.3.4 
OS:                Linux

This bug seems to be very similar to bug 89982, but it is different enough to warrant a new report (especially since bug 89982 is marked as "resolved").

While using ICQ and AIM, once in a while (but not as often as was previously occurring before the 89982 fix), my connection to both ICQ and AIM will be suddenly dropped.  I receive two dialog boxes - one for ICQ and one for AIM.  The title bar looks like:

<nickname> Disconnected - Kopete

And the dialog text is:

An unknown error has occurred and the connection has been closed.

This seems to happen when a person in my contact list signs on or off, but it certainly does not happen every time.

In version 0.10.0, this would happen, and I would receive a STACK of dialog boxes, apparently one for each contact.  At least in this version (0.10.2), I get only two dialogs, one for the AIM account and one for the ICQ account.

However, these spurious disconnects do not occur if I use Gaim, or if I use Trillian on Windows.  There must be something that happens that causes Kopete to disconnect me from my ICQ and AIM sessions.

In addition, after this occurs, my ICQ and AIM icons properly go grey.  However, when I click on Set Status -> Online, nothing happens.  I will log a separate bug report for that.
Comment 1 Matt Rogers 2005-06-08 18:51:26 UTC

*** This bug has been marked as a duplicate of 107023 ***