OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
wayland-compat low common DISPUTE

Fix Spotify drawing at double size or cut off on a 1x monitor

omarchyarchhyprlandwaylandxwaylandhidpi
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Issues 11175 and 7153 support the mechanism: 11175's body and a comment from a 4.0.4-1 user describe GDK_SCALE=2 against a 1x monitor scale with force_zero_scaling, the top-left-quadrant clipping, and the env -u GDK_SCALE spotify --force-device-scale-factor=1 desktop entry. 7153 documents the mapfile one-arg-per-line trap, and the AUR spotify.sh is byte-identical to /usr/bin/spotify here. monitors.lua does seed local omarchy_gdk_scale = 2. Two defects. First, Omarchy's Super+Shift+M binding runs omarchy-launch-spotify, which execs /usr/bin/spotify directly through uwsm-app and never reads a .desktop file, so both desktop-entry fixes do nothing for the main way Omarchy users open Spotify. Second, Spotify comes from the omarchy repository (pacman -Si shows Repository: omarchy, installed by omarchy-install-service-spotify via omarchy-pkg-add), not the AUR, though it carries the AUR wrapper. The Arch wiki also documents --force-device-scale-factor in spotify-flags.conf, which reaches every launch path. Not exercised: running Spotify.

The cause above was rewritten on 2026-10-05 to match this note; the fix was corrected by the audit itself.

Symptom

Spotify opens with everything twice as large, or only the top-left quarter of its interface is drawn and the rest is cut off at the window edge. On a laptop with an external monitor it is right on one screen and wrong on the other. hyprctl clients -j shows "xwayland": true for it. A flag added to ~/.config/spotify-flags.conf seems to have no effect.

Cause

Spotify is a CEF (Chromium Embedded Framework) app and on Omarchy it runs under XWayland (issue omarchy#11175 shows its GPU process with --ozone-platform=x11). Omarchy sets xwayland.force_zero_scaling = true and seeds ~/.config/hypr/monitors.lua with local omarchy_gdk_scale = 2, while the monitor scale is computed separately. When the monitor resolves to scale 1, the compositor does not scale XWayland clients and GDK_SCALE=2 tells CEF to draw at 2x, so the UI is oversized, and reporters on omarchy#11175 also saw the surface allocated at 2x inside a 1x window, which clips it. XWayland has one global scale, so on mixed-DPI setups no value is right for every screen. Omarchy installs the spotify package from its own omarchy repository, which ships the AUR wrapper /usr/bin/spotify. That wrapper reads ~/.config/spotify-flags.conf with mapfile, one argv element per line, so two flags on one line arrive as a single argument that Chromium ignores (omarchy#7153). Omarchy's Super+Shift+M runs omarchy-launch-spotify, which starts /usr/bin/spotify directly and does not read any .desktop file.

Fix

Put flags in ~/.config/spotify-flags.conf, one per line. That file is read by /usr/bin/spotify on every launch path, including Omarchy's Super+Shift+M (omarchy-launch-spotify), which bypasses desktop entries.

**Option 1, run Spotify natively on Wayland** (per-monitor scaling, the better fix on mixed DPI), as tested on omarchy#11175:


printf '%s\n' '--ozone-platform=wayland' >> ~/.config/spotify-flags.conf

The Arch wiki notes that some Spotify builds also need DISPLAY unset to come up on Wayland. If it still starts on XWayland, test once from a terminal with env -u DISPLAY spotify. To make that stick for launcher starts, use a desktop entry:


cp /usr/share/applications/spotify.desktop ~/.local/share/applications/
sed -i 's|^Exec=spotify|Exec=env -u DISPLAY spotify|' ~/.local/share/applications/spotify.desktop

That entry does not affect Super+Shift+M. For the keybinding, rebind it in ~/.config/hypr/bindings.lua to run env -u DISPLAY spotify instead.

On Wayland the window class changes from Spotify to spotify, so any of your own window rules that match the capitalised class need updating. Omarchy's omarchy-launch-spotify matches case-insensitively and is unaffected.

**Option 2, stay on XWayland but stop the 2x.** Pin CEF's scale in the flags file, which covers every launch path:


printf '%s\n' '--force-device-scale-factor=1' >> ~/.config/spotify-flags.conf

Use the factor that matches your monitor scale. The tested fix on omarchy#11175 also strips GDK_SCALE for Spotify only. That cannot go in the flags file, so it needs a desktop entry (launcher starts only):


# ~/.local/share/applications/spotify.desktop, Exec line
Exec=env -u GDK_SCALE spotify --force-device-scale-factor=1 --uri=%u

This keeps GDK_SCALE=2 for GTK apps that want it.

With spotify-launcher instead of the spotify package, flags go in ~/.config/spotify-launcher.conf under extra_arguments, not in spotify-flags.conf.

Quit Spotify fully (it keeps running in the tray) and start it again.

Verify

Start Spotify with Super+Shift+M. hyprctl clients -j | jq -r '.[] | select(.class|test("spotify";"i")) | "\(.xwayland) \(.size)"' shows false for option 1. The whole interface fits the window in either option. spotify started from a terminal prints User flags: followed by your flags, each as a separate word.

Sources

spotify-oversized-or-clipped-on-xwayland