Exception in thread "main" java.security.ProviderException
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ca-certificates (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
During the update process of ca-certificates I got the following error in the terminal:
Setting up ca-certificates (20110502+
Clearing symlinks in /etc/ssl/
Updating certificates in /etc/ssl/certs... WARNING: Skipping duplicate certificate IGC_A.pem
WARNING: Skipping duplicate certificate IGC_A.pem
WARNING: Skipping duplicate certificate UbuntuOne-
WARNING: Skipping duplicate certificate UbuntuOne-
156 added, 0 removed; done.
Running hooks in /etc/ca-
Exception in thread "main" java.security.
at sun.security.
at sun.security.
at sun.reflect.
at sun.reflect.
at sun.reflect.
at java.lang.
at sun.security.
at sun.security.
at java.security.
at sun.security.
at sun.security.
at sun.security.
at sun.security.
at sun.security.
at java.security.
at java.security.
at sun.security.
at sun.security.
at sun.security.
at sun.security.
at sun.security.
at sun.security.
at sun.security.
at sun.security.
at sun.security.
at sun.security.
at java.security.
at sun.security.
at sun.security.
at java.security.
at UpdateCertifica
at UpdateCertifica
Caused by: java.io.
at sun.security.
at sun.security.
... 31 more
E: /etc/ca-
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: ca-certificates 20110502+
ProcVersionSign
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Wed Sep 21 00:38:18 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ca-certificates
UpgradeStatus: Upgraded to oneiric on 2011-08-30 (20 days ago)
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #855171, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.