Version: 0.50.80 (using Devel) Installed from: Compiled sources Compiler: gcc 4.3 OS: Linux After configuring Kopete from KDE 4.1 Beta1 from scratch and connecting with a new Jabber account in the company intranet, there are some of the about 100 contacts occuring as online and after 1 or 2 seconds I get a messagebox: There was an error in the protocol stream: Malformed stream package received In some cases Kopete crashes with the backtrace below, in some cases it switches back offline. The 3rd attempt to connect was successful and all goes fine. I found this problem already in the bug tracker, but is was marked as resolved there a long time ago. It seems like this is not reliably resolved. Thanks for Your hard work, R. ---------- Backtrace: Application: Kopete (kopete), signal SIGSEGV [?1034h[Thread debugging using libthread_db enabled] [New Thread 0xb5ba36d0 (LWP 4489)] [New Thread 0xb31c1b90 (LWP 4504)] [KCrash handler] #5 0xb37294e1 in XMPP::Client::streamReadyRead () from /usr/lib/libiris_kopete.so.1 #6 0xb36d58fe in XMPP::Client::qt_metacall () from /usr/lib/libiris_kopete.so.1 #7 0xb6f5d45a in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #8 0xb6f5d9d2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #9 0xb36d1167 in XMPP::Stream::readyRead () from /usr/lib/libiris_kopete.so.1 #10 0xb371274d in XMPP::ClientStream::doReadyRead () from /usr/lib/libiris_kopete.so.1 #11 0xb36d5526 in XMPP::ClientStream::qt_metacall () from /usr/lib/libiris_kopete.so.1 #12 0xb6f5d45a in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #13 0xb6f5d9d2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #14 0xb6f645a7 in ?? () from /usr/lib/libQtCore.so.4 #15 0xb6f646cc in ?? () from /usr/lib/libQtCore.so.4 #16 0xb6f59d7f in QObject::event () from /usr/lib/libQtCore.so.4 #17 0xb644aecc in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #18 0xb645131e in QApplication::notify () from /usr/lib/libQtGui.so.4 #19 0xb756427d in KApplication::notify () from /usr/lib/libkdeui.so.5 #20 0xb6f4bbc1 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #21 0xb6f741e1 in ?? () from /usr/lib/libQtCore.so.4 #22 0xb6f7445b in QEventDispatcherUNIX::processEvents () from /usr/lib/libQtCore.so.4 #23 0xb64d50a2 in ?? () from /usr/lib/libQtGui.so.4 #24 0xb6f4a33a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #25 0xb6f4a4fa in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #26 0xb6f4c6dd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #27 0xb644ad47 in QApplication::exec () from /usr/lib/libQtGui.so.4 #28 0x08088aff in main () #0 0xffffe430 in __kernel_vsyscall ()
Help->About: --- Kopete Version 0.50.80 Using KDE 4.00.81 (KDE 4.0.81 >= 20080527) "release 6.4" --- RPM package: kde4-kopete-4.0.81-4.2 (but the old version number is shown by Kopete in Help->About, for whatever reason, because in the RPM changelog appears as the most recent entries: --- * Thu Jun 05 2008 wstephenson@suse.de - Hint that filesharing support enhances dolphin (bnc#396242) * Tue Jun 03 2008 dmueller@suse.de - update to 4.0.81 ---
regarding the version number: we forgot to update it. Can you tell us what server software your company is using on their jabber server?
Of course, here you are: jabberd-2.0s11 BTW: May be you can't do so much here. Yesterday I gathered a similar problem while connecting to the same server using Psi (psi-0.11.99.1-22.1). There seems to be a problem with initially loading the quite large number of contacts I use (about 120). Anyway, maybe you can at least avoid the crash with the above backtrace(?)
I can confirm this bug too - Kopete shows "Malformed packet..." message and sometimes goes offline, sometimes hangs. I can send you whole log privately (don't want to show my contacts to public). --log-- kopete(30339)/kopete (jabber) JabberCapabilitiesManager::discoRequestFinished: "Disco response from doesnotdependon@jabber.cz/Home, node=http://pidgin.im/caps#avatardata, success=1" kopete(30339)/kopete (jabber) JabberCapabilitiesManager::discoRequestFinished: notify affected jids kopete(30339)/kopete (jabber) JabberByteStream::slotReadyRead: called: available: 1225 kopete(30339)/kopete (jabber - raw protocol) JabberAccount::slotClientDebugMessage: "XML IN: <stream:error> <xml-not-well-formed xmlns="urn:ietf:params:xml:ns:xmpp-streams"/> </stream:error> " kopete(30339)/kopete (jabber) JabberByteStream::close: Closing stream. QObject: Do not delete object, 'unnamed', during its event handler! kopete(30339)/kopete (jabber) JabberByteStream::slotConnectionClosed: Socket has been closed. kopete(30339)/kopete (jabber) JabberByteStream::close: Closing stream. kopete(30339)/kopete (jabber - raw protocol) JabberAccount::slotClientDebugMessage: "Client stream error." kopete(30339)/kopete (jabber) JabberAccount::slotCSError: Error in stream signalled. kopete(30339)/kopete (jabber) JabberAccount::slotCSError: Disconnecting.
I confirm this bug, too. I have been unable to connect to my accounts on jabber.fr and jabber.org since KDE 4.1. I'm using KDE 4.1.2 now and it still does it. Sometimes, this even makes Kopete crash.
Can confirm it with this version: Kopete Version 0.60.3 Unter KDE 4.1.3 (KDE 4.1.3)Kopete
Seems to be fixed in 4.1.96 (KDE 4.2 RC) - it's working flawlessly for me now. It's not change on server side - with older Kopete it is still buggy.
Closing, should be fixed since KDE 4.2