I pulled down what I think is the source for Jaunty (pidgin_2.5.5 plus ubuntu-specific diff patch) and looking at the code, it appears to use the (later) rewritten/reorganized authentication code (yay!)
If you're seeing the same symptoms, my guess is that maybe it's a different root cause this time. If you can capture the issues you're seeing in a new bug against pidgin 2.5.5, maybe that's the best way to pursue a fix. I'm afraid I'm unable to help - we stopped using the Jabber (OS X) server that required the "Force old SSL" switch to be set which subsequently crashed Pidgin. Using "standard" SSL/TLS on our new server is working fine for me. -- stack smashing detected: pidgin terminated https://bugs.launchpad.net/bugs/211507 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
