Bug#989962: shim-signed 1.36~1+deb10u1 fails to boot some systems

2021-06-28 Thread Steve McIntyre
[ please keep the bug report in CC, I'm not the only person who might be reading this! ] On Mon, Jun 28, 2021 at 09:19:48AM -0700, David George Henderson III wrote: > >I generally install Debian off of DVD or a *.iso copied to flash rather than >an online repository. > >    That way I get a

Bug#989962: update to the version of shim-signed(Re: Bug#989962: shim-signed 1.36~1+deb10u1 fails to boot some systems)

2021-06-28 Thread David George Henderson III
Updated: the email is incorrect: this is the version shown in Debian 10 security : shim-signed (1.36~1+deb10u2+15.4-5~deb10u1) On 6/28/21 9:19 AM, David George Henderson III wrote: Hello Steve, I generally install Debian off of DVD or a *.iso copied to flash rather than an online

Bug#989962: shim-signed 1.36~1+deb10u1 fails to boot some systems

2021-06-28 Thread David George Henderson III
Hello Steve, I generally install Debian off of DVD or a *.iso copied to flash rather than an online repository.     That way I get a reproducible install. Recently, I found that my Debian 10.9 amd64 dvd-1 install stopped working on the Dell T1600 boot in UEFI mode.     This is the

Bug#989962: shim-signed 1.36~1+deb10u1 fails to boot some systems

2021-06-23 Thread Steve McIntyre
On Wed, Jun 23, 2021 at 04:10:46PM +0200, Ayke Halder wrote: >The new build also works on a T5600, thanks a lot! > > >What I did: > >1. Upgrade: shim-signed:amd64 (1.33+15+1533136590.3beb971-7, >1.36~1+deb10u2+15.4-5~deb10u1), shim-signed-common:amd64 >(1.33+15+1533136590.3beb971-7,

Bug#989962: shim-signed 1.36~1+deb10u1 fails to boot some systems

2021-06-23 Thread Ayke Halder
The new build also works on a T5600, thanks a lot! What I did: 1. Upgrade: shim-signed:amd64 (1.33+15+1533136590.3beb971-7, 1.36~1+deb10u2+15.4-5~deb10u1), shim-signed-common:amd64 (1.33+15+1533136590.3beb971-7, 1.36~1+deb10u2+15.4-5~deb10u1) --> System does not boot - as expected. 2.

Bug#989962: shim-signed 1.36~1+deb10u1 fails to boot some systems

2021-06-23 Thread Steve McIntyre
On Wed, Jun 23, 2021 at 01:00:51PM +0200, Grzegorz Szymaszek wrote: >On Tue, Jun 22, 2021 at 10:36:48PM +0100, Steve McIntyre wrote: >> Could you please verify if this new build fixes the problem you're >> seeing on your hardware? […] It may still complain about resource >> failures and

Bug#989962: shim-signed 1.36~1+deb10u1 fails to boot some systems

2021-06-23 Thread Grzegorz Szymaszek
On Tue, Jun 22, 2021 at 10:36:48PM +0100, Steve McIntyre wrote: > Could you please verify if this new build fixes the problem you're > seeing on your hardware? […] It may still complain about resource > failures and "import_mok_state() failed", but should then boot anyway in > non-secure mode. It

Bug#989962: shim-signed 1.36~1+deb10u1 fails to boot some systems

2021-06-22 Thread Steve McIntyre
On Tue, Jun 22, 2021 at 09:20:36PM +0200, Grzegorz Szymaszek wrote: >On Tue, Jun 22, 2021 at 01:35:51PM +0200, Grzegorz Szymaszek wrote: >> I have recently upgraded several buster amd64 machines; shim-signed went >> up from 1.33 to 1.36~1+deb10u1. […] > >FWIW, upgrading to 1.36~1+deb10u2 brings

Bug#989962: shim-signed 1.36~1+deb10u1 fails to boot some systems

2021-06-22 Thread Grzegorz Szymaszek
On Tue, Jun 22, 2021 at 01:35:51PM +0200, Grzegorz Szymaszek wrote: > I have recently upgraded several buster amd64 machines; shim-signed went > up from 1.33 to 1.36~1+deb10u1. […] FWIW, upgrading to 1.36~1+deb10u2 brings the problem back. Looks like the same as #990158. signature.asc

Bug#989962: shim-signed 1.36~1+deb10u1 fails to boot some systems

2021-06-22 Thread Grzegorz Szymaszek
Hi, I have recently upgraded several buster amd64 machines; shim-signed went up from 1.33 to 1.36~1+deb10u1. This has caused some machines to fail to boot with the mentioned error (“MoklistRT out of resources”). The affected systems include a Dell Latitude E6410 as well as a E6420, while a Dell