vscode: Blurry UI on Wayland + GNOME 200% scaling

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.82.0
OS Version: Arch Linux (rolling) + Wayland (v1.22.0)

Steps to Reproduce:

Run a Linux distribution + Wayland + GNOME
Set display scaling to 200%
Launch VS Code (with or without --ozone-platform-hint=auto)
Observe the UI is blurry

I am running this on a 4K (3840 x 2160) monitor with 200% scaling configured in the GNOME display settings. I also observed the following warnings that may or may not be relevant here.

[7962:0908/080844.064895:WARNING:wayland_surface.cc(165)] Server doesn't support zcr_alpha_compositing_v1.
[7962:0908/080844.064905:WARNING:wayland_surface.cc(180)] Server doesn't support overlay_prioritizer.
[7962:0908/080844.064908:WARNING:wayland_surface.cc(194)] Server doesn't support surface_augmenter.
[7962:0908/080844.064911:WARNING:wayland_surface.cc(209)] Server doesn't support wp_content_type_v1
[7962:0908/080844.064913:WARNING:wayland_surface.cc(228)] Server doesn't support zcr_color_management_surface.

About this issue

Original URL
State: closed
Created 10 months ago
Reactions: 26
Comments: 15 (3 by maintainers)

Most upvoted comments

Kind of the same isssue on 1.82.0 with Sway Previously I was launching VS Code like this in order to launch prefectly on wayland+scaling: code --enable-features=UseOzonePlatform --ozone-platform=wayland Now this crashes code and logs are empty, downgraded.

hazzus on Sep 13, 2023

VS Code Version: 1.82.0 Reproduced this on fedora 38 silverblue + wayland + gnome 44 with --ozone-platform-hint=auto.

ghost on Sep 9, 2023

--disable-features=WaylandFractionalScaleV1 will work with tomorrow’s insider, please use that as a workaround until the upstream issue is resolved.

deepak1556 on Sep 22, 2023

Looks like the issue is already tracked in https://bugs.chromium.org/p/chromium/issues/detail?id=1356014

But on chrome it can be fixed with --disable-features=WaylandFractionalScaleV1 flag which is not working with vscode.

Since we maintain a disable list from the application code, it overrides the ones from command line. I will address this so that the flag can be used as workaround in VSCode as well.

deepak1556 on Sep 11, 2023

Same issue here, using Fedora 38 / Wayland / GNOME 44. It happened both with --ozone-platform-hint=auto and --ozone-platform=wayland. This kind of sucks, since Wayland is far more performant than X11, which means I either get blurry text or a bad framerate 😦.

claytonwramsey on Sep 10, 2023

Same problem exists on Chrome 114+ (under gnome’s wayland). But on chrome it can be fixed with --disable-features=WaylandFractionalScaleV1 flag which is not working with vscode.

hummerd on Sep 9, 2023