Bug 129811 - aim disconnects a few minutes after going online
Summary: aim disconnects a few minutes after going online
Status: RESOLVED DUPLICATE of bug 129366
Alias: None
Product: kopete
Classification: Unmaintained
Component: ICQ and AIM Plugins (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-25 23:08 UTC by baum-im-wald
Modified: 2006-07-12 15:24 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description baum-im-wald 2006-06-25 23:08:22 UTC
Version:           0.12.0 (using KDE 3.5.3, Kubuntu Package 4:3.5.3-0ubuntu0.1 dapper)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15-23-386

A few minutes after logging in to my AIM account, Kopete 0.12 disconnects from it showing a passive popup saying some like "Account xy disconnected". This does not happen with my ICQ account. Problem started after running 0.12 for about a month or so.
I tested the account in question with Gaim and Kopete 0.11 and it worked fine.

Command line output:

kopete (oscar - raw protocol): [void KNetworkByteStream::slotError(int)] Socket error 14
kopete (oscar - raw protocol): [void KNetworkConnector::slotError(int)] Error detected: 14
kopete (oscar - raw protocol): [void ClientStream::cr_error()]
kopete (oscar - raw protocol): [virtual void KNetworkConnector::done()]
kopete (oscar): [void OscarAccount::logOff(Kopete::Account::DisconnectReason)] accountId='##MY_ACCOUNT##'
kopete (oscar - raw protocol): [void ConnectionHandler::clear()] Clearing all connections
kopete (oscar - raw protocol): [void SSIManager::clear()] Clearing the SSI list
kopete: [void KopeteWindow::slotAccountStatusIconChanged(Kopete::Contact*)] [variant:  toString=]
kopete: [void KopeteWindow::slotAccountStatusIconChanged(Kopete::Contact*)] [variant:  toString=]
kopete: [void KopeteWindow::slotAccountStatusIconChanged(Kopete::Contact*)] [variant:  toString=]
kopete (oscar/aim): [virtual void AIMAccount::disconnected(Kopete::Account::DisconnectReason)] Attempting to set status offline
kopete: [void KopeteWindow::slotAccountStatusIconChanged(Kopete::Contact*)] [variant:  toString=]
kopete (oscar - raw protocol): [void ConnectionHandler::remove(Connection*)] Removing connection 0x850cc58
kopete (oscar - raw protocol): [void KNetworkByteStream::slotConnectionClosed()] Socket has been closed.
kopete (oscar - raw protocol): ..by ourselves!
kopete (oscar - raw protocol): socket error is Kein Fehler feststellbar
kopete (oscar - raw protocol): [virtual void KNetworkConnector::done()]
kopete (oscar - raw protocol): [virtual void KNetworkConnector::done()]
kopete (oscar - raw protocol): [void KNetworkByteStream::slotConnectionClosed()] Socket has been closed.
kopete (oscar - raw protocol): ..by ourselves!
kopete (oscar - raw protocol): socket error is Kein Fehler feststellbar
kopete (oscar - raw protocol): [virtual void KNetworkConnector::done()]
kopete (oscar - raw protocol): [virtual void KNetworkConnector::done()]
kopete (oscar - raw protocol): [virtual void KNetworkConnector::done()]
libkopete: [virtual void Kopete::Account::reconnect()] account ##MY_ACCOUNT## restoreStatus 50 restoreMessage
kopete (oscar/aim): [virtual void AIMAccount::setOnlineStatus(const Kopete::OnlineStatus&, const QString&)] called with reason =  status = 50
kopete: [void KopeteWindow::slotAccountStatusIconChanged(Kopete::Contact*)] [variant:  toString=]
Comment 1 Frank Roscher 2006-06-26 18:16:39 UTC
This does happen to me with my ICQ account since today - and Gaim indeed seems not to suffer from this problem. Friends of mine using the original client, Trillian or Miranda don't seem to be affected either.
I don't use AIM, so no idea about that.
Comment 2 Andrew Barr 2006-06-26 18:31:49 UTC
This is happening to me on AIM today as well.
Comment 3 Juliano F. Ravasi 2006-06-28 03:42:31 UTC
I started experiencing this same problem last sunday (2006-06-25), on ICQ. After a few minutes connected, kopete disconnects the ICQ protocol. After a few reconnections, I'm banned from the ICQ network for 10 minutes.

Kopete 0.12.0 (Using KDE 3.5.3-0.2.fc5 Red Hat).

By monitoring the network with ethereal, I notice that kopete sends "Keep Alive" messages constantly, and then, exactly 11 seconds after the 3rd or 4th keep alive message, Kopete disconnects by itself. There is no traffic from the server that could be ordering for a disconnection. And it is always, precisely 11s after one of the keep alive messages sent to the server.

What is most strange is that I didn't do any change in either contactlist or kopete preferences when it started happening, and it started happening at the same day on both my desktop and my laptop.

Related: bug 129454

Side question: how do I get this output from kopete? I compiled it with --enable-debug as per instructions found in another bug report, but I still don't get this output.
Comment 4 baum-im-wald 2006-06-28 21:39:13 UTC
After uninstalling my self-built Kopete and replacing it with Kubuntu packages from kde-apps.org the problem persistet for another day and then, suddenly, vanished.

As for your side question: If you refer to the commandline output above, I got it from a self-built Kopete 0.12 without any other configuration options than --prefix.
Comment 5 Frank Roscher 2006-06-29 22:46:47 UTC
Downgraded to 0.11.4 and the problem disappeared - though I'm quite sure I tried this before without success. 0.12.0 worked great for me for a long time anyway... Very strange.
Comment 6 Bartosz Świątek 2006-07-12 15:19:36 UTC
The problem is still there in the ICQ plugin. Can't get rid of it.
Comment 7 Roman Jarosz 2006-07-12 15:24:34 UTC
Please see bug 129366, there is a fix for this, the fix is also in SVN version of Kopete 0.12.

Roman


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