Bug#990867: shim-helpers-arm64-signed: post-install script fails with 'error exit status 1'

Diederik de Haas didi.debian at cknow.org
Sun Jul 11 17:56:16 BST 2021


On zondag 11 juli 2021 17:42:27 CEST Steve McIntyre wrote:
> >If an error is detected, a message like "Look at this wiki page <URL> for
> >possible solutions", with the solution you just provided me (among others),
> >would be really helpful.
> >I've made/attached screenshots which could be used for that.
> 
> I'm adding an extra section to https://wiki.debian.org/UEFI right now,
> at least.

Great :-)
But IMO it's also important to point to that when it fails.
"shim-helpers-arm64-signed package post-installation script subprocess 
returned error exit status 1" is not a helpful error message for most people.
I was wondering whether the 'real' problem was in that package or in an efi 
package or in grub(-*?) or in the kernel (evivars) or yet something else. Or a 
combination of those.

> >> 2. To the best of my knowledge, none of the current U-Boot releases
> >> support Secure Boot so you may as well remove the shim-signed
> >> package anyway. It's normally harmless to include it (so we pull
> >> it in via recommends), but on your system it's not going to do
> >> anything for you so you may as well remove it.
> >
> >It may have prevented me seeing this issue, but others would likely have
> >encountered it anyway. One of the reasons I run Sid is encountering issues
> >and finding a fix, so others won't have to. So I'm keeping it for now.
> Fair enough. You *should* be getting the same error message without
> shim being involved, though. Any update to the various grub-efi
> packages will end up calling grub-install, with the same results. 

ACK

> Have you not been seeing that?

Maybe I have, but I didn't realize it. I didn't know what caused the previous 
time I got this error and it was a 'random' command (or a lucky sequence of 
commands) that made the error go away. Assuming/Hoping it was a one time 
thing, I didn't investigate further.
But when I encountered it a second time, I felt I needed to report it.

Not knowing what caused it and not (really) knowing what fixed it, makes it 
hard to make connections. Now that I know it is/was caused by grub-install I 
can/will look out for that and that'll make me recognize patterns.

Thanks,
  Diederik
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-grub-devel/attachments/20210711/a22d03ab/attachment.sig>


More information about the Pkg-grub-devel mailing list