Your message dated Fri, 8 May 2020 09:08:58 +0200
with message-id <[email protected]>
and subject line Re: Bug#954266: FYI debugged and a fix is committed in VTE
has caused the Debian Bug report #954266,
regarding qemu-system-x86: graphical-mode monitor doesn't work
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.)


-- 
954266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954266
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-system-x86
Version: 1:4.2-3

I can switch to the monitor using Ctrl-Alt-2; but when I start typing a command, nothing happens.

Work-around: text-mode monitor (-monitor stdio) works as it should.


-- System Information:
Architecture: i386

Versions of packages qemu-system-x86 depends on:
ii  ipxe-qemu             1.0.0+git-20190125.36a4c85-5
ii  libaio1               0.3.112-5
ii  libasound2            1.2.2-2.1
ii  libbrlapi0.7          6.0+dfsg-5
ii  libc6                 2.30-2
ii  libcacard0            1:2.6.1-1
ii  libcapstone3          4.0.1+really+3.0.5-1+b2
ii  libepoxy0             1.5.4-1
ii  libfdt1               1.6.0-1
ii  libgbm1               19.3.3-1
ii  libgcc-s1 [libgcc1]   10-20200312-2
ii  libglib2.0-0          2.64.1-1
ii  libgnutls30           3.6.12-2
ii  libibverbs1           28.0-1+b1
ii  libjpeg62-turbo       1:1.5.2-2+b1
ii  libncursesw6          6.2-1
ii  libnettle7            3.5.1+really3.5.1-2
ii  libnuma1              2.0.12-1+b1
ii  libpixman-1-0         0.36.0-1
ii  libpng16-16           1.6.37-2
ii  librdmacm1            28.0-1+b1
ii  libsasl2-2            2.1.27+dfsg-2
ii  libseccomp2           2.4.3-1
ii  libslirp0             4.1.0-2
ii  libspice-server1      0.14.2-4
ii  libtinfo6             6.2-1
ii  libusb-1.0-0          2:1.0.23-2
ii  libusbredirparser1    0.8.0-1+b1
ii  libvdeplug2           2.3.2+r586-2.2
ii  libvirglrenderer1     0.8.2-1
ii  libxendevicemodel1    4.11.3+24-g14b62ab3e5-1
ii  libxenevtchn1         4.11.3+24-g14b62ab3e5-1
ii  libxenforeignmemory1  4.11.3+24-g14b62ab3e5-1
ii  libxengnttab1         4.11.3+24-g14b62ab3e5-1
ii  libxenmisc4.11        4.11.3+24-g14b62ab3e5-1
ii  libxenstore3.0        4.11.3+24-g14b62ab3e5-1
ii  libxentoolcore1       4.11.3+24-g14b62ab3e5-1
ii  qemu-system-common    1:4.2-3
ii  qemu-system-data      1:4.2-3
ii  seabios               1.13.0-1
ii  zlib1g                1:1.2.11.dfsg-2

--
Jakub Wilk

--- End Message ---
--- Begin Message ---
* Christian Ehrhardt <[email protected]>, 2020-03-27, 14:35:
FYI - VTE 0.60.1 will fix this

For details see:
https://bugs.launchpad.net/qemu/+bug/1868116
https://gitlab.gnome.org/GNOME/vte/issues/222

It works now, presumably thanks to libvte update.

--
Jakub Wilk

--- End Message ---

Reply via email to