blob: 81681cc8c399b518f22a1b3cdda1982f48b9a56d (
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
44
|
graphic: 0.968
device: 0.878
virtual: 0.781
performance: 0.736
VMM: 0.695
vnc: 0.681
semantic: 0.666
mistranslation: 0.543
KVM: 0.539
risc-v: 0.488
ppc: 0.427
network: 0.410
architecture: 0.409
hypervisor: 0.407
debug: 0.399
PID: 0.376
socket: 0.351
permissions: 0.342
user-level: 0.334
boot: 0.315
TCG: 0.297
i386: 0.265
peripherals: 0.253
register: 0.249
x86: 0.242
arm: 0.232
assembly: 0.208
kernel: 0.160
files: 0.105
GNOME/Mutter - Wayland Fractional Scaling Breaks VM Resolution
Description of problem:
VMs are rendered at a higher resolution than the pixel count of their window, seemingly because mutter is upscaling for fractional scaling.
Steps to reproduce:
1. Enable GNOME Mutter experimental fractional scaling
2. Launch VM
Additional information:
This only occurs when wayland fractional scaling is enabled, not when text is scaled. Since GNOME/mutter accomplishes fractional scaling by upscaling, I think the VM is being told its window has a higher resolution than it actually has, so it is rendering the VM at a higher resolution, which is then displayed at the display's real resolution.
In the screenshot below, my resolution is 2256 x 1504 and I have set fractional scaling to 125%. It is worth noting (2256 / 1.25) / 3606 is approximately 0.5.
I apologize if the report is unsatisfactory. I will provide more detail if instructed. I tried reporting to GNOME Boxes and Virt-manager, which both use QEMU, but it seems the problem is upstream.
|