[Pidgin] #9038: pidgin crashs with jaunty jackalope (was: pidgin crahs with jaunty jackalope)

[Pidgin]

#9038: pidgin crashs with jaunty jackalope
---------------------+------------------------------------------------------
 Reporter:  la_cuba  |        Owner:  lschiere    
     Type:  defect   |       Status:  new         
Milestone:           |    Component:  unclassified
  Version:  2.5.5    |   Resolution:              
 Keywords:           |  
---------------------+------------------------------------------------------
Description changed by la_cuba:

Old description:

> after upgrading system to ubuntu 9.04, pidgin crash when logging in with
> an ssl-encrypted jabber-account.
>

> backtrace:
>

> Starting program: /usr/local/bin/pidgin
> [Thread debugging using libthread_db enabled]
> [New Thread 0xb6f3c750 (LWP 30084)]
> [New Thread 0xb6659b90 (LWP 30087)]
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xb6f3c750 (LWP 30084)]
> 0xb5cbf331 in ?? () from /usr/lib/libnss3.so
> (gdb) bt full
> #0  0xb5cbf331 in ?? () from /usr/lib/libnss3.so
> No symbol table info available.
> #1  0x30b7c81a in ?? ()
> No symbol table info available.
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)

New description:

 after upgrading system to ubuntu 9.04, pidgin crashs when logging in with
 an ssl-encrypted jabber-account.


 backtrace:


 Starting program: /usr/local/bin/pidgin
 [Thread debugging using libthread_db enabled]
 [New Thread 0xb6f3c750 (LWP 30084)]
 [New Thread 0xb6659b90 (LWP 30087)]

 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 0xb6f3c750 (LWP 30084)]
 0xb5cbf331 in ?? () from /usr/lib/libnss3.so
 (gdb) bt full
 #0  0xb5cbf331 in ?? () from /usr/lib/libnss3.so
 No symbol table info available.
 #1  0x30b7c81a in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)

--

-- 
Ticket URL: <http://developer.pidgin.im/ticket/9038#comment:1>
Pidgin <http://pidgin.im>
Pidgin