Your message dated Sun, 14 Feb 2021 14:16:44 +0000
with message-id <[email protected]>
and subject line Bug#959530: fixed in qemu 1:5.2+dfsg-4
has caused the Debian Bug report #959530,
regarding qemu-user-binfmt: Some passed target arguments get interpreted by qemu
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.)


-- 
959530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959530
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-user-binfmt
Version: 1:3.1+dfsg-8+deb10u5
Severity: important

Dear Maintainer,

For Intel Atom (x86) notebooks used for education purposes, we need this 
package to run vscode which is no more released for i386. All other apps are 
running great on it, including other amd64 apps, thanks to binfmt.

On startup, I get the following error message in terminal:
> qemu: unknown option 'type=gpu-process'

After that message, the main process quits, saying that it failed to start the 
gpu process.

The code binary is starting several instances of itself for various tasks. For 
each subprocess, it passes this type argument to them. Obviously, qemu thinks 
that it should take it as its own argument but it is intended for code.
I do not really know hot this argument is passed and how to fix it; maybe we 
need a way to wrap the original command completly to isolate it from the qemu 
arguments...

It seems to be a relatively easy fix, so I dare reporting it. :-)

Greetings,
L3P3

-- System Information:
Debian Release: 10.3
  APT prefers stable-updates
  APT policy: (1000, 'stable-updates'), (1000, 'proposed-updates'), (1000, 
'stable'), (1, 'stable-updates'), (1, 'proposed-updates'), (1, 'stable')
Architecture: i386 (i686)
Foreign Architectures: amd64

Kernel: Linux 4.19.0-9-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:5.2+dfsg-4
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: SHA256

Format: 1.8
Date: Sun, 14 Feb 2021 16:52:10 +0300
Source: qemu
Architecture: source
Version: 1:5.2+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QEMU Team <[email protected]>
Changed-By: Michael Tokarev <[email protected]>
Closes: 956377 959530 970460
Changes:
 qemu (1:5.2+dfsg-4) unstable; urgency=medium
 .
   [ Michael Tokarev ]
   * require libfdt >= 1.5.0-2 due to #931046
   * qemu-user: attempt to preserve argv[0] when run under binfmt
     (Closes: #970460, #959530)
     This changes the enterpreter name for all linux-user registered
     binfmts, so it potentially can break stuff.  The actual binary
     being registered now is /usr/libexec/qemu-binfmt/foo-binfmt-P,
     which is a symlink to actual /usr/lib/qemu-foo[-static].
   * ignore .git-submodule-status when building source
   * some security fixes from upstream:
     o arm_gic-fix-interrupt-ID-in-GICD_SGIR-CVE-2021-20221.patch
       Closes: CVE-2021-20221
       GIC (armv7): out-of-bound heap buffer access via an interrupt ID field
     o 9pfs-Fully-restart-unreclaim-loop-CVE-2021-20181.patch
       Closes: CVE-2021-20181
   * non-security fixes from upstream:
     pc-bios-descriptors-fix-paths-in-json-files.patch - fixes wrong paths
     in edk2-firmware-related json files introduced in 5.2
 .
   [ Christian Ehrhardt ]
   * d/control-in: avoid version mismatch of installed binaries
     (Closes: #956377)
 .
   [ Dan Streetman ]
   * Backport configure param --with-git-submodules and set to 'ignore'
Checksums-Sha1:
 816f1682c4f54ef9e0b77e959c5c77f8460db94a 6597 qemu_5.2+dfsg-4.dsc
 99f4aeddc6f5ed0c1f4ee84da22a591d32dff623 99408 qemu_5.2+dfsg-4.debian.tar.xz
 11aae2831edfc5fa28a51506a6ac7b47737c25c4 9102 qemu_5.2+dfsg-4_source.buildinfo
Checksums-Sha256:
 7841e5dc1b7e286b6efb901ca6d440cccb39e1624c6311a10b1fef0ca2f6bf65 6597 
qemu_5.2+dfsg-4.dsc
 c4439a4130efa9eb37664e04e9d93722d37a2b3c836dd107240d372e72947899 99408 
qemu_5.2+dfsg-4.debian.tar.xz
 18c4557a95b45b1ccd56325aab3de78744a4c217869604c256e2bed411c084dc 9102 
qemu_5.2+dfsg-4_source.buildinfo
Files:
 4349e64c2a2f579dcc52eb4cdfe7e142 6597 otherosfs optional qemu_5.2+dfsg-4.dsc
 8e4239a97dd4fd18c47151393a39ae29 99408 otherosfs optional 
qemu_5.2+dfsg-4.debian.tar.xz
 4a7e8f8261142b4b7943369734938de0 9102 otherosfs optional 
qemu_5.2+dfsg-4_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQFDBAEBCAAtFiEEe3O61ovnosKJMUsicBtPaxppPlkFAmApK1MPHG1qdEB0bHMu
bXNrLnJ1AAoJEHAbT2saaT5ZcuMH+gJbgCItoTfYCaJtKtiiS5mt2wQJH9pwCs8Z
GTLU8TA9t4l4SQ8JebpfWFNgeCJnz4fiTR9S7d35JBJewcb9yvLWZ0/0X7aPTdO2
xWWzdjfLm/DPcmGenQd1FTmrsObVNrgzaqOLBLCm/67vHqwk1mBqJQgEt4Il+ZR8
yKNMsykk8hyun1AxZ8pZRyriT6njKLAvD50uA9sW0j7G0REgr1JvkJWOPLEpkk98
KxSC56CvAA5HOuFJvHuPDOIOAgrU4KNB0n4bTSj8ewehZT7MgF1/S0nBS3R4DBST
SNaRPY7O0AiCAC+0GpEyppw3/feYgu5ImGaWWz7G1684eXxDf1E=
=969T
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to