Blurry scaling on Linux Wayland when moving Warp between monitors with differen…

[vikvang]

🤖 Filed automatically by @ozdotdev on behalf of @vikvang1.
Source: https://x.com/vikvang1/status/2053946819911037423

Summary

Warp displays blurry scaling on Linux Wayland when the window is moved between monitors with different DPI/resolution settings.

Problem

When moving Warp between monitors with different resolutions on Linux Wayland, the scaling becomes blurry, indicating improper DPI awareness or scaling factor updates during monitor transitions.

Expected behavior

Warp should detect monitor changes and dynamically adjust scaling to maintain crisp text and UI rendering when moving between monitors with different resolutions.

Actual behavior

Text and UI elements become blurry when Warp is moved between monitors with different resolutions on Linux Wayland.

Reproduction hints

• Set up Linux system with Wayland
• Configure multiple monitors with different resolutions/DPI settings
• Open Warp window on one monitor
• Move Warp window to another monitor with different resolution

Additional context

This issue was reported in response to the Warp announcement about rendering markdown tables, mermaid diagrams, and images in agent responses. Issue reported by @​Yue_5O5 on X. Reference: https:​//x.com/vikvang1/status/2053946819911037423

Source thread

@​warpdotdev: Warp now renders markdown tables, mermaid diagrams, and images in all agent responses. No more stray Markdown formatting to read 👏 https:​//t.co/hrlV7xj2Kv
@​Yue_5O5: @​warpdotdev Blurry scaling issue on Linux Wayland when moving Warp between monitors with different resolutions. https:​//t.co/GL3MLK2SWP

[oz-for-oss]

@vikvang

I'm implementing this issue with no spec context.

You can view the conversation on Warp.

I created a new draft implementation PR for this issue.

Next steps:

• Review the implementation changes in the PR.
• Complete any manual verification needed for this issue before merging.

Powered by Oz

[oz-for-oss]

@vikvang

I'm implementing this issue with no spec context.

You can view the conversation on Warp.

I created a new draft implementation PR for this issue.

Next steps:

• Review the implementation changes in the PR.
• Complete any manual verification needed for this issue before merging.

Powered by Oz

[oz-for-oss]

@vikvang

Here's what I found while triaging this issue:

Thanks for the report. This looks like a Linux/Wayland per-monitor scaling issue, but we need visual evidence and compositor details to confirm whether Warp is failing to apply the output scale change or whether the compositor/GPU backend is involved.

I have a few follow-up questions before I can narrow this down:

1. Can you attach a screenshot or short screen recording showing Warp before and after moving between the two monitors?
2. Which Wayland compositor or desktop environment are you using when this happens?

Reply in-thread with those details and the triage workflow will automatically re-evaluate the issue and update the diagnosis, labels, and next steps.

Maintainer details

I concluded that linux/Wayland per-monitor scaling appears to make Warp render blurry after moving the window between differently scaled displays, but the report needs visual evidence and compositor details before the fix path can be confirmed..

Triage summary

This looks like a Linux/Wayland rendering bug involving per-monitor scale-factor changes when a Warp window moves between displays with different DPI or resolution settings. The current report has a plausible reproduction path but does not include enough environment detail or media to confirm whether Warp is failing to receive/apply a Wayland scale-factor change, whether the compositor is scaling an old surface, or whether a GPU/backend-specific rendering path is involved.

Reproducibility

Medium. The scenario is specific and plausible: run Warp on a Wayland session with two differently scaled displays, then move the window between them and observe blurred text/UI. Confidence is limited because there is no screenshot/video, Warp build, compositor/desktop environment, GPU/backend, or exact monitor scale configuration.

Likely area

• os:linux
• area:ui-framework
• Rendering/windowing code that converts winit window scale and size into Warp scene scale and wgpu surface configuration.

Code pointers

• crates/warpui/src/windowing/winit/event_loop/mod.rs: handles WindowEvent::ScaleFactorChanged, but the current special handling is Windows-only and returns early on other platforms. Resize events mark the surface for reconfiguration separately.
• crates/warpui/src/windowing/winit/window.rs: WindowContext::backing_scale_factor() reads winit::window::Window::scale_factor(), update_size_if_needed() reconfigures the wgpu surface from physical size, and rendering uses the cached surface_size.
• crates/warpui_core/src/core/app.rs and crates/warpui_core/src/presenter.rs: scene building passes window.backing_scale_factor() through layout/paint so glyph rasterization and drawing depend on the current scale factor.
• crates/warpui/src/rendering/wgpu/resources.rs: surface configuration is updated by physical size, not directly by scale-factor events.
• app/src/settings/linux.rs: native Wayland is opt-in unless system.force_x11 is disabled or WARP_ENABLE_WAYLAND=1 is set, which matters for reproduction.

Duplicate check

I checked all open issues with GitHub API pagination and searched for Wayland/scaling/DPI/monitor/display/blurry combinations, plus recently closed issues from the last 7 days. I found related Linux/Wayland issues such as #9836 and #5457, but none that match this exact per-monitor blurry scaling symptom, so I am not marking this as a duplicate.

Question reasoning

1. Can you attach a screenshot or short screen recording showing Warp before and after moving between the two monitors? — The symptom is visual, and media is needed to distinguish blurry compositor scaling from font rasterization, surface-size, or general rendering issues.
2. Which Wayland compositor or desktop environment are you using when this happens? — Wayland scale-factor and fractional-scaling behavior varies by compositor, and this detail materially affects reproduction and routing.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz

[yue-codes]

I am using CachyOS with KDE Plasma (Wayland) and an NVIDIA RTX 4060.

What I was doing:
I was moving the Warp window between two monitors with different resolutions: a 1440p primary monitor and a 1080p secondary monitor.

What I expected to happen:
I expected the terminal UI and text to stay sharp and adjust its scaling factor natively when entering the new monitor.

What actually happened:
The entire interface and text become extremely blurry specifically when I move the window to the 1080p monitor. It appears that the fractional scaling is not being handled correctly by the GPU-accelerated renderer on Wayland when transitioning between these different pixel densities.

1080p

1440p