Bug 167684 - Connection problem with Jabber 2.0
Summary: Connection problem with Jabber 2.0
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: kopete
Classification: Unmaintained
Component: Jabber Plugin (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-29 22:01 UTC by dv5a
Modified: 2011-05-16 21:51 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dv5a 2008-07-29 22:01:33 UTC
Version:           0.50.80 (using 4.1.00 (KDE 4.1.0), Kubuntu packages)
Compiler:          gcc
OS:                Linux (i686) release 2.6.24-20-generic

Cannot connect to an internal Jabber server (jabberd 2.0s9) . Error message is displayed:

Connection problem with jabber server <server_name> - Kopete
There was an error in the protocol stream: Malformed stream packet received.
Details: mismatched tag
Comment 1 dv5a 2008-07-29 22:39:48 UTC
After capturing the network traffic it seems the problem is here. Kopete sends several Jabber messages in a long tcp packet that ends with:

<iq type="error" to="user@server/OsMac" id="purple1b433a37" >
<query xmlns="jabber:iq:last"/>
<error type="cancel" >
<feature-not-implemented xmlns="u

Then a single TCP packet with:

trn:ietf:para

And server responds:

<stream:error xmlns:stream='http://etherx.jabber.org/streams'><xml-not-well-formed xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text xmlns='urn:ietf:params:xml:ns:xmpp-streams'>mismatched tag</text></stream:error>
Comment 2 Roman Šmakal 2008-09-15 09:52:53 UTC
I can confirm this problem - kopete connects to server and then disconnect with this message...
Comment 3 Ben Aceler 2008-11-06 15:01:01 UTC
Same here. Server - Jabber.ru, for livejournal.com kopete works fine. I can even connect to server using invisible mode, than go to visible, but this is a workaround only.

Any tcpdump needed?
Comment 4 Juuso Alasuutari 2009-07-31 15:14:31 UTC
I suspect that I ran into this bug while trying to connect to our internal ejabberd server (version 2.0.3) using Kopete 4.2.4 from PPA packages for Kubuntu 9.04.

Connecting and chatting works fine with Pidgin 2.5.5. However, this is what the ejabberd logs show when I try to connect from Kopete using the exact same settings ('jabber.example.net' is a made-up pseudonym for our Jabber server located at 10.0.0.10):


=INFO REPORT==== 2009-07-31 15:43:22 ===
I(<0.264.0>:ejabberd_listener:116) : (#Port<0.3454>) Accepted connection {{10,0,0,200},58031} -> {{10,0,0,10},5222}

=INFO REPORT==== 2009-07-31 15:43:22 ===
D(<0.1732.0>:ejabberd_receiver:306) : Received XML on stream = [128,116,1,3,1,
                                                                0,75,0,0,0,32,
                                                                0,0,57,0,0,56,
                                                                0,0,53,0,0,22,
                                                                0,0,19,0,0,10,
                                                                7,0,192,0,0,
                                                                51,0,0,50,0,0,
                                                                47,3,0,128,0,
                                                                0,5,0,0,4,1,0,
                                                                128,0,0,21,0,
                                                                0,18,0,0,9,6,
                                                                0,64,0,0,20,0,
                                                                0,17,0,0,8,0,
                                                                0,6,4,0,128,0,
                                                                0,3,2,0,128,
                                                                77,60,103,160,
                                                                115,172,19,
                                                                212,133,38,31,
                                                                50,174,221,52,
                                                                177,83,247,
                                                                242,72,139,44,
                                                                2,157,94,149,
                                                                99,219,187,
                                                                129,89,43]

=INFO REPORT==== 2009-07-31 15:43:22 ===
D(<0.1733.0>:ejabberd_c2s:1346) : Send XML on stream = "<?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='none' from='jabber.example.net' version='1.0'><stream:error><xml-not-well-formed xmlns='urn:ietf:params:xml:ns:xmpp-streams'/></stream:error></stream:stream>"


The server is configured to force STARTTLS.
Comment 5 Lamarque V. Souza 2011-05-16 21:51:03 UTC
Is this still happening?