Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Spotify is oversized on mixed-DPI setups: ship spotify-flags.conf with --ozone-platform=wayland
Reported by jamers99 · filed Sep 10, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
Summary
Spotify runs on XWayland, so it gets one global scale for every monitor. On a mixed-DPI
setup there's no correct value. Here the laptop wants 1.6 and the two externals want 1.0,
so Spotify is oversized on the externals no matter what GDK_SCALE is set to. Native
Wayland apps don't have this problem — they get each output's scale and re-render when
you drag them across.
Spotify is the app Omarchy installs that's still on XWayland. Chrome and Chromium already
ship --ozone-platform=wayland in their default flags files; Spotify doesn't.
System details
- Omarchy 4.0.3-1, Arch, kernel 6.19.8-arch1-3-surface
- Hyprland 0.56.2-2, UWSM 0.26.7-1
- Spotify 1:1.2.96.518-2 (CEF/Chromium 146), on XWayland
- eDP-1 2400x1600 at scale 1.6; DP-4 and DP-5 both 1920x1080 at scale 1
Reproduction
- Attach a 1x monitor to a machine whose laptop panel is at 1.6.
- Launch Spotify (SUPER+SHIFT+M) and drag it between the two.
- It stays one fixed size. Sized right for one monitor, wrong for the other.
hyprctl clients -j shows "xwayland": true.
Fix
Ship a default spotify-flags.conf, same as the existing chrome-flags.conf andchromium-flags.conf:
--ozone-platform=wayland
--enable-features=WaylandWindowDecorations,WaylandFractionalScaleV1omarchy-install-service-spotify currently just runs omarchy-pkg-add spotify, so
Spotify keeps its upstream X11 default (its GPU process runs --ozone-platform=x11).
Tested here: hyprctl clients -j shows "xwayland": false and Spotify resizes correctly
moving between the 1.6 laptop and the 1.0 externals.
One thing that comes with it: the window class changes from Spotify to spotify, so
anything matching the old capitalised class breaks — see #7700, #7154, #9544.
Side note
Related but separate, and it only matters while Spotify is still on XWayland:bin/omarchy-hyprland-monitor-scaling:92-94 rounds GDK_SCALE to the nearest integer,
which is correct for GTK but not for Chromium, which reads it as a float. At monitor
scale 1.6 that's 2, so CEF apps come out 25% large; at 1.25 it rounds to 1 and they come
out 20% small. Worth a separate issue if you want it fixed for other XWayland apps, but
moving Spotify to Wayland sidesteps it here.
I can send a PR if this looks like the right approach.
View raw text
## Summary Spotify runs on XWayland, so it gets one global scale for every monitor. On a mixed-DPI setup there's no correct value. Here the laptop wants 1.6 and the two externals want 1.0, so Spotify is oversized on the externals no matter what `GDK_SCALE` is set to. Native Wayland apps don't have this problem — they get each output's scale and re-render when you drag them across. Spotify is the app Omarchy installs that's still on XWayland. Chrome and Chromium already ship `--ozone-platform=wayland` in their default flags files; Spotify doesn't. ## System details - Omarchy 4.0.3-1, Arch, kernel 6.19.8-arch1-3-surface - Hyprland 0.56.2-2, UWSM 0.26.7-1 - Spotify 1:1.2.96.518-2 (CEF/Chromium 146), on XWayland - eDP-1 2400x1600 at scale 1.6; DP-4 and DP-5 both 1920x1080 at scale 1 ## Reproduction 1. Attach a 1x monitor to a machine whose laptop panel is at 1.6. 2. Launch Spotify (SUPER+SHIFT+M) and drag it between the two. 3. It stays one fixed size. Sized right for one monitor, wrong for the other. `hyprctl clients -j` shows `"xwayland": true`. ## Fix Ship a default `spotify-flags.conf`, same as the existing `chrome-flags.conf` and `chromium-flags.conf`: ``` --ozone-platform=wayland --enable-features=WaylandWindowDecorations,WaylandFractionalScaleV1 ``` `omarchy-install-service-spotify` currently just runs `omarchy-pkg-add spotify`, so Spotify keeps its upstream X11 default (its GPU process runs `--ozone-platform=x11`). Tested here: `hyprctl clients -j` shows `"xwayland": false` and Spotify resizes correctly moving between the 1.6 laptop and the 1.0 externals. One thing that comes with it: the window class changes from `Spotify` to `spotify`, so anything matching the old capitalised class breaks — see #7700, #7154, #9544. ## Side note Related but separate, and it only matters while Spotify is still on XWayland: `bin/omarchy-hyprland-monitor-scaling:92-94` rounds `GDK_SCALE` to the nearest integer, which is correct for GTK but not for Chromium, which reads it as a float. At monitor scale 1.6 that's 2, so CEF apps come out 25% large; at 1.25 it rounds to 1 and they come out 20% small. Worth a separate issue if you want it fixed for other XWayland apps, but moving Spotify to Wayland sidesteps it here. I can send a PR if this looks like the right approach.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 11:28 UTC