Bug 223000

Summary:	does not connect to icq anymore (2010-01-16)
Product:	[Unmaintained] kopete	Reporter:	arne anka <kde-bugs>
Component:	general	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	languitar, lorenzph
Priority:	NOR
Version First Reported In:	0.80.2
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description arne anka 2010-01-16 17:43:08 UTC

Version:           0.80.2 (using 4.3.4 (KDE 4.3.4), Debian packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.32.3

since today, kopete doesn't connect to icq anymore.
it tries, but always ends up with "unknown error", no further info seems to be logged anymore.
has icq.com again tampered with their servers?


additionally, it seems to cancel all connection attempts if using
file->set status
icq fails and jabber does not connect either.
selecting only jabber (from the icon at the bottom), jabber connects w/o any problems.

Comment 1 Roman Jarosz 2010-01-16 17:46:32 UTC

if you start Kopete from console do you see any error there?

Comment 2 Philip Lorenz 2010-01-16 20:21:46 UTC

I have experienced similar problems today. However for me this is caused by a routing failure to login.messaging.aol.com. You might want to try pinging login.messaging.aol.com or performing a traceroute to figure out whether you are experiencing the same issue.

Comment 3 Johannes Wienke 2010-01-16 21:13:26 UTC

These is the full debug log for connecting to icq until it failed:

kopete(16339)/libkopete KopetePasswordRequest::begin:
kopete(16339)/libkopete Kopete::WalletManager::openWalletInner:  about to open wallet async
kopete(16339)/libkopete Kopete::WalletManager::slotWalletChangedStatus:  isOpen:  true
kopete(16339)/libkopete Kopete::WalletManager::slotWalletChangedStatus: Successfully opened the wallet !
kopete(16339)/libkopete KopetePasswordRequest::walletReceived:
kopete(16339)/kopete (oscar/icq) ICQAccount::connectWithPassword: accountId=' "xxx" '
kopete(16339) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, )
kopete(16339)/kopete (oscar/icq) ICQAccount::connectWithPassword: Logging in as  "125520245"
kopete(16339)/kopete (oscar - raw protocol) ConnectionHandler::clear: Clearing all connections
kopete(16339)/kopete (oscar - raw protocol) Client::setStatus: Setting status message to  ""
kopete(16339)/kopete (oscar - raw protocol) Connection::initSequence: d->flapSequence: 1f4c
kopete(16339)/libkopete Kopete::OnlineStatusManager::cacheLookupByObject: Missed  "Verbindungsaufbau .../icq_protocol/#000000/icq_connecting/16/a"  in icon cache!
kopete(16339)/kopete (oscar - raw protocol) ClientStream::socketError:  error:  5
kopete(16339)/kopete (oscar) OscarAccount::logOff: accountId=' "xxx" '
kopete(16339)/kopete (oscar - raw protocol) CloseConnectionTask::onGo: Sending channel 0x04 close packet
kopete(16339)/kopete (oscar - raw protocol) Task::done:
kopete(16339)/kopete (oscar - raw protocol) Task::done: emitting finished
kopete(16339)/kopete (oscar - raw protocol) ConnectionHandler::clear: Clearing all connections
kopete(16339) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, )
kopete(16339)/kopete (oscar/icq) ICQAccount::disconnected: Attempting to set status offline
kopete(16339)/libkopete Kopete::Account::disconnected: 1
kopete(16339)/kopete (oscar - raw protocol) ConnectionHandler::remove: Removing connection  Connection(0x269ceb0, name = "AUTHORIZER")
kopete(16339)/libkopete Kopete::Account::reconnect: account  "xxx"  restoreStatus  50  restoreTitle  ""  restoreMessage  ""
kopete(16339)/kopete (oscar/icq) ICQAccount::connectWithPassword: accountId=' "xxx" '
kopete(16339) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, )
kopete(16339)/kopete (oscar/icq) ICQAccount::connectWithPassword: Logging in as  "xxx"
kopete(16339)/kopete (oscar - raw protocol) ConnectionHandler::clear: Clearing all connections
kopete(16339)/kopete (oscar - raw protocol) Client::setStatus: Setting status message to  ""
kopete(16339)/kopete (oscar - raw protocol) Connection::initSequence: d->flapSequence: 25d5

Comment 4 Roman Jarosz 2010-01-16 23:50:57 UTC

Yeah it could be routing problem because the error is "The socket operation timed out." so IMHO the socket doesn't connect to ICQ server at all ... or if you have proxy enabled you may try to disable it.

Comment 5 arne anka 2010-01-19 14:57:55 UTC

late in the night it started to work again.
additionally, while kopete couldn't connect, the browser client at icq.com (icq2go it is called, i think) didn't connect either.

looks like it was a problem at icq's part.
anyway, the error message could be a tad more verbose.

Comment 6 arne anka 2010-01-19 15:32:50 UTC

and my favourite news ticker says, icq released version 7 today -- thus, any issues with the server sound really familiar ...

Comment 7 Roman Jarosz 2010-01-21 22:30:11 UTC

Most likely ICQ server problem, works now so I'm closing this.