> The 3.13.0-92 kernel is the first one in this series which implements > Ubuntu's updated SecureBoot policy, which requires specific action by the > machine administrator in order to allow unsigned modules. > You should have been prompted for this on upgrade. Do you remember seeing > such a prompt? No, I just clicked Install Updates in the Software Updater as normal.
$ debconf-show shim-signed debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied shim/secureboot_key: shim/secureboot_key_again: shim/title/secureboot: shim/error/secureboot_key_mismatch: * shim/disable_secureboot: shim/error/bad_secureboot_key: shim/enable_secureboot: false $ sudo debconf-show shim-signed shim/error/secureboot_key_mismatch: shim/secureboot_key: shim/secureboot_key_again: shim/error/bad_secureboot_key: shim/title/secureboot: shim/enable_secureboot: false * shim/disable_secureboot: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603655 Title: After update, xorg will not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
