| Summary: | Kopete crashes while connecting to Jabber - Malformed stream package received | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | René Krell <renda.krell> |
| Component: | Jabber Plugin | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | anmeldungen, jreznik, raphink, renda.krell |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
René Krell
2008-06-06 11:51:44 UTC
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 |