> I never heard of debconf before today. Google tells me that debconf is > related to answering configuration questions while installing packages. > Is that related? There weren't any questions when installing linux- > signed-image-generic. Were there supposed to be?
Not when installing linux-signed-image-generic itself, but when installing the shim-signed package or when the fglrx-updates-core package builds its dkms module, yes there should be a series of questions asked about disabling secureboot. > Under 3.13.0-91, sudo modprobe fglrx-updates goes through without comment. > Under 3.13.0-92, sudo modprobe fglrx-updates fails with ERROR: could not > insert fglrx_updates: required key not available. > I don't know how this could be, since > 3.13.0-92-generic/updates/dkms/fglrx_updates.ko is signed with the same > key as 3.13.0-91-generic/updates/dkms/fglrx_updates.ko. This is because 3.13.0-91-generic doesn't enforce kernel signature verification, so it will load the module with a warning in dmesg about it being unverified and the kernel being 'tainted', whereas 3.13.0-92-generic does enforce kernel signature verification and rejects this module because it's not signed by a *trusted* key. To have the kernel trust the key you used for signing, you must enroll it in the firmware in either the SecureBoot database or the MOK database. -- 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
