1 files changed, 43 insertions, 0 deletions
diff --git a/results/classifier/118/graphic/1439800 b/results/classifier/118/graphic/1439800
new file mode 100644
index 000000000..e490359e4
--- /dev/null
+++ b/results/classifier/118/graphic/1439800
@@ -0,0 +1,43 @@
+graphic: 0.933
+device: 0.895
+performance: 0.666
+architecture: 0.653
+mistranslation: 0.637
+network: 0.628
+boot: 0.620
+semantic: 0.610
+vnc: 0.456
+hypervisor: 0.444
+files: 0.439
+kernel: 0.427
+debug: 0.417
+peripherals: 0.404
+risc-v: 0.379
+socket: 0.352
+PID: 0.351
+ppc: 0.333
+register: 0.333
+user-level: 0.304
+VMM: 0.302
+permissions: 0.301
+TCG: 0.292
+x86: 0.273
+virtual: 0.239
+i386: 0.238
+arm: 0.198
+assembly: 0.188
+KVM: 0.126
+
+GTK fullscreen mode start stretched but fixes after leaving and returning full screen mode
+
+I'm running QEMU 2.2.91 compiled directly from git and starting QEMU with the -full-screen option. The guest OS is Windows 8.1 using the VGA driver from QEMU.
+
+The image can be fixed leaving the full-screen mode and returning it back. So it appears that QEMU loses the information with multiple resolution changes of the boot process and fails in the end.
+
+The description can be a little confusing, so I've put a video on Youtube, so it can demonstrate the real issue:
+https://www.youtube.com/watch?v=-lWbWEUOSsk
+
+Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU and the latest version of GTK? Or could we close this ticket nowadays?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+