Quick terminal (drop down style) spawning with the wrong width in setups with two different resolution monitors

[guillermo-st]

Issue Description

When using the toggle_quick_terminal keybind twice in a monitor at 2560x1440 resolution (show, then hide), then using it twice on a 1920x1080 secondary monitor (show then hide), and then pressing the key a final time on the secondary 1080p monitor, the quick terminal spawns with the wrong width, overflowing into the main monitor and even getting cut off outside the screen limits.

I'm not sure how to diagnostic if this is a KDE Plasma or compositor bug instead.

Expected Behavior

The quick terminal always spawn with the correct size depending on the focused monitor.

Actual Behavior

The quick terminal spawns with the wrong width, overflowing into the main monitor and even getting cut off outside the monitor limits.

here is a video: https://streamable.com/9104sh

Reproduction Steps

1. Set a toggle_quick_terminal keybind for ghostty in your .config/ghostty/config file
2. Press it twice to show it then hide it in a 2560x1440 monitor that's currently focused
3. Press it twice to show it then hide it in a 1920x1080 monitor that's currently focused
4. Press it a final time to show it in the same monitor as step 3. It will appear with distorted width

Ghostty Logs

No response

Ghostty Version

Ghostty 1.2.3

Version
  - version: 1.2.3
  - channel: stable
Build Config
  - Zig version   : 0.14.0
  - build mode    : builtin.OptimizeMode.ReleaseFast
  - app runtime   : apprt.Runtime.gtk
  - font engine   : font.main.Backend.fontconfig_freetype
  - renderer      : renderer.generic.Renderer(renderer.OpenGL)
  - libxev        : io_uring
  - kernel version: 6.18.2-1-default
  - desktop env   : other
  - GTK version   :
    build         : 4.20.2
    runtime       : 4.20.2
  - libadwaita    : enabled
    build         : 1.8.1
    runtime       : 1.8.1
  - libX11        : enabled
  - libwayland    : enabled
➜  ~

OS Version Information

Opensuse Tumbleweed

(Linux only) Display Server

Wayland

(Linux only) Desktop Environment/Window Manager

KDE Plasma 6.5.4

Minimal Ghostty Configuration

keybind = global:F12=toggle_quick_terminal

Additional Relevant Configuration

No response

I acknowledge that:

• I have reviewed the FAQ and confirm that my issue is NOT among them.
• I have searched the Ghostty repository (both open and closed Discussions and Issues) and confirm this is not a duplicate of an existing issue or discussion.
• I have checked the "Preview" tab on all text fields to ensure that everything looks right, and have wrapped all configuration and code in code blocks with a group of three backticks (```) on separate lines.

[gabrielbenedikt]

There is potential directionality in this behaviour.
I tested this on two setups, but only ran into this issue on one of them.

Both are on
KDE Plasma 5.6.4 / Frameworks 6.20 / Qt 6.9.2 / KWin-wayland 6.5.4

The most obvious difference between the two is the screen arrangement. From left to right:

(A) 2160p - 1200p
(B) 1200p - 1440p - 1080p

(0) I'll call the monitors M1-M2-M3 from left to right

Tested on 1.2.3 and tip (c90f47f)

• (A): could not trigger width change
• I only see this behaviour on (B) with M1 bleeding into M2
• Once quick_terminal is over-wide, opening it on M2 brings it back to its standard with (as in OPs post)
• Once quick_terminal is over-wide, opening it on M3 keeps the width (too wide)
• Once quick_terminal is over-wide, opening it on M3 (too wide), then opening it on M2 keeps the width (too wide)

A screencast is worth more than a 100 bulletpoints, so: streamable

If I don't overlook anything, the behaviour seems to be triggered by opening quick_terminal on a lower-resultion display on the left; And it persists as long as you keep going left, with cyclic boundary conditions.

I hope this helps in triaging.

[ksbrar]

Only thing I'll add to this excellent summary is that I have begun to experience the same issue on MacOS (Tahoe, 26.3.1 (a)), seemingly (unless I missed this before?) after updating to Ghostty 1.3+

[jeffbuttars]

Also experiencing the same issue on Linux (CachyOS) with Hyprland