OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
display-monitors medium very-common DISPUTE

Fix Chromium and Electron apps looking soft on a fractionally scaled monitor

omarchyarchendeavouroscachyosmanjarohyprlandwayland
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

The problem and most of the fix are right: ~/.config/chromium-flags.conf and --force-device-scale-factor are documented on the Arch HiDPI/Chromium pages, ~/.config/electron-flags.conf is the documented Arch Electron config file, the slack.desktop Exec-copy pattern is straight off the HiDPI page, and Omarchy's default/hypr/envs.lua really does export ELECTRON_OZONE_PLATFORM_HINT and OZONE_PLATFORM. But the Electron advice is obsolete: the Arch Electron page states --ozone-platform-hint=wayland (removed in Electron 38) and uses --ozone-platform=wayland instead, so --ozone-platform-hint=auto is a dead flag in electron-flags.conf and in the Slack launcher. Two further problems. First, electron-flags.conf is only read by Arch's electron package and NOT by apps that bundle their own Electron (slack-desktop, signal-desktop), which need a per-app ~/.config/<app>-flags.conf or the .desktop edit. Second, hyprctl clients | grep -A2 xwayland prints the lines *after* the xwayland field, so it never shows you which app it is.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.

Symptom

Chrome/Brave/Chromium, VS Code, Slack, Signal, Spotify and Discord look soft, fuzzy or double-scaled on a fractionally scaled monitor (e.g. 150%). Fonts have halos. Native GTK apps next to them look sharp.

Cause

Chromium/Electron apps that fall back to XWayland get bitmap-upscaled by the compositor. Even on native Wayland they follow GTK settings and ignore fractional factors unless told a device scale factor explicitly. Since Electron 38.2 Wayland is the default. Older builds need an ozone hint.

Fix

Omarchy already exports ELECTRON_OZONE_PLATFORM_HINT=wayland and OZONE_PLATFORM=wayland. If an app still uses XWayland or renders blurry, force the scale factor.

Chromium (Arch's package reads this file, and Chromium 140+ is already Wayland by default, so the ozone flag is only needed on older builds):


# ~/.config/chromium-flags.conf
--force-device-scale-factor=1.5
--ozone-platform=wayland

Electron apps built against Arch's electron package:


# ~/.config/electron-flags.conf
--force-device-scale-factor=1.5
--ozone-platform=wayland

--ozone-platform-hint was removed in Electron 38, so use --ozone-platform=wayland. Note that electron-flags.conf is read only by Arch's electron package. Apps that bundle their own Electron (slack-desktop, signal-desktop, Discord) ignore it. Some of those read a per-app file instead, e.g. ~/.config/spotify-flags.conf. For the rest, copy the launcher and edit Exec=:


cp /usr/share/applications/slack.desktop ~/.local/share/applications/
sed -i 's|^Exec=/usr/bin/slack|Exec=/usr/bin/slack --force-device-scale-factor=1.5 --ozone-platform=wayland|' \
  ~/.local/share/applications/slack.desktop
update-desktop-database ~/.local/share/applications

List which clients are actually on XWayland:


hyprctl clients -j | jq -r '.[] | select(.xwayland) | "\(.class)\t\(.title)"'

Verify

hyprctl clients | grep -B4 'xwayland: 1' no longer lists the app, and its UI text is crisp at the fractional scale.

Sources

electron-chromium-blurry-fractional-scale