Ubuntu
software-properties package

  1. Xenial (16.04)
  2. Bug #1679784
  3. Comment #2

Comment 2 for bug 1679784

Revision history for this message
Steve Langasek (vorlon) wrote : Re: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Crashed on changing from Xorg video driver to NVIDIA driver

The error in your log is:

Processing triggers for shim-signed (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
Running in non-interactive mode, doing nothing.
dpkg: error processing package shim-signed (--configure):
 subprocess installed post-installation script returned error exit status 1

This shows that shim needs to interact with you in order to disable secureboot on your system; this is correct, if you are installing the nvidia modules you need SB disabled so that kernel module signatures are not enforced.

And your DpkgHistoryLog.txt shows that dpkg is being run via aptdaemon.

Start-Date: 2017-04-04 18:20:35
Commandline: aptdaemon role='role-commit-packages' sender=':1.100'
Install: libcuda1-375:amd64 (375.39-0ubuntu0.16.04.1, automatic), libvdpau1:amd64 (1.1.1-3ubuntu1, automatic), vdpau-driver-all:amd64 (1.1.1-3ubuntu1, automatic), nvidia-prime:amd64 (0.8.2, automatic), libxnvctrl0:amd64 (361.42-0ubuntu1, automatic), lib32gcc1:amd64 (1:6.0.1-0ubuntu1, automatic), libc6-i386:amd64 (2.23-0ubuntu7, automatic), screen-resolution-extra:amd64 (0.17.1, automatic), mesa-vdpau-drivers:amd64 (12.0.6-0ubuntu0.16.04.1, automatic), ocl-icd-libopencl1:amd64 (2.2.8-1, automatic), libjansson4:amd64 (2.7-3, automatic), bbswitch-dkms:amd64 (0.8-3ubuntu1, automatic), nvidia-opencl-icd-375:amd64 (375.39-0ubuntu0.16.04.1, automatic), nvidia-375:amd64 (375.39-0ubuntu0.16.04.1), nvidia-settings:amd64 (361.42-0ubuntu1, automatic)

So clearly, aptdaemon is being run in a context that has no debconf frontend.

This is really not acceptable that we have such bugs after all this time.

When I run update-manager (AKA Software Updater) here, I see that aptdaemon does get run with the correct environment of 'DEBCONF_PIPE=/tmp/aptdaemon-jcxymk3r/debconf.socket DEBIAN_FRONTEND=passthrough'. So this doesn't appear to be a problem in the version of update-manager that I have here.

Can you please describe exactly how you went about installing the nvidia driver, step by step? What did you click on at each step, etc.

To work around the problem on your system now, you should be able to run 'sudo dpkg --configure -a' from a terminal to go through the process of disabling SecureBoot.