Intrepid upgrade could not install ca-certificates

[Smotsie]

Binary package hint: update-manager

Error reported was "subprocess post-installation script killed by signal (Segmentation fault)"

[Michael Vogt (mvo)]

Thanks for your bugreport.

please attach the files in /var/log/dist-ugprade/* to this bugreport.

[Smotsie (simon-west)]

Hi Michael,

Sorry, but after filing that bug report, things went a lot worse. I was
unable to get Intrepid to run properly on my hardware - X was a complete
nightmare. It started but then locked everything up apart from a moveable
mouse (numlock, ctrl-alt-del didn't work!). There was no panel and
ctrl-alt-1 didn't bring up a command line session. I went through the
"recovery" process, tryingto fix X and various other options, but no dice.
In exasperation I blew away the installation and started from scratch with
an Intrepid Kubuntu CD. That too failed in a similar way, with a panel, but
numlock locked and no real response. Finally I went back to Kubuntu 8.04
KDE4 Remix so I can get on with life. I would be happy to help resolve this,
as in a short while 8.10 will be released and I will be left behind. My PC
is a Dell Optiplex 755 with NVidia GeForce 8400 GS video card.

Cheers

Simon West

On Tue, Oct 7, 2008 at 7:20 AM, Michael Vogt <email address hidden>wrote:

> Thanks for your bugreport.
>
> please attach the files in /var/log/dist-ugprade/* to this bugreport.
>
> ** Changed in: update-manager (Ubuntu)
> Assignee: (unassigned) => Michael Vogt (mvo)
> Status: New => Incomplete
>
> --
> Intrepid upgrade could not install ca-certificates
> https://bugs.launchpad.net/bugs/277477
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "update-manager" source package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: update-manager
>
> Error reported was "subprocess post-installation script killed by signal
> (Segmentation fault)"
>

********************************************************************
This email and any attachments are confidential and meant only for the addressees,
and may be protected by law. If this email has been sent to you in error,
please notify the sender immediately and delete this e-mail from your computer.
emails are not secure and we will not accept liability if this e-mail is accessed
by anyone or modified or amended following dispatch. Any views or opinions in this
email are those of the author and do not represent those of Mirada unless otherwise
specifically stated. Although we has taken every reasonable precaution to ensure that
any attachment to this e-mail has been checked for viruses, we do not accept
liability for any damages.

Mirada is a public limited company,
Registered Number: 03609752
Registered Office: Units 6 & 7 Princes Court, Wapping Lane, London, E1W 2DA.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[chris (info-spuhler)]

I'm getting the same problem. See attached log

[chris (info-spuhler)]

The problem came up another time later in the upgrade process. It crashed the upgrading, I had to continue it from the command line. Log from this attached

[Jean-Baptiste Lallement (jibel)]

@chris, your problem is not the same as the original reporter.
According to the error from your log:
Setting up ca-certificates (20080809) ...

Updating certificates in /etc/ssl/certs....done.

Running hooks in /etc/ca-certificates/update.d....

updating keystore /etc/ssl/certs/java/cacerts...

Unrecognized command: -importcert

Usage: keytool [COMMAND] [-- COMMAND]...

Manage private keys and public certificates.

Yours has to do with ca-certificates but OR's bug is very likely a hardware issue. So I'm closing this report, if you're still experiencing you issue then submit a new report.

Thanks.