Public bug reported:
Binary package hint: pidgin
Recently upgraded to Gutsy from Feisty. Under Feisty with Pidgin
(installed from a different repo since it wasn't part of Feisty) all my
accounts (AIM, Google and XMPP server at work) could connect. After the
upgrade, using pidgin 2.2.1 from Gutsy repo AIM and Google can connect
but connection to XMPP server at work fails. Using Pidgin under windows
I can successfully connect to the work XMPP server.
Here are the related packages installed on my system:
$ dpkg -l | egrep "purple|pidgin|sasl"
ii libpurple0 1:2.2.1-1ubuntu4.1
multi-protocol instant messaging library
ii libsasl2-2 2.1.22.dfsg1-9ubuntu2
Authentication abstraction library
ii libsasl2-modules 2.1.22.dfsg1-9ubuntu2
Pluggable Authentication Modules for SASL
ii pidgin 1:2.2.1-1ubuntu4.1
graphical multi-protocol instant messaging cii pidgin-data
1:2.2.1-1ubuntu4.1 multi-protocol instant
messaging client - daii pidgin-rhythmbox 2.0-1
Pidgin Rhythmbox Plugin
Here is the output from the debug window when attempting to connect to
work XMPP server:
(15:54:12) jabber: jabber_actions: have pep: NO
(15:54:12) account: Connecting to account [EMAIL PROTECTED]/Work
(15:54:12) connection: Connecting. gc = 0x86027c8
(15:54:12) dnssrv: querying SRV record for _xmpp-client._tcp.XXX.XXX.XXX.com
(15:54:12) dnssrv: found 0 SRV entries
(15:54:12) dns: DNS query for 'XXX.XXX.XXX.com' queued
(15:54:12) dns: Created new DNS child 15340, there are now 1 children.
(15:54:12) dns: Successfully sent DNS request to child 15340
(15:54:12) dns: Got response for 'XXX.XXX.XXX.com'
(15:54:12) dnsquery: IP resolved for XXX.XXX.XXX.com
(15:54:12) proxy: Attempting connection to XXX.XXX.XXX.XXX
(15:54:12) proxy: Connecting to XXX.XXX.XXX.com:5222 with no proxy
(15:54:12) proxy: Connection in progress
(15:54:12) proxy: Connected to XXX.XXX.XXX.com:5222.
(15:54:12) jabber: Sending: <?xml version='1.0' ?>
(15:54:12) jabber: Sending: <stream:stream to='XXX.XXX.X.com'
xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'
version='1.0'>
(15:54:12) jabber: Recv (454): <?xml version='1.0'
encoding='UTF-8'?><stream:stream
xmlns:stream="http://etherx.jabber.org/streams"; xmlns="jabber:client"
from="XXX.XXX.com" id="85a4f392" xml:lang="en"
version="1.0"><stream:features><starttls
xmlns="urn:ietf:params:xml:ns:xmpp-tls"><required/></starttls><mechanisms
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>PLAIN</mechanism><mechanism>CRAM-MD5</mechanism><mechanism>DIGEST-MD5</mechanism></mechanisms></stream:features>
(15:54:12) jabber: Sending: <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
(15:54:12) jabber: Recv (50): <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
(15:54:12) jabber: Sending (ssl): <stream:stream to='XXX.XXX.XXX.com'
xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'
version='1.0'>
(15:54:12) jabber: Recv (ssl)(582): <?xml version='1.0'
encoding='UTF-8'?><stream:stream
xmlns:stream="http://etherx.jabber.org/streams"; xmlns="jabber:client"
from="XXX.XXX.com" id="85a4f392" xml:lang="en"
version="1.0"><stream:features><mechanisms
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>PLAIN</mechanism><mechanism>CRAM-MD5</mechanism><mechanism>DIGEST-MD5</mechanism></mechanisms><compression
xmlns="http://jabber.org/features/compress";><method>zlib</method></compression><auth
xmlns="http://jabber.org/features/iq-auth"/><register
xmlns="http://jabber.org/features/iq-register"/></stream:features>
(15:54:12) sasl: Mechs found: PLAIN CRAM-MD5 DIGEST-MD5
(15:54:12) jabber: Sending (ssl): <auth
xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='DIGEST-MD5'/>
(15:54:12) jabber: Recv (ssl)(228): <challenge
xmlns="urn:ietf:params:xml:ns:xmpp-sasl">cmVhbG09InRvb2xzLmNvbnZpby5jb20iLG5vbmNlPSJpRWZVVzV0cm84UVZXenJLeENjS2ZPb3dvbEpWaTlEcXFKbnlCdXNGIixxb3A9ImF1dGgiLGNoYXJzZXQ9InV0Zi04IixhbGdvcml0aG09Im1kNS1zZXNzIg==</challenge>
(15:54:12) sasl: DIGEST-MD5 client step 2
(15:54:12) jabber: Sending (ssl): <response
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>dXNlcm5hbWU9Impib2RuYXIiLHJlYWxtPSJ0b29scy5jb252aW8uY29tIixub25jZT0iaUVmVVc1dHJvOFFWV3pyS3hDY0tmT293b2xKVmk5RHFxSm55QnVzRiIsY25vbmNlPSIwM0hXNnhnSlh0eVJUdGtDaHdsWlpFM3BucmtORzVWYVBVbDhQcmtMR1M4PSIsbmM9MDAwMDAwMDEscW9wPWF1dGgsZGlnZXN0LXVyaT0ieG1wcC9jaGF0LmNvcnAuY29udmlvLmNvbSIscmVzcG9uc2U9Zjk3ZjdiNmEzMzQ5NzQxNGVlN2M2MzI4YmZjYzc3NTA=</response>
(15:54:12) jabber: Recv (ssl)(77): <failure
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><not-authorized/></failure>
(15:54:12) jabber: jabber_actions: have pep: NO
(15:54:12) account: Disconnecting account 0x819b128
(15:54:12) connection: Disconnecting connection 0x86027c8
(15:54:12) jabber: jabber_actions: have pep: NO
(15:54:12) connection: Destroying connection 0x86027c8
** Affects: pidgin (Ubuntu)
Importance: Undecided
Status: New
--
pidgin 2.2.1 cannot connect to certain XMPP servers
https://bugs.launchpad.net/bugs/174248
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
