Incompatibility with future VTE will breaks qemu monitor (::commit signal)
Hi, this is a writeup of the remaining loose ends on this LP1868116.
What happened was that VTE applied this change and due to that (quoting from the GNOME issue)
So the problem turns out that because the terminal has no PTY, the commit in question short-circuits the emission of the ::commit signal, which qemu uses to a) echo the data back to the terminal via vte_terminal_feed(), and b) write somewhere else.
Not sure what it's trying to achieve here, and if there would be more sane setup that vte could support than hooking ::commit.
For the time being this was resolved in VTE via this fix, but it was stated that
Since I do want to get rid of the ::commit signal eventually ...
So sooner or later qemu needs to fix or adapt things in that regard. There was a qemu patch suggested on the gnome issue. I've back then tested it and can confirm that it works properly.
But the patch wasn't meant to be complete or final-polished, so the Author Christian Persch (thanks for all the work btw!) didn't fully submit it to qemu and asked for someone to to consider picking it up or discussing alternatives - quote:
Since I do want to get rid of the ::commit signal eventually, it would be good to get some (obviously more polished) form of that patch upstream, and/or discuss what qemu's requirements for a replacement are.
This "pick up polish and finalize" tasks still is let open for grabs. Therefore I was filing this bug to carry this leftover of LP1868116 into the new tracker so that we can close the old bug.
P.S: @thuth is there any tagging needed that usually would be needed for those carry-over-bugs?