This is a known problem; it occurs when you've got another plugin active that also uses libgcrypt. libgcrypt keeps global state, and has no way to gracefully handle being initialized and removed by two separate shared objects. Over on the libgcrypt list, they were talking about how to fix this a little while back.
- Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
