summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/108/other/1423
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/zero-shot/108/other/1423')
-rw-r--r--results/classifier/zero-shot/108/other/142328
1 files changed, 28 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/1423 b/results/classifier/zero-shot/108/other/1423
new file mode 100644
index 000000000..5c9417ccc
--- /dev/null
+++ b/results/classifier/zero-shot/108/other/1423
@@ -0,0 +1,28 @@
+graphic: 0.913
+device: 0.907
+PID: 0.791
+semantic: 0.726
+debug: 0.632
+permissions: 0.629
+boot: 0.621
+performance: 0.610
+files: 0.567
+vnc: 0.549
+other: 0.522
+socket: 0.475
+network: 0.423
+KVM: 0.103
+
+QEMU 6.2.0 fullscreen problem
+Description of problem:
+After running the command above, clicking on "Try Ubuntu" and adjusting the guest display resolution in GNOME to the native resolution, pressing ctrl+alt+f yields a "fullscreen" that only covers the QEMU window but not the entire host screen. This is not the case when switching to fullscreen while the boot screen is active or running `qemu-system-x86_64 -display gtk,full-screen=on`. 
+
+The problem also occurs when replacing `-device qxl-vga` by `-device VGA,vgamem_mb=64`. The problem however does not occur when using `-device virtio-vga` instead of `-device qxl-vga` or `-display sdl` instead of `-display gtk`.
+Steps to reproduce:
+1. Run the command above
+2. Click "Try Ubuntu"
+3. Set guest resolution to native resolution (1920x1200 in my case)
+4. Move the window a bit off the corners to observe the effect
+5. Press ctrl+alt+f
+Additional information:
+The bug has also been [reported here](https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2000739).