Feisty: Jabber doesn't work after updating to Feisty

Bug #97265 reported by Lennart Hansen
4
Affects Status Importance Assigned to Milestone
gaim (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gaim

After updating to Feisty my Jabber doesn't work anymore, it worked fine in Edgy, think it was Gaim Beta2.

I'll be happy to supply any information needed to solve this problem.

Here is some info that might be of use.

==============================================================
dns: Got response for 'xxxxx.xxxxxxx.com'
dnsquery: IP resolved for xxxxx.xxxxxxx.com
proxy: Attempting connection to 10.xxx.xxx.xxx
proxy: Connecting to xxxxx.xxxxxxx.com:5222 with no proxy
proxy: Connection in progress
proxy: Connected.
jabber: Sending: <?xml version='1.0' ?>
jabber: Sending: <stream:stream to='amazon.com' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
jabber: Recv (183): <?xml version='1.0' encoding='UTF-8'?><stream:stream xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" from="amazon.com" id="71d798db" xml:lang="en" version="1.0">
jabber: Recv (201): <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></mechanisms></stream:features>
jabber: Sending: <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
jabber: Recv (50): <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
util: Writing file accounts.xml to directory /home/lhansen/.gaim
util: Writing file blist.xml to directory /home/lhansen/.gaim
util: Writing file prefs.xml to directory /home/lhansen/.gaim
nss: Handshake failed -12286
account: Disconnecting account 0x8144068
connection: Disconnecting connection 0x84d1768
connection: Destroying connection 0x84d1768
==============================================================

ProblemType: Bug
Architecture: i386
Date: Wed Mar 28 05:22:59 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gaim
Package: gaim 1:2.0.0+beta6-1ubuntu2
PackageArchitecture: i386
ProcCmdline: gaim -d
ProcCwd: /home/lhansen
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_IE.UTF-8
SourcePackage: gaim
Uname: Linux lhansen-laptop 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

Revision history for this message
Lennart Hansen (lahansen) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug. I don't confirm that, likely an upstream bug, they might know better about it

Changed in gaim:
importance: Undecided → Medium
Revision history for this message
Paul Jaros (madmike77) wrote :

I've got the exact same bug with Pidgin 2.2.1 on Gutsy Gibbon on a Jabber-Server.
This used to work with Pidgin 2.2.0 on Feisty Fawn.

Revision history for this message
Jeff Anderson (jander99) wrote :

Can anyone confirm this bug still exists? If not it may be considered a candidate to be closed.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, do you get the same with pidgin in Intrepid or Jaunty?.

Changed in gaim:
status: New → Incomplete
Revision history for this message
Lennart Hansen (lahansen) wrote : Re: [Bug 97265] Re: Feisty: Jabber doesn't work after updating to Feisty

Not for me, I think you can resolve this bug.

On Fri, Jan 16, 2009 at 6:03 PM, Pedro Villavicencio <email address hidden> wrote:
> Thanks for your report, do you get the same with pidgin in Intrepid or
> Jaunty?.
>
> ** Changed in: gaim (Ubuntu)
> Status: New => Incomplete
>
> --
> Feisty: Jabber doesn't work after updating to Feisty
> https://bugs.launchpad.net/bugs/97265
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Med Venlig Hilsen / Kind Regards

Lennart Hansen

Revision history for this message
Pedro Villavicencio (pedro) wrote :

closing the bug then, thanks.

Changed in gaim:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.