quake mode issues on plasma, also headless service on startup?

[jg-xyz]

Issue Description

Primary issue:
When using Ghostty with quake mode on Wayland/Plasma the quick term will appear when summoned but the window doesn't fully disappear when the summon button is pressed again and the empty quick term window remains until I click another application window.

initial summon:

pressing the summon button again:

Secondary issue:
Separately, I can't figure out a way to have ghostty start as a background service at launch so I can use the quick term freely after logging in. I'm coming from Yakuake which is obviously built for this workflow but I'd like to move to a better terminal if possible.

Expected Behavior

Primary issue:
The quick term appears when the summon shortcut is pressed and the window disappears when the summon shortcut is pressed again and focus returns to the last used application

Secondary issue:
Ghostty starts as a background service at login and quick term is available for use

Actual Behavior

Primary issue:
after hitting the summon button on after opening the quick term window, the empty quick term window remains on the screen holding the focus

Secondary issue:
after trying different configurations for the service like shown below, the quick term is not available at login

• ghostty --initial-window=false
• ghostty --initial-window=false --gtk-single-instance=true

Reproduction Steps

Primary issue:

1. press the shortcut for toggle-quick-terminal
2. press the shortcut again

Secondary issue:

1. Set the service to start up with the parameters provided
2. Have it not work at login

Ghostty Logs

No response

Ghostty Version

Ghostty 1.3.1

Version
  - version: 1.3.1
  - channel: stable
Build Config
  - Zig version   : 0.15.2
  - build mode    : .ReleaseSmall
  - app runtime   : .gtk
  - font engine   : .fontconfig_freetype
  - renderer      : renderer.generic.Renderer(renderer.OpenGL)
  - libxev        : io_uring
  - kernel version: 6.19.8-pikaos
  - desktop env   : other
  - GTK version   :
    build         : 4.21.5
    runtime       : 4.21.5
  - libadwaita    : enabled
    build         : 1.9.0
    runtime       : 1.9.0
  - libX11        : enabled
  - libwayland    : enabled

OS Version Information

PikaOS 4 (rolling Debian)

(Linux only) Display Server

Wayland

(Linux only) Desktop Environment/Window Manager

KDE Plasma

Minimal Ghostty Configuration

quit-after-last-window-closed = false
quit-after-last-window-closed-delay = 1y
gtk-single-instance = true
gtk-quick-terminal-layer = top
gtk-quick-terminal-namespace = ghostty-quick-terminal
quick-terminal-autohide = true
quick-terminal-space-behavior = move
quick-terminal-keyboard-interactivity = on-demand
quick-terminal-size = 33%,75%

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.

[rhodes-b]

You need global keybinds to use the quick terminal in "headless" mode

[jg-xyz]

my keybinds are global, I've also tried without global with no success

[Corvimae]

I'm also seeing this on Plasma 6.6.2, though for me it renders as just a white box the second time the keybind is pressed.

[jg-xyz]

glad I'm not the only one, are you a light-mode person?

also plz upvote the issue so people don't think I'm crazy

[Corvimae]

yep I'm using light mode, so that would make sense!

[pluiedev]

This is odd. In every other implementation of quick terminal we tell the compositor to hide the window when it, well, should be hidden, and it works just fine. Is this perhaps a KDE-specific regression?

[pluiedev]

Aha. Managed to minimize this down to quick-terminal-autohide = true causing all this. Has nothing to do with light mode either - dark mode can reproduce this just fine. Something is quite fishy here since on Niri you have to hit the toggle thrice to bring the quick terminal back properly, too. I'll file an issue and see if there's something we can do.

[pluiedev]

Created #11679

[notDavid]

Hi there, could someone confirm: that the only workaround currently, is setting quick-terminal-autohide = false? Correct?