I started experiencing this bug after upgrading my Jabber server (running ejabberd) to Debian wheezy. Someone created an associated bug report which can be found at <http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=654853>.
I also started to experience this bug on a different machine (previously not experiencing it there, even after the server upgrade) after upgrading it to Fedora 19. The Fedora people have fixed this bug (bug report at <https://bugzilla.redhat.com/show_bug.cgi?id=979052>) by explicitly adding a dependency on the cyrus-sasl-scram library (see <http://pkgs.fedoraproject.org/cgit/pidgin.git/commit/?id=a3d3522983ef0633e960dcaefa1973c8667eb2ea>). I can confirm that this fix works for me: the pidgin SASL module will prefer SCRAM-SHA1 over DIGEST-MD5 and pidgin authenticates successfully. While this probably doesn't address the underlying bug (possibly in ejabberd) maybe Ubuntu can also ship the appropriate libraries for SCRAM-SHA1 support in SASL and fix user experience in this way. ** Bug watch added: Debian Bug tracker #654853 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654853 ** Bug watch added: Red Hat Bugzilla #979052 https://bugzilla.redhat.com/show_bug.cgi?id=979052 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993989 Title: can't connect to Jabber account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/993989/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
