[Linux, KDE Plasma] Window scaling too small

Open
#4,355 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
linux, rust

Research direction

No source file, test, or entry point is identified. Reproduce the scaling difference on Linux with KDE Plasma, comparing Warp with Konsole at the same font settings, then trace the platform-specific scaling behavior. Done means Warp's UI elements and text render at the expected 100% scale.

Written by the indexing model from the issue text.

Description

area:window-tabs-panes bug os:linux ready-to-implement triaged
Discord username (optional)

none

Describe the bug

The scaling of the application (UI elements, text, etc) is too small, definitely not 100%. (See images)

  • Left side: Konsole (Hack Nerd Font 11pts)
  • Right side: Warp (Hack Nerd Font 11 pts)

Screenshot_20240226_211033

Screenshot_20240226_211349

To reproduce
  1. open Warp
  2. observe that UI elements and fonts are smaller than in other applications using the exact same font face and size
Expected behavior

I expect to see Warp UI and font scaling to be at the same level as other applications.

Screenshots

No response

Operating system

Linux

Operating system and version

EndeavourOS

Shell Version

zsh 5.9

Current Warp version

v0.2024.02.20.08.01.stable_02

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

No

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

Yes, this I confirmed this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.