Ubuntu

Installing shim 13-0ubuntu2 (artful-proposed) breaks secure boot and grub configuration

Asked by wmccarty

Today when I performed apt update, an update to shim was shown, I have backports enabled. I am using kubuntu 17.10 and have backports enabled as I have the Raven Ridge cpu on this new laptop. As a side note trying to troubleshoot with 800X600 will be fun until 4.15.

uname -r gets:
4.13.0-31-generic

lsb_release -a gets:
LSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
Distributor ID: Ubuntu
Description: Ubuntu 17.10
Release: 17.10
Codename: artful

I had the shim package version installed:
0.9+1474479173.6c180c6-1ubuntu1

And the artful proposed repo asked to install:
13-0ubuntu2 (artful-proposed)

I installed the new version of shim and shim-signed, and it broke the grub efi bootloader. Somehow I managed to revert to the old package version and now secure boot works.

Not sure if I'm being a noob and not understanding that I'm breaking this by installing proposed shim or not, but hopefully this is useful.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
wmccarty
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

I suggest you report a bug

Revision history for this message
wmccarty (wdmlist) said : 		#2

I couldn't find how to 'report a bug' without a bug report. Either way now, it looks like this problem has been solved. Just received an update to shim and shim-signed.

shim still shows 13-0ubuntu2
shim-signed shows 1.33.1~17.10.1+13-0ubuntu2

the changelog doesn't show any notes since 2017 for either, so I'm assuming the issue was eventually identified and fixed.

How does one create a bug when there is no trace or crash?

Revision history for this message
wmccarty (wdmlist) said : 		#3

Marking problem solved.

Revision history for this message
wmccarty (wdmlist) said : 		#4

Also, I rebooted after receiving the update, and was able to boot into Kubuntu ok, also I tested a signed kernel extension with VirtualBox that also started without incident.

Revision history for this message
Manfred Hampl (m-hampl) said : 		#5

1. Don't confuse artful-proposed and artful-backports
The -proposed repository is used during testing and might contain software that turns out not to work as expected.
See also https://wiki.ubuntu.com/Testing/EnableProposed

2. You can create a bug with the command "ubuntu-bug name_of_the_source_package".
See also https://help.ubuntu.com/community/ReportingBugs

Revision history for this message
wmccarty (wdmlist) said : 		#6

Many thanks, you nudged me in the right direction. Won't make that mistake again. Didn't see that proposed was enabled. Spent three hours straightening the pile of spaghetti noodle packages.