(unattended-upgrade, already-installed dkms modules) package shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[John Edwards]

g

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
.proc.sys.kernel.moksbstate_disabled: 0
.sys.firmware.efi.efivars.MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23: Error: [Errno 2] No such file or directory: '/sys/firmware/efi/efivars/MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23'
.sys.firmware.efi.efivars.SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c: 

[Steve Langasek (vorlon)]

Thank you for the report. This shows that you had an unattended upgrade that ran and upgraded the version of the nvidia dkms module that you have installed; and that this triggered a request from shim to disable SecureBoot on your system, because dkms modules are incompatible with SecureBoot currently.

Do you remember being prompted previously about turning off SecureBoot? Did you elect not to turn off SecureBoot? Or, did you choose the option to disable SecureBoot, but not confirm this selection on reboot?

[John Edwards (jsedwards)]

Thanks for the reply I have since successfully upgraded

John

> On 1 Jun 2017, at 19:25, Steve Langasek <email address hidden> wrote:
>
> Thank you for the report. This shows that you had an unattended upgrade
> that ran and upgraded the version of the nvidia dkms module that you
> have installed; and that this triggered a request from shim to disable
> SecureBoot on your system, because dkms modules are incompatible with
> SecureBoot currently.
>
> Do you remember being prompted previously about turning off SecureBoot?
> Did you elect not to turn off SecureBoot? Or, did you choose the option
> to disable SecureBoot, but not confirm this selection on reboot?
>
> ** Summary changed:
>
> - package shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
> + (unattended-upgrade, already-installed dkms modules) package shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
>
> ** Changed in: shim-signed (Ubuntu)
> Importance: Undecided => High
>
> ** Changed in: shim-signed (Ubuntu)
> Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1694986
>
> Title:
> (unattended-upgrade, already-installed dkms modules) package shim-
> signed 1.28+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade:
> subprocess installed post-installation script returned error exit
> status 1
>
> Status in shim-signed package in Ubuntu:
> New
>
> Bug description:
> g
>
> ProblemType: Package
> DistroRelease: Ubuntu 17.04
> Package: shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1
> ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
> Uname: Linux 4.10.0-21-generic x86_64
> .proc.sys.kernel.moksbstate_disabled: 0
> .sys.firmware.efi.efivars.MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23: Error: [Errno 2] No such file or directory: '/sys/firmware/efi/efivars/MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23'
> .sys.firmware.efi.efivars.SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c: 
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1694986/+subscriptions

[Steve Langasek (vorlon)]

I'm glad you were able to upgrade. It is still important to us to understand how your system got into this state, so that we can help solve the problem for other users. Do you remember handling SecureBoot on your system previously?

[John Edwards (jsedwards)]

Sorry don't remember, but it certainly did this time when it succeeded

John

> On 1 Jun 2017, at 20:45, Steve Langasek <email address hidden> wrote:
>
> I'm glad you were able to upgrade. It is still important to us to
> understand how your system got into this state, so that we can help
> solve the problem for other users. Do you remember handling SecureBoot
> on your system previously?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1694986
>
> Title:
> (unattended-upgrade, already-installed dkms modules) package shim-
> signed 1.28+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade:
> subprocess installed post-installation script returned error exit
> status 1
>
> Status in shim-signed package in Ubuntu:
> New
>
> Bug description:
> g
>
> ProblemType: Package
> DistroRelease: Ubuntu 17.04
> Package: shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1
> ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
> Uname: Linux 4.10.0-21-generic x86_64
> .proc.sys.kernel.moksbstate_disabled: 0
> .sys.firmware.efi.efivars.MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23: Error: [Errno 2] No such file or directory: '/sys/firmware/efi/efivars/MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23'
> .sys.firmware.efi.efivars.SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c: 
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1694986/+subscriptions

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Psenik1 (psenik1)]

some news about this?