summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/118/graphic/1439800
blob: e490359e4e68673c7c78284601e323edb197fa79 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
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.]