Dennis HilkLinux Fix LabDE

Desktop, X11 & Wayland

Plasma applications have unexpected display scaling

Different output scale settings and Qt overrides can multiply application scaling. Compare native output settings with the app’s launch environment.

Editorial source review: Start with the evidenceShare this guide
On this page
  1. Symptoms & scope
  2. Possible causes
  3. Diagnose safely
  4. Evidence-guided next steps
  5. References & review
  6. Related problems

Symptoms & scope

  • Only certain applications appear twice as large.
  • Moving an app between displays changes size or sharpness unexpectedly.

Relevant environment

Plasma with mixed-resolution displays; native Wayland, Xwayland and X11 apps can follow different scaling paths.

Possible causes

These are possible explanations, not a confirmed diagnosis. Several independent faults can coexist.

  • A Qt scale override may multiply the compositor’s native scale factor.
  • Per-output settings or an application’s Xwayland behavior may differ.

Diagnose safely

Run one command at a time in the relevant session. Read the explanation first. Uppercase placeholders need your own values; tools and privileges vary by distribution. These commands are displayed here and never executed by the website.

Check 1

Queries output names, modes and scale without setting display configuration; run in the Plasma session.

kscreen-doctor -o

Interpret the result: Compare Scale for the affected output and verify its resolution. A native scale of 1.5 and an app-specific factor of 2 can produce an effective factor of 3.

Check 2

Read from the affected app’s launch context; toolkit-specific overrides may not be present in a different terminal.

printenv QT_SCALE_FACTOR QT_SCREEN_SCALE_FACTORS QT_FONT_DPI GDK_SCALE GDK_DPI_SCALE XDG_SESSION_TYPE

Interpret the result: A global Qt factor or forced font DPI can explain app-only differences. Empty output does not rule out app settings or Xwayland-specific scaling.

Evidence-guided next steps

Remove a redundant application scale override

If the app inherits an unintended Qt/GDK factor, save its launcher environment and remove only the extra factor for that application. Close and reopen it so it can use the desktop’s native scale. Leave other toolkit settings intact.

Precautions: Qt’s QT_SCALE_FACTOR multiplies native scaling; setting it to 1 does not force a native 200% screen to 100%.

Recovery / rollback: Restore the saved per-application factor and relaunch if the override was intentionally required.

Did this solution help you?

Share this solution#

Adjust the intended output’s native scale

If every native app is wrong on one output, record the current display settings and adjust only that output’s scale in Plasma Display Configuration. Keep its resolution and refresh rate unchanged for this comparison, then assess the affected app across displays.

Precautions: Fractional scaling and Xwayland rendering can affect sharpness independently of size. Do not delete the entire display profile as a first step.

Recovery / rollback: Restore the recorded output scale in Display Configuration; use the settings dialog’s revert option if the display becomes unusable.

Did this solution help you?

Share this solution#

References & review

This guide was prepared from primary project or distribution sources and reviewed on the date shown. This is an editorial source check, not evidence that a fix was reproduced on your hardware. Diagnostic log examples are synthetic fixtures. Version-dependent details must be checked against your installed release.