Your message dated Thu, 8 Oct 2026 13:51:40 +0100
with message-id <[email protected]>
and subject line Re: Bug#1150289: shim-signed: 1.51+pmx1+16.1-2+pmx1 fails to 
install due to no "SetupMode"
has caused the Debian Bug report #1150289,
regarding shim-signed: 1.51+pmx1+16.1-2+pmx1 fails to install due to no 
"SetupMode"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1150289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1150289
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: shim-signed
Version: 1.48+pmx1+16.1-1+pmx1
Severity: important
X-Debbugs-Cc: [email protected]

Dear Maintainer,

   * What led up to the situation?

I was updating my system when this package update failed to install. It only 
failed on one of my systems.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

I just did a standard upgrade, which was ineffective.

   * What was the outcome of this action?

I received the following error:

> Preparing to unpack .../shim-signed_1.51+pmx1+16.1-2+pmx1_amd64.deb ...
> shim-signed: checking if we can safely install 
> /usr/lib/shim/shimx64.efi.signed
> Unexpected outcome from mokutil:
> """
> Failed to read "SetupMode" variable: No such file or directory
> """
> Please report this as a bug agsinst shim-signed, including the above 
> information.
> dpkg: error processing archive 
> /var/cache/apt/archives/shim-signed_1.51+pmx1+16.1-2+pmx1_amd64.deb 
> (--unpack):
>  new shim-signed:amd64 package pre-installation script subprocess returned 
> error exit status 1
> Errors were encountered while processing:
>  /var/cache/apt/archives/shim-signed_1.51+pmx1+16.1-2+pmx1_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)

I would also note there is a typo in the word "against" instead being "agsinst".

   * What outcome did you expect instead?

I expected all updates to install properly.


-- System Information:
Debian Release: 13.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 7.0.2-6-pve (SMP w/40 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages shim-signed depends on:
ii  grub-efi-amd64-bin         2.12-9+pmx2
ii  grub2-common               2.12-9+pmx2
iu  shim-helpers-amd64-signed  1+16.1+2+pmx1
iu  shim-signed-common         1.51+pmx1+16.1-2+pmx1

shim-signed recommends no packages.

shim-signed suggests no packages.

-- debconf information excluded

--- End Message ---
--- Begin Message ---
Hi Amy,

On Wed, Oct 07, 2026 at 09:27:07PM -0700, Amy Parker wrote:
>Package: shim-signed
>Version: 1.48+pmx1+16.1-1+pmx1

That's not a Debian version of the shim-signed package, and we fixed
this issue in version 1.50 in Debian.

That version suggests you might be using a Proxmox system? If so, you
should be talking to them rather than Debian directly here. I've added
a CC to their support team here for you.

Checking, they also have a Proxmox version of 1.51 in
shim-signed_1.51+pmx1+16.1-2+pmx1_amd64.deb which will almost
definitely fix this problem for you.

Anyway, closing this Debian bug - it's not a Debian issue.

>Severity: important
>X-Debbugs-Cc: [email protected]
>
>Dear Maintainer,
>
>   * What led up to the situation?
>
>I was updating my system when this package update failed to install. It only 
>failed on one of my systems.
>
>   * What exactly did you do (or not do) that was effective (or
>     ineffective)?
>
>I just did a standard upgrade, which was ineffective.
>
>   * What was the outcome of this action?
>
>I received the following error:
>
>> Preparing to unpack .../shim-signed_1.51+pmx1+16.1-2+pmx1_amd64.deb ...
>> shim-signed: checking if we can safely install 
>> /usr/lib/shim/shimx64.efi.signed
>> Unexpected outcome from mokutil:
>> """
>> Failed to read "SetupMode" variable: No such file or directory
>> """
>> Please report this as a bug agsinst shim-signed, including the above 
>> information.
>> dpkg: error processing archive 
>> /var/cache/apt/archives/shim-signed_1.51+pmx1+16.1-2+pmx1_amd64.deb 
>> (--unpack):
>>  new shim-signed:amd64 package pre-installation script subprocess returned 
>> error exit status 1
>> Errors were encountered while processing:
>>  /var/cache/apt/archives/shim-signed_1.51+pmx1+16.1-2+pmx1_amd64.deb
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>I would also note there is a typo in the word "against" instead being 
>"agsinst".
>
>   * What outcome did you expect instead?
>
>I expected all updates to install properly.
>
>
>-- System Information:
>Debian Release: 13.7
>  APT prefers stable-updates
>  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
> 'stable')
>Architecture: amd64 (x86_64)
>
>Kernel: Linux 7.0.2-6-pve (SMP w/40 CPU threads; PREEMPT)
>Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
>Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not 
>set
>Shell: /bin/sh linked to /usr/bin/dash
>Init: systemd (via /run/systemd/system)
>LSM: AppArmor: enabled
>
>Versions of packages shim-signed depends on:
>ii  grub-efi-amd64-bin         2.12-9+pmx2
>ii  grub2-common               2.12-9+pmx2
>iu  shim-helpers-amd64-signed  1+16.1+2+pmx1
>iu  shim-signed-common         1.51+pmx1+16.1-2+pmx1
>
>shim-signed recommends no packages.
>
>shim-signed suggests no packages.
>
>-- debconf information excluded
>
-- 
Steve McIntyre, Cambridge, UK.                                [email protected]
"Since phone messaging became popular, the young generation has lost the
 ability to read or write anything that is longer than one hundred and sixty
 characters."  -- Ignatios Souvatzis

--- End Message ---

Reply via email to