[Bug 1673904] [NEW] update-secureboot-policy --enable does not work after dkms modules removed

[Steve Langasek]

Public bug reported:

If I have disabled secureboot on my system via update-secureboot-policy
due to the presence of dkms modules, but subsequently remove these dkms
modules because I decide I don't like not having secureboot, I cannot
re-enable SB by running 'update-secureboot-policy --enable'.

I think either the check for /var/lib/dkms should only apply when
update-secureboot-policy is called without arguments, or this check
should be encoded in the shim-signed postinst so that manual calls from
the commandline DWIM.

** Affects: shim-signed (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shim-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1673904

Title:
  update-secureboot-policy --enable does not work after dkms modules
  removed

Status in shim-signed package in Ubuntu:
  New

Bug description:
  If I have disabled secureboot on my system via update-secureboot-
  policy due to the presence of dkms modules, but subsequently remove
  these dkms modules because I decide I don't like not having
  secureboot, I cannot re-enable SB by running 'update-secureboot-policy
  --enable'.

  I think either the check for /var/lib/dkms should only apply when
  update-secureboot-policy is called without arguments, or this check
  should be encoded in the shim-signed postinst so that manual calls
  from the commandline DWIM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1673904/+subscriptions