This problem occurs when the PKCS#11 module is already configured in Firefox for a different filename, but with the same name as the one we use. Removing it and allowing the add-on to re-add it is, at that point, the correct thing to do.