OS: Opensuse 12.3
KDE: 4.10.3 "release 1"
Kopete: 1.4.3

Problem: Form time to time at least ICQ get disconnected. I tried running kopete from cli and the error at the disconnect moment was like:

Code: Select all

kopete(1937) Kopete::SocketTimeoutWatcher::ackTimeoutCheck: Connection timeout for   QHostAddress( "205.188.11.53" ) 

The problem is that it's not reconnected after get disconnected. So it happens my ICQ is offline for several hours till I note I'm offline.

I have 2 ICQ accounts simultaneously, but I don't think it's a problem.

Whay isn't kopete tring to reconnect? Is there any special option or plugin? Can a kopete instance be forced to reconnect from command line?

Thanks in advance.

I'm not sure why it is not automatically reconnecting. Is your global status set to Online? Also - do both accounts get disconnected at the same time, or just one of the two?

bcooksley wrote:I'm not sure why it is not automatically reconnecting. Is your global status set to Online?

Yes, global is Online. But even if it wasn't set globaly, why wouldn't reconnect a single IM set to online?

bcooksley wrote: Also - do both accounts get disconnected at the same time, or just one of the two?

They disconnect independently mostly.

Is there any way to get some additional debug information?

For debugging information, you can start Kopete in Konsole, which should cause it to output there. You should also enable all debugging areas using "kdebugdialog".

bcooksley wrote:For debugging information, you can start Kopete in Konsole, which should cause it to output there. You should also enable all debugging areas using "kdebugdialog".

I run it in the Konsole and had provided the output before.
In `kdebugdialog` all items with name kopete are enabled anyway.

May this be because of some outdated settings in the kopete profile? Maybe it's worth to remove it and readd all accouts to kopete? But I don't want to lose my chat history,

Any ideas?

Was there any other output after the timeout occurred, such as further timeouts indicating that it couldn't reconnect?
I'm not sure if this is being caused by any profile specific options though - no need to re-add your accounts at the moment.

bcooksley wrote:Was there any other output after the timeout occurred, such as further timeouts indicating that it couldn't reconnect?

I don't think there have been any other output. Need to check. This will take several hource since I have to wait for the disconnect. I don't know how to reproduce it manually.
I've forgotten to say, that when disconnected it shows a nice KDE message window 'Unknown error'.

I've rebooted my ADSL modem to have an internet loss. All IM's except GTalks don't try to autoreconnect though internet is back.

Here is the output which I have now:

Startin from Konsole:

Code: Select all

gruz@gruz:/mnt/sda2/home/gruz> kopete
Fontconfig warning: "/etc/fonts/conf.d/56-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
kopete(31035)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know "/mnt/sda2/home/gruz/.kde4/share/apps/kabc"
gruz@gruz:/mnt/sda2/home/gruz> kopete(31035)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "" '!
kopete(31035)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "" '!
Unknown signature value:  7
Unknown signature value:  7
Unknown signature value:  795
Unknown signature value:  7
Unknown signature value:  7
Unknown signature value:  795                                                                                                                               
unexpected version response
Transfer ACCEPTED by: LoginTask
Transfer ACCEPTED by: LoginTask
kopete(31035) OscarStatusManager::onlineStatusOf: Kopete::OnlineStatus doesn't exists for internal status  278  Using basic status for type  6

kopete(31035) OscarStatusManager::onlineStatusOf: Kopete::OnlineStatus doesn't exists for internal status  278  Using basic status for type  6

CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
kopete(31035)/libkopete Kopete::Account::addContact: You are not allowed to add yourself to the contact list. The addition of "gruz_ua" to account "gruz_ua" will not take place.
Transfer ACCEPTED by: ListTask
Transfer ACCEPTED by: StatusNotifierTask
Transfer ACCEPTED by: LoginTask
Transfer ACCEPTED by: MailNotifierTask
Transfer ACCEPTED by: StatusNotifierTask
Transfer ACCEPTED by: StatusNotifierTask


Killining internet connection:

Code: Select all

CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
kopete(31035) Kopete::SocketTimeoutWatcher::ackTimeoutCheck: Connection timeout for   QHostAddress( "173.194.70.125" ) 
Unknown signature value:  7
Unknown signature value:  7
Unknown signature value:  795
kopete(31035) Kopete::SocketTimeoutWatcher::ackTimeoutCheck: Connection timeout for   QHostAddress( "205.188.11.48" ) 
kopete(31035) Kopete::SocketTimeoutWatcher::ackTimeoutCheck: Connection timeout for   QHostAddress( "64.12.104.72" ) 
Unknown signature value:  7
Unknown signature value:  7
Unknown signature value:  795
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
kopete(31035) Kopete::SocketTimeoutWatcher::ackTimeoutCheck: Connection timeout for   QHostAddress( "205.188.17.129" ) 
Unknown signature value:  7
Unknown signature value:  7
Unknown signature value:  795
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
kopete(31035) Kopete::SocketTimeoutWatcher::ackTimeoutCheck: Connection timeout for   QHostAddress( "205.188.11.53" ) 
kopete(31035) Kopete::SocketTimeoutWatcher::ackTimeoutCheck: Connection timeout for   QHostAddress( "208.68.163.220" ) 
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
CLIENT: LoginTask: Task::done()
CLIENT: LoginTask: emitting finished
CLIENT: ListTask: Task::done()
CLIENT: ListTask: emitting finished
CLIENT: StatusNotifierTask: Task::done()
CLIENT: StatusNotifierTask: emitting finished
CLIENT: MailNotifierTask: Task::done()
CLIENT: MailNotifierTask: emitting finished
CLIENT: MessageReceiverTask: Task::done()
CLIENT: MessageReceiverTask: emitting finished
CLIENT: PictureNotifierTask: Task::done()
CLIENT: PictureNotifierTask: emitting finished
CLIENT: WebcamTask: Task::done()
CLIENT: WebcamTask: emitting finished
CLIENT: ConferenceTask: Task::done()
CLIENT: ConferenceTask: emitting finished
CLIENT: YABTask: Task::done()
CLIENT: YABTask: emitting finished
CLIENT: FileTransferNotifierTask: Task::done()
CLIENT: FileTransferNotifierTask: emitting finished
CLIENT: YahooChatTask: Task::done()
CLIENT: YahooChatTask: emitting finished


Internet is back:

Code: Select all

Unknown signature value:  7
Unknown signature value:  7
Unknown signature value:  795
unexpected version response
QProcess::start: Process is already running


Here I make kopete go online manually

Code: Select all

Transfer ACCEPTED by: LoginTask
Transfer ACCEPTED by: LoginTask
kopete(31035) OscarStatusManager::onlineStatusOf: Kopete::OnlineStatus doesn't exists for internal status  278  Using basic status for type  6

kopete(31035) OscarStatusManager::onlineStatusOf: Kopete::OnlineStatus doesn't exists for internal status  278  Using basic status for type  6

CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
kopete(31035)/libkopete Kopete::Account::addContact: You are not allowed to add yourself to the contact list. The addition of "gruz_ua" to account "gruz_ua" will not take place.
Transfer ACCEPTED by: ListTask
Transfer ACCEPTED by: StatusNotifierTask
Transfer ACCEPTED by: LoginTask
Transfer ACCEPTED by: StatusNotifierTask
Transfer ACCEPTED by: MailNotifierTask
Transfer ACCEPTED by: StatusNotifierTask
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
Transfer ACCEPTED by: StatusNotifierTask
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished


Okay, it would appear that the ICQ backend for Kopete has a bug - which leads to it not reconnecting. You could try reporting this at bugs.kde.org and wait for the developer(s) to fix it, or you could possibly try KDE Telepathy - which may not be affected by the same issue if it supports ICQ.

bcooksley wrote:Okay, it would appear that the ICQ backend for Kopete has a bug - which leads to it not reconnecting. You could try reporting this at bugs.kde.org and wait for the developer(s) to fix it, or you could possibly try KDE Telepathy - which may not be affected by the same issue if it supports ICQ.

It's already a confirmed bug https://bugs.kde.org/show_bug.cgi?id=301121
Posted a year ago and seems no activity.

I tried telepathy. There seems no way to open an incoming message from keyboard like it's possible in kopete. It's a killing feature for me alas.

Thanks for your efforts to help.

The KDE Telepathy developers are significantly more active than the Kopete developers - so you might want to request the keyboard opening functionality. They have a forum on this site which would probably be a good place to ask, to see what they think.

For those, who may meet the same proble, with Kopete and ICQ.
Now I still use Kopete, but use ICQ as a jabber transport, not like a Kopete account!
Here is some Documentation: http://userbase.kde.org/Kopete/Jabber_Transport
Thus I don't meet the connection problem.