Comment 2 for bug 664412

Also on lucid, I see something like this on our Ubuntu machines at the Sanger Institute; we have our own local CA, and the keytool invocation in the postinst script which attempts to add the certificate fails. I edited the postinst script to include set -x so that I could get something out of it, and noticed (1) that the init script deletes the temporary output file even if the script fails, which means that you can't see the errors. So, I changed it so that it doesn't delete the tempfile if there are errors, and this then showed me that the following part of the script execution path shows the error being generated:

+ LANG=C
+ LC_ALL=C
+ keytool -importcert -trustcacerts -keystore /etc/ssl/certs/java/cacerts -providerClass sun.security.pkcs11.SunPKCS11 -providerArg '${java.home}/lib/security/nss.cfg' -noprompt -storepass changeit -alias genome_research_ltd_certificate_authority_cert_pem -file /usr/share/ca-certificates/sanger.ac.uk/Genome_Research_Ltd_Certificate_Authority-cert.pem
+ grep -q 'Signature not available' /tmp/fileW2Zx2A
+ echo ' error adding sanger.ac.uk/Genome_Research_Ltd_Certificate_Authority-cert.pem'
  error adding sanger.ac.uk/Genome_Research_Ltd_Certificate_Authority-cert.pem
++ expr 0 + 1
+ errors=1

and the log entry says:

keytool error: java.security.ProviderException: Secmod module already configured

Google doesn't have much to say about this particular error. This is causing us serious issues, since it's causing dpkg and aptitude to fall over on most machines, perpetually trying to run the ca-certificates-java postinst script.