wp_fractional_scale_v1 will report 1x scale at first, and then switch to proper scale later

[matejdro]

Regression?

No

System Info and Version

System/Version info

Hyprland, built from branch  at commit 918d8340afd652b011b937d29d5eea0be08467f5  (flake.lock: update).
Date: Tue Jun 25 12:06:02 2024
Tag: v0.41.2, commits: 4886

flags: (if any)


System Information:
System name: Linux
Node name: KOMP
Release: 6.9.7-arch1-1
Version: #1 SMP PREEMPT_DYNAMIC Fri, 28 Jun 2024 04:32:50 +0000


GPU information: 
28:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6950 XT] [1002:73a5] (rev c0) (prog-if 00 [VGA controller])


os-release: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo


plugins:
  hypreasymotion by Zakk ver 1.0

Description

It appears that, when opening an application with wp_fractional_scale_v1 support, Hyprland will first give the application 1x scale (120) and then later correct it to real scale.

Sway, for example, does not have such behavior.

See more detailed analysis here: moverest/wl-kbptr#14 (comment)

How to reproduce

1. Set one of your monitors to scale >1
2. Open an application that supports wp_fractional_scale_v1 (such as git version of the https://github.com/moverest/wl-kbptr)
3. Note that application is blurry until the first keystroke is pressed.

Crash reports, logs, images, videos

Logs of me opening git version of the wl-kbptr on the 1.25x scale display:

wl-kbptr.txt

[matejdro]

Issue also seems to happen without wl_fractional_scale_v1 with similar symptoms (blurry windows on some applications until first keystroke). See moverest/wl-kbptr#14 (comment)

[vaxerski]

it's not really invalid, and neither is it a protocol violation or something unusual... This value can change (user changed scale factor) and is just how hyprland interally works. I don't see why this is a hyprland bug.

[matejdro]

This might be true, but it seems that at least some programs expect initial value to be correct, especially since other compositors like Sway do this.

[vaxerski]

I think it's a bug on the side of the programs then, though.

[matejdro]

Fair enough