Your message dated Mon, 01 Jun 2026 06:04:40 +0000
with message-id <[email protected]>
and subject line Bug#1136993: fixed in qemu 1:11.0.1+ds-1
has caused the Debian Bug report #1136993,
regarding qemu-user: Attempting to install qemu-user without qemu-user-binfmt
installed a foreign arch qemu-user-binfmt
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.)
--
1136993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1136993
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-user
Version: 1:10.0.8+ds-0+deb13u1+b2
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainer,
* What led up to the situation?
I wanted to install a cross-compile/emulation setup for s390x (the
only(?) big-endian arch supported by debian).
* What exactly did you do (or not do) that was effective (or
ineffective)?
I installed the s390x cross compiler, apt-get install gcc-s390x-linux-gnu.
I enabled s390x as a foreign arch, dpkg --add-foreign-architectore
s390x, and ran apt-get update. (My intention was to enable
installation of s390x library dev packages, e.g., apt-get install
nettle-dev:s390x. But I haven't been able to actually do that install,
due to what looked like version conflicts with my native libc, which I
haven't investigated).
Next, I wanted qemu-user. Just running apt-get install qemu-user also
installs the recommended qemu-user-binfmt package. Since I didn't want
to get the binfmt magic, I instead ran apt-get install qemu-user
qemu-user-binfmt- (note trailing -). Then apt-get decided to install
the additional package qemu-user-binfmt:s390x, and I accepted that
and pressed ENTER without realizing the bad consequences.
* What was the outcome of this action?
I could no longer execute *any* native (x86_64) binaries, no ls, no
dpkg, no apt-get... Everything failed, and as far as I understand this
broken state, my shell got a ENOEXEC error from the exec syscall. My
computer was closed to bricked. (Luckily, I still had an open root
bash shell, and I could use the *builtin* printf command like printf
"" > /usr/lib/binfmt.d/qemu-x86_64.conf, reboot using the power
button, and get back to a working state where I could run apt-get
remove qemu-user-binfmt:s390x).
* What outcome did you expect instead?
Execution of native binaries unaffected. s390x binaries executable
only by invoking qemu-s390x explicitly.
-- System Information:
Debian Release: 13.5
APT prefers stable-updates
APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990,
'stable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: s390x
Kernel: Linux 6.12.88+deb13-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
qemu-user depends on no packages.
Versions of packages qemu-user recommends:
pn qemu-user-binfmt <none>
qemu-user suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:11.0.1+ds-1
Done: Michael Tokarev <[email protected]>
We believe that the bug you reported is fixed in the latest version of
qemu, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Tokarev <[email protected]> (supplier of updated qemu package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 01 Jun 2026 08:51:12 +0300
Source: qemu
Architecture: source
Version: 1:11.0.1+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QEMU Team <[email protected]>
Changed-By: Michael Tokarev <[email protected]>
Closes: 1136993
Changes:
qemu (1:11.0.1+ds-1) unstable; urgency=medium
.
* new upstream stable/bugfix release
Closes: multiple vulnerabilities in the UEFI code:
CVE-2026-8341 CVE-2026-41435 CVE-2026-41436 CVE-2026-41437
CVE-2026-41438 CVE-2026-41439 CVE-2026-41440
* remove hw-display-don-t-accidentally-autofree-existing-virg.patch
* d/control: add Depends: native-architecture to qemu-user-binfmt
(Closes: #1136993)
Similar dependency for qemu-user should probably be added too
Checksums-Sha1:
85e4ba3169aac20b0c5b940429959971283f8793 10043 qemu_11.0.1+ds-1.dsc
e4967313f7cfa85cb25b82a589f66a5dbb58e7a0 38811112 qemu_11.0.1+ds.orig.tar.xz
ed39af8672b39fdeb3a62297a2bac6bd9a2c4c25 126472 qemu_11.0.1+ds-1.debian.tar.xz
2440a9b48d988af9ee77af518502d0a0d0f7f01f 8327 qemu_11.0.1+ds-1_source.buildinfo
Checksums-Sha256:
86ba29b4df1721d3bffa040f4328a4f1e0b0f192382fb0efa91db1269030fc8b 10043
qemu_11.0.1+ds-1.dsc
75a0f910bc45ef532ab3c705a6995bb96d70bca1826c2f61da6e13a3719a089f 38811112
qemu_11.0.1+ds.orig.tar.xz
668dd373f9bf89dbb70568384ef909ae18e11ac0296f9201d77353d754bf93fb 126472
qemu_11.0.1+ds-1.debian.tar.xz
015f7a136d89f2f18686a7c71eb3f68883d165095c1c8ff4f8279ca66472c755 8327
qemu_11.0.1+ds-1_source.buildinfo
Files:
05d8027b7c467fc5267a36cf8bf854cd 10043 otherosfs optional qemu_11.0.1+ds-1.dsc
b8681dce2d17236a24eca9ef2cdba054 38811112 otherosfs optional
qemu_11.0.1+ds.orig.tar.xz
38ca0535c70404461b3758d5206944e9 126472 otherosfs optional
qemu_11.0.1+ds-1.debian.tar.xz
5dc68392794522ef5e5f91df53cb97e9 8327 otherosfs optional
qemu_11.0.1+ds-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
wsG7BAEBCgBvBYJqHR34CRCCqkokOx6UeEcUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmd+mYBRD715ocdnL9lyOfGkANbrzu8n13SGvrLQSHl9
PRYhBGSqKrUx1WkDNmv++YKqSiQ7HpR4AAAfoRAApL0mRfUDwVholpk9dzbljTdD
FPXusN3ZMIPl0xRnwrapNe1ry1YujBHZTHzmnYZLKlfPM/71FK/8tssVtPjvCoyh
m+5ySCICFqzwVTq4lAu2YzmQ13yrn6ma4/ZlyHy7WsxMXQrKoWItt9q4NSI0VHAB
lDK/moCgt5fo4bShpKOe5ZEhAcnUrw9hUZVxcixea3aO1dvfWcPVK1ossFtlSg+a
1SDSkAmqmFHG6kTVi6/uXYcjFd/yjdklfc3EHMS4Dq0NGw4/R9juVVpAHcaRBL70
gz7QwpF5RlxtIk7nMhodlS+IuJhozJSRUzzSeqEpFF6iAkqifatgYRmfZnueOj3H
S2Qpc2M/Y4dLdUSlE0IQ+DQvqVXG9RRyVyiz+4x2DVda171MDbh1KZ88wvaX6hoz
zK0fBpw/mkaYC5oel7hnYOnUA3rtP7PtrpI7IqrSkqY1f33gg1Nqaky767uCULJv
x6ta9Rbgxn7GpVcujxbz7lbZHDWKfTpjpeD1hdvI6kvQ6FmmdS/kGBT7yVs5C0SB
z87oFBel0yqpxZM0fIiEyOufRrMyoXZ0sQmuqctz9tN+jVRKAnK7U+r09BE7OCbq
JhZXD20NsTedvJ0XDR/2kBfBnKbMj2mVlC+IMiY4T7qIagrU3FMQIJNQr4qQuzj6
4AVFYykoyq2ksx0fhoo=
=FO5X
-----END PGP SIGNATURE-----
pgps4WSMGcIcH.pgp
Description: PGP signature
--- End Message ---
