summary refs log tree commit diff stats
path: root/results/classifier/118/graphic/1819908
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/118/graphic/1819908')
-rw-r--r--results/classifier/118/graphic/181990857
1 files changed, 57 insertions, 0 deletions
diff --git a/results/classifier/118/graphic/1819908 b/results/classifier/118/graphic/1819908
new file mode 100644
index 000000000..64b199715
--- /dev/null
+++ b/results/classifier/118/graphic/1819908
@@ -0,0 +1,57 @@
+graphic: 0.956
+kernel: 0.707
+semantic: 0.682
+performance: 0.680
+device: 0.652
+virtual: 0.604
+user-level: 0.592
+KVM: 0.573
+hypervisor: 0.550
+mistranslation: 0.533
+x86: 0.432
+architecture: 0.394
+i386: 0.390
+ppc: 0.389
+PID: 0.360
+permissions: 0.317
+network: 0.303
+register: 0.290
+socket: 0.257
+debug: 0.254
+risc-v: 0.231
+peripherals: 0.230
+VMM: 0.226
+arm: 0.205
+assembly: 0.201
+vnc: 0.181
+TCG: 0.172
+files: 0.134
+boot: 0.097
+
+slight screen corruption when maximizing window
+
+Host: Ubuntu disco
+qemu-kvm: 1:3.1+dfsg-2ubuntu2
+libvirt: 5.0.0-1ubuntu2
+
+
+Guest: ubuntu bionic
+guest is using cirrus video, with the extra modules kernel package installed and the cirrus kernel module loaded
+
+A non-maximized terminal window works just fine. As an example, I run "lsmod". It fills the screen, which then scrolls a bit.
+
+The moment I maximize that window, though, the rendering breaks. I can see the commands I type, but not their output. See attached video.
+
+
+
+lsmod run on a non-maximized window. All looks good.
+
+continuing from the previous screenshot, all I did here was to click the maximize button. We can already see some bad rendering on the top right corner.
+
+Here, with the maximized window, I typed several commands again: lsmod, clear, clear. If you look carefully, you can see the clear at the bottom, then at the top again, and nothing changes. All I can see are the characters I type, but not the command's output or effect. The screen doesn't clear, and the list of modules produced by "lsmod" doesn't appear.
+
+Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+