Bug 161054

Summary:	Jabber accounts constantly disconnect/reconnect
Product:	[Unmaintained] kopete	Reporter:	Adam Porter <adam>
Component:	Jabber Plugin	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	hhielscher, matt.wilks
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Adam Porter 2008-04-20 03:59:54 UTC

Version:            (using KDE 3.5.9)
Installed from:    Ubuntu Packages
OS:                Linux

https://bugs.launchpad.net/ubuntu/+source/kopete/+bug/219768

I have three Jabber accounts in Kopete, one on a dreamhost.com account and two on Gmail/GTalk. All three are constantly disconnecting and reconnecting; they don't stay connected for more than 30-60 seconds. They continuously disconnect/reconnect in sequence; first Account 1, then Account 2, then Account 3, then starting from Account 1 again. This would seem to indicate that it's a problem with the protocol support in Kopete, not a server problem, since they are spread over two different servers. There must be some kind of timeout error, since it happens after the same amount of time, and in the same order.

I also have YIM, MSN, ICQ, and AIM accounts in Kopete, and none of them are having this problem, only the Jabber accounts.

kopete:
  Installed: 4:3.5.9-0ubuntu1
  Candidate: 4:3.5.9-0ubuntu1
  Version table:
 *** 4:3.5.9-0ubuntu1 0
        500 http://us.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

Comment 1 Bram Schoenmakers 2008-04-20 09:49:08 UTC

Can you provide us console output while this happens?

Comment 2 Adam Porter 2008-04-21 10:39:57 UTC

I restarted Kopete from the console but there was no output when it
disconnected and reconnected other than saying it was going to
reconnect.  If it happens again I will save the output and send it
here, even if it seems useless.

On Sun, Apr 20, 2008 at 2:49 AM, Bram Schoenmakers
<bramschoenmakers@kde.nl> wrote:
[bugs.kde.org quoted mail]

Comment 3 Adam Porter 2008-04-23 07:11:59 UTC

Here is some output.  I don't know if it's from the disconnecting/reconnecting or from other stuff, but it is happening now.

QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished

Comment 4 Helge Hielscher 2008-11-19 10:12:04 UTC

I have the problem as well with Kopete 0.12.7 using KDE 3.5.10:

kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML IN: <iq from="phielscher@gmail.com" type="error" id="aadea" to="hhielscher@gmail.com/Kopete" >
<query xmlns="jabber:iq:last"/>
<error type="cancel" code="503" >
<service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
</error>
</iq>
kopete (jabber - raw protocol):
kopete (msn - raw protocol): [void MSNSocket::slotDataReceived()] CHG 6 NLN 1073741860
kopete: [void KopeteWindow::slotAccountStatusIconChanged(Kopete::Contact*)] [variant:  toString=]
kopete (jabber): [void JabberContact::slotGetTimedLastActivity()] Requesting last activity from timer for linda-paola@gmx.de
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML OUT: <iq type="get" to="linda-paola@gmx.de" id="aadfa" >
<query xmlns="jabber:iq:last"/>
</iq>
kopete (jabber - raw protocol):
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML IN: <iq from="linda-paola@gmx.de" type="error" id="aadfa" to="hhielscher@gmail.com/Kopete" >
<query xmlns="jabber:iq:last"/>
<error type="cancel" code="503" >
<service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
</error>
</iq>
kopete (jabber - raw protocol):
kopete (jabber): [void JabberResource::slotGetTimedClientVersion()] Requesting client version for dtt@jabber.org/Office
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML OUT: <iq type="get" to="dtt@jabber.org/Office" id="aae0a" >
<query xmlns="jabber:iq:version"/>
</iq>
kopete (jabber - raw protocol):
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML IN: <iq from="dtt@jabber.org/Office" type="result" id="aae0a" to="hhielscher@gmail.com/Kopete" >
<query xmlns="jabber:iq:version">
<name>Pidgin</name>
<version>2.5.2 (libpurple 2.5.2)</version>
</query>
</iq>
kopete (jabber - raw protocol):
kopete (jabber): [void JabberResourcePool::slotResourceUpdated(JabberResource*)] Updating capabilities for JID: dtt@jabber.org/Office
kopete (jabber): [void JabberResource::slotGetTimedClientVersion()] Requesting client version for hhielscher@gmx.de/Kopete
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML OUT: <iq type="get" to="hhielscher@gmx.de/Kopete" id="aae1a" >
<query xmlns="jabber:iq:version"/>
</iq>
kopete (jabber - raw protocol):
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML IN: <iq from="hhielscher@gmail.com/Kopete" type="get" id="aae1a" to="hhielscher@gmx.de/Kopete" >
<query xmlns="jabber:iq:version"/>
</iq>
kopete (jabber - raw protocol):
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML OUT: <iq type="result" to="hhielscher@gmail.com/Kopete" id="aae1a" >
<query xmlns="jabber:iq:version">
<name>Kopete</name>
<version>0.12.7</version>
<os>Linux 2.6.27.4-tmb-desktop-2mdv</os>
</query>
</iq>
kopete (jabber - raw protocol):
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML IN: <iq from="hhielscher@gmx.de/Kopete" type="result" id="aae1a" to="hhielscher@gmail.com/Kopete" >
<query xmlns="jabber:iq:version">
<name>Kopete</name>
<version>0.12.7</version>
<os>Linux 2.6.27.4-tmb-desktop-2mdv</os>
</query>
</iq>
kopete (jabber - raw protocol):
kopete (jabber): [void JabberResourcePool::slotResourceUpdated(JabberResource*)] Updating capabilities for JID: hhielscher@gmx.de/Kopete
kopete (jabber): [void JabberResource::slotGetTimedClientVersion()] Requesting client version for testerus@googlemail.com/Kopete
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML OUT: <iq type="get" to="testerus@googlemail.com/Kopete" id="aae2a" >
<query xmlns="jabber:iq:version"/>
</iq>
kopete (jabber - raw protocol):
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML IN: <iq from="hhielscher@gmail.com/Kopete" type="get" id="aae2a" to="testerus@googlemail.com/Kopete" >
<query xmlns="jabber:iq:version"/>
</iq>
kopete (jabber - raw protocol):
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML OUT: <iq type="result" to="hhielscher@gmail.com/Kopete" id="aae2a" >
<query xmlns="jabber:iq:version">
<name>Kopete</name>
<version>0.12.7</version>
<os>Linux 2.6.27.4-tmb-desktop-2mdv</os>
</query>
</iq>
kopete (jabber - raw protocol):
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML IN: <iq from="testerus@googlemail.com/Kopete" type="result" id="aae2a" to="hhielscher@gmail.com/Kopete" >
<query xmlns="jabber:iq:version">

Comment 5 Matt Wilks 2010-01-05 20:27:38 UTC

I'm seeing this issue with kopete version 4:4.3.2-0ubuntu4 on Kubuntu Karmic 9.10.  Intermittent disconnects from the Jabber server.  Running kopete from the console only gives me: "Unknown signature value:  0" messages.

Comment 6 Roman Jarosz 2010-01-17 16:01:43 UTC

Please update to newer version as we don't have manpower to support Kopete in
KDE 3.

Matt please create new bug report and if the server which disconnects you is public please add the server url to bug report too. It could also be unstable Internet connection if so you should see timeout error in console.