** Changed in: qemu (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte2.91 in Ubuntu.
https://bugs.launchpad.net/bugs/1868116
Title:
QEMU monitor no longer works
Status in QEMU:
New
Status
** Changed in: qemu (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte2.91 in Ubuntu.
https://bugs.launchpad.net/bugs/1868116
Title:
QEMU monitor no longer works
Status in QEMU:
New
Statu
Looking at the comments, it seems to me that this was an issue in VTE
that got fixed. Is there still anything left to do for upstream QEMU
here?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
@Thomas - there is a leftover task here and I've filed [1] for it in the new
tracker.
What is the right state to move this bug here into now?
[1]: https://gitlab.com/qemu-project/qemu/-/issues/137
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #137
https://gitlab.com/qemu-project/q
Thanks for opening the new ticket. Let's close this one here as WontFix
- since we will only look at the new issue now instead.
** Changed in: qemu
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vt
$ apt install libvte-2.91-0
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
libgnutls30 libhogweed5 libnettle7 libp11-kit0
Suggested packages:
gnutls-bin
The following NEW packages will be insta
Version difference of libvte-2.91-0 is 0.58.2-1ubuntu2 <->
0.59.91-0ubuntu2
Debian isn't frozen yet and has 0.60.0-2, but that is broken as well.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte2.91 in Ubuntu.
https://bugs.launchpad.n
Building vte from git on the tags matching eoan and focal.
LD_LIBRARY_PATH=/usr/local/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH ldd
./build/x86_64-softmmu/qemu-system-x86_64 | grep vte
libvte-2.91.so.0 => /usr/local/lib/x86_64-linux-gnu/libvte-2.91.so.0
(0x7ff9b4908000)
Eoans version 0
commit 55e5d53676960feb5dc11400ecdc7c9d7c4ab13e (refs/bisect/bad)
Author: Christian Persch
Date: Sun Nov 17 22:15:38 2019 +0100
lib: Add missing files
commit 7888602c3a980eee093313b2c0f949c756668070
(refs/bisect/skip-7888602c3a980eee093313b2c0f949c756668070)
Author: Christian Persch
Date
Bisect build
$ ninja -C _build uninstall; rm -rf _build; meson _build && ninja -C _build &&
ninja -C _build install; echo $?; ll /usr/local/lib/x86_64-linux-gnu/
Test
$ LD_LIBRARY_PATH=/usr/local/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH
./build/x86_64-softmmu/qemu-system-x86_64 -enable-kvm --drive
Lets turn the order around a bit:
83cbe9998aa1c2babbf32eed0b5fa3909360a83b (known good)
+ cherry pick 55e5d53676960feb5dc11400ecdc7c9d7c4ab13e lib: Add missing files
=> Good
+ cherry pick 9e4fbae2cabcd937ac4d1a984ba844d24b44b83f Use ICU for legacy =>
Bad
83cbe9998aa1c2babbf32eed0b5fa3909360a83
Last commit mentioning VTE is a while ago:
6415994 Thu Oct 11 17:30:39 2018 +0200 gtk: Don't vte_terminal_set_encoding()
on new VTE versions
I built head of qemu against head of vte - to check if I even need to look for
existing fixes.
=> That still fails, so it is probably time for a bug report
FYI: Since this affects qemu (and VTE) git head I added an upstream-qemu
task to the bug.
** Tags added: champagne rls-ee-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte2.91 in Ubuntu.
https://bugs.launchpad.net/bugs/1868116
Thanks for this investigation so far!
We've opened an upstream VTE issue at
https://gitlab.gnome.org/GNOME/vte/issues/222 .
We'd appreciate if QEMU developers joined us there. Apparently QEMU uses
the "commit" signal in a way that it was not meant to be used, and thus
it's unclear what the best s
Thank you Egmont for the bug for VTE in the gnome tracker!
Graphics isn't something I'm usually at home - the related qemu code is
mostly in ui/gtk.c per Maintainers file Gerd Hoffmann is the expert. I
subscribed him to the bug here to raise visibility for him.
--
You received this bug notificat
For a bit of reverse-confirmation of the findings so far.
If I build qemu without VTE, like (configure)
GTK support yes (3.24.14)
VTE support no
It works, due to the fallback implemented by [1][2].
But obviously without all the VTE features, I'd prefer a more fine grained fix
than dis
I'm not really a UI guy, so I was checking what I might have lost by disabling
VTE and found the very old [1]. That list of features really seems to make
disabling VTE not an real option:
"It's also screen reader accessible, supports copy/paste, proper scrolling and
most of the other feature
same seems to happen on Fedora 32.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte2.91 in Ubuntu.
https://bugs.launchpad.net/bugs/1868116
Title:
QEMU monitor no longer works
Status in QEMU:
New
Status in qemu package in Ubuntu:
I'm not sure how many of you are tracking the Vte bug [1] so here a
summary of the latest insight from there.
- Short term it seems that new behavior will be reverted in Vte 0.60.1.
- Long term the Vte devs might want to deprecate no-pty use cases or at least
better understand why apps use it tha
Thank you for investigating this. I would bisect QEMU, but wouldn't
investigate its libraries. Consequently, I would never find the cause of
this problem.
For now, I am using -monitor telnet:127.0.0.1:5,server,nowait to
have access to the monitor on QEMU guests.
--
You received this bug noti
Subscribed and Assigned to Ubuntu Desktop to get to 0.60.1 before Focal
releases.
I'd be happy about an update here that this surely is on your todo list.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte2.91 in Ubuntu.
https://bugs.la
>From IRC:
[16:10] cpaelzer, @vte, we should get 0.60.1 for focal, 0.59.91 is a
rc1 for 0.60, we are lacking behind merging the stable version from Debian but
it's on our backlog (kenvandine was look at that one), the .1 is part of GNOME
3.36.1 which we plan to get before release (I would under
As Vte-upstream long term would want to get rid of this implementation
style Christian Persch provided a qemu patch [1]. That is too much UI
for me to really have an in-depth opinion, but I can say that it builds
and input works fine with it.
I suggested on [2] to send it to qemu-devel, but in cas
THe update should be part of GNOME 3.36.1 which is due this weekend
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte2.91 in Ubuntu.
https://bugs.launchpad.net/bugs/1868116
Title:
QEMU monitor no longer works
Status in QEMU:
New
S
This bug was fixed in the package vte2.91 - 0.60.0-2ubuntu2
---
vte2.91 (0.60.0-2ubuntu2) focal; urgency=medium
* debian/libvte-2.91-0.install
- Dropped files duplicated in libvte-2.91-common
* debian/control.in
- Add appropriate Breaks/Replaces for moved files.
-- Ken V
** Bug watch added: Debian Bug tracker #954266
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954266
** Also affects: qemu (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954266
Importance: Unknown
Status: Unknown
--
You received this bug notification because yo
Thanks Ken!
I verified it and the new version indeed fixes the issue in focal.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte2.91 in Ubuntu.
https://bugs.launchpad.net/bugs/1868116
Title:
QEMU monitor no longer works
Status in QE
** Changed in: qemu (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte2.91 in Ubuntu.
https://bugs.launchpad.net/bugs/1868116
Title:
QEMU monitor no longer works
Status in QEMU:
New
Status in
28 matches
Mail list logo