Bug 129454 - kopete autodisconnect icq after a few minutes.
Summary: kopete autodisconnect icq after a few minutes.
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: ICQ and AIM Plugins (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-19 22:33 UTC by Thomas Lindroth
Modified: 2006-06-28 03:14 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 Thomas Lindroth 2006-06-19 22:33:23 UTC
Version:           0.12.0 (using KDE KDE 3.4.2)
Installed from:    Gentoo Packages
Compiler:          gcc (GCC) 4.1.1 (Gentoo 4.1.1) 
OS:                Linux

Icq gets disconnected about 1 min after it connected. It will try to reconnect and stay online for another min until it gets disconnected again.

It also displays a non invasive popup with the message "<myuin> disconnected"

Here are some log messages when it disconnects:

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='XXXXXXX'
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 (oscar/icq): [virtual void ICQAccount::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 0xb4744590
kopete (oscar - raw protocol): [void KNetworkByteStream::slotConnectionClosed()] Socket has been closed.
kopete (oscar - raw protocol): ..by ourselves!
kopete (oscar - raw protocol): socket error is no error
kopete (oscar - raw protocol): [virtual void KNetworkConnector::done()]
kopete (oscar - raw protocol): [virtual void KNetworkConnector::done()]
kopete (oscar - raw protocol): [virtual void KNetworkConnector::done()]
Comment 1 Thomas Lindroth 2006-06-26 19:41:25 UTC
I upgraded to kopete-0.12.0-r1 (gentoo) and I no longer experience the problem.
Comment 2 Frank Roscher 2006-06-27 12:44:44 UTC
I upgraded as well - but the bug is still there. There doesn't seem to be a relevant patch in r1 anyway, you probably just were lucky.
Comment 3 Juliano F. Ravasi 2006-06-28 03:14:26 UTC
I started experiencing this same problem last sunday (2006-06-25). 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.