Comment 8 for bug 241602

Same issue, different context and effects with FF 3.6.17 on Kubuntu 10.4, which lead me to plea for this bug to be reopen. No Torbutton installed, FF fails to create the pkcs12 backup file even from a freshly initiated FF profile.

However, a keypair with cert issued by the same CA (ca.freeicp.org basic level) and email (the sender's) was generated and bakced up successfully by SeaMonkey 2.0.11 running in the same system, Furthermore, the intringuing part in the sequel is that the pcks12 file created by Seamonkey could be imported by the same FF, and the corresponding imported keypair could successfuly be (re)exported by FF,

Searching around for possible explanations (unrelated to Torbutton) I ran accross this Debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469079 which was solved by removal of libnss3 and keeping only libnss3-1d. However, my system already had only libnss3-1d installed. Nonetheless, following up the discussion on that bug I noticed that my system has two versions of libusrsoftokn3, of different size and date ?usr/lib/firefox-3.6.17/libsoftokn3.so and /usr/lib/nss/libsoftokn3.so.

Could that duplicity be related with this behaviour, as in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469079?