XMPP, Server does not use any supported authentication method

Paul Aurich darkrain42 at pidgin.im
Sat Sep 3 00:19:09 EDT 2011

And Alexander Ustinov spoke on 09/01/2011 12:26 PM, saying:
>> I'm not sure ... do you have a libplain.so.* file in libsasl2-modules?
>> (dpkg -L libsasl2-modules | grep plain)
>> If so, then I don't know why this is failing, someone who knows more
>> about XMPP than I will have to look at it.  We support SASL PLAIN
>> internally, and if we're built against Cyrus SASL then libplain should
>> provide it there.  I don't see why your Pidgin wouldn't find an auth
>> method in that case.

If libpurple is built with Cyrus SASL support, libpurple just uses that
wholesale, and don't use any of the built-in code (which is something I
keep meaning to fix).

I'm not sure what's going on here, though.  Something in Cyrus is returning

>> Ethan
> Yes, libplain.so is there. Thank you for your time.

Could you get a debug log of Pidgin starting up?  Disable all accounts, and
then quit Pidgin.  From the command line, run:

	pidgin -d > ~/pidgin.log

After it starts up, go ahead and enable one of your XMPP accounts, and then
quit Pidgin, and attach that debug log.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://pidgin.im/pipermail/support/attachments/20110902/833f9dea/attachment.sig>

More information about the Support mailing list