Native Wayland - LibreOffice GTK3 blurry rendering with certain scaling

[tekstryder]

At certain combinations of scaling factors the rendered document text in LibreOffice is blurry.

I have two displays:

• Display (PHL 328E1): 3840x2160 @ 60 Hz (as 3072x1728) in 32" [External]
• Display (DELL U2711): 1440x2560 @ 60 Hz in 27" [External]

Optimal scaling factors for my eyes is 1.25 : 1.00 respectively.

Hyprland version

0.50

Regression

No

Describe the bug

• hyprland is build without Xwayland (-DNO_XWAYLAND:STRING=true)
• LibreOffice is using the default GTK3 backend
• LibreOffice UI elements are rendered correctly and are NOT affected
• Rendering of document text and font picker options are blurry

Does NOT occur on Sway with native Wayland (wlroots 0.19 (Vulkan Backend) (-Dxwayland=disabled))
Does NOT occur on Mutter with native Wayland (-Dxwayland=false -Dx11=false)

Comparison of same scaling factors (1.25 : 1.00) Sway vs Hyprland:

Clean is Sway. Blurry is Hyprland.

Testing a variety of scaling combos yielded:

------
 good
------
1.10 : 1.00
1.20 : 1.066667
1.25 : 1.066667
1.333333 : 1.066667

------
 bad
------
1.20 : 0.90
1.20 : 1.00
1.25 : 1.00
1.25 : 0.90
1.25 : 0.95
1.333333 : 1.00

So far I've come up with 2 sub-optimal workarounds:

1. Use GTK4 or QT5 or QT6 renderer for LibreOffice at desired scaling factors
2. Use default GTK3 renderer for LibreOffice at similar scaling factors

Other things I've tried:

• GDK_DPI_SCALE adjusts scaling of entire application, but blurry scales are still blurry.

Reproduction steps

See display resolutions and relative scaling settings in description

System info and config

• kernel 6.15.7
• hyprland 0.50 (-DNO_XWAYLAND:STRING=true)
• gtk3 3.24.49
• sway 1.11 (Native Wayland)
• wlroots 0.19 (Vulkan Backend) (-Dxwayland=disabled)

Config attached:

hypr-conf.txt

[tekstryder]

I reproduced this at the various "bad" scaling factors with Hyprland 0.50.1.

Please let me know if there's any further information I can provide.

Currently building a patched LO to see if I can put another workaround in place.

$ hyprctl version
Hyprland 0.50.1 built from branch  at commit 4e242d086e20b32951fdc0ebcbfb4d41b5be8dcc  ([gha] Nix: update inputs).
Date: Sat Jul 19 21:37:06 2025
Tag: v0.50.1, commits: 6291
built against:
 aquamarine 0.9.2
 hyprlang 0.6.3
 hyprutils 0.8.1
 hyprcursor 0.1.12
 hyprgraphics 0.1.5


flags set:
no xwayland

EDIT:

I needed an upstream fix to allow the LO GTK4 backend to launch on native Wayland.
That also does not have this scaling issue, so I've added it to the OP as another workaround.
However, each of the alternate LO back-ends are sub-optimal due to low performance / scrolling issues (not Hypr-related).

[tekstryder]

Reproduced using nouveau to rule out the nVidia proprietary driver.

• kernel 6.15.7
• mesa 25.1.6

As mentioned in the OP, this issue is not present with sway or mutter.

I realize this is somewhat niche/esoteric given that the issue only manifests when two displays are using different scaling factors.

[tekstryder]

Ugh... it was the borders.

border_size = 0 and the issue is gone.

How I'd not tried that yet is beyond me. D'oh!

[vaxerski]

it still shouldn't do that... odd.

[tekstryder]

Yeah that's why I left this open ;) But at least root cause configuration is found. Was driving me nuts haha.

If you ever want to look into it further... to reproduce, the monitor/scaling settings must be applied prior to launching the LibreOffice instance.

[tekstryder]

Well now I can reproduce this with or without borders. Wth.

I'll pretend this issue doesn't exist and use one of the "good" scaling (1.33 : 1.07) combos instead of the desired 1.25 : 1.00.

[Weltspear]

It seems that I had similar issues and as of now everything works properly.

[tekstryder]

How similar?

I reproduced again with the recently released LO 25.8.1.

Still blurry with 1.25:1.00 scalings.

hyprctl version

$ hyprctl version
Hyprland 0.50.1 built from branch makepkg at commit 4e242d086e20b32951fdc0ebcbfb4d41b5be8dcc dirty ([gha] Nix: update inputs).
Date: Sat Jul 19 17:37:06 2025
Tag: v0.50.1, commits: 6291
built against:
 aquamarine 0.9.4
 hyprlang 0.6.3
 hyprutils 0.8.4
 hyprcursor 0.1.13
 hyprgraphics 0.1.5


flags set:
no xwayland

[tekstryder]

This is still an issue with hyprland v0.51.0.

Not that I expected differently, only hoping some random render commit may have got this one fixed too.

Hyprland 0.51.0 built from branch makepkg at commit 46174f78b374b6cea669c48880877a8bdcf7802f dirty (version: bump to 0.51.0).
Date: Wed Sep 10 08:41:05 2025
Tag: v0.51.0, commits: 6418
built against:
 aquamarine 0.9.4
 hyprlang 0.6.3
 hyprutils 0.8.4
 hyprcursor 0.1.13
 hyprgraphics 0.1.5


flags set:
no xwayland

[tekstryder]

This pesky little anomaly is still present with hyprland v0.52.1.

[japhir]

I also ran into this with a second monitor scaled at 2 or 3:

monitor=,preferred,auto,1 # default
monitor = desc:Samsung Electric Company SAMSUNG 0x01000000, preferred, auto-up, 2

this is on a laptop with integrated intel graphics