1.4.0 (GTK): text after a fallback glyph from a proportional font is not drawn

[fadi-labib]

Issue Description

Since updating from 1.3.1 to 1.4.0, text that follows a fallback glyph on the same row is not drawn when the fallback font is proportional. The text is still in the terminal: copying the screen contents returns the full line. It is only missing on screen.

I noticed it in Claude Code, whose search box starts with U+2315 (⌕). JetBrainsMono Nerd Font has no U+2315, so fontconfig falls back to FreeSerif. U+23F5 (⏵) behaves the same way, falling back to FreeSans.

Expected Behavior

⌕ hello world is drawn in full, as it is in 1.3.1.

Actual Behavior

Only ⌕ is visible. hello world is not drawn

Reproduction Steps

1. Use a primary font that lacks U+2315, on a system where fontconfig resolves U+2315 to a proportional font (here FreeSerif from fonts-freefont).
2. Run: printf '⌕ hello world\n'
3. The text after ⌕ is missing. Running the same command in 1.3.1 shows the full line.

Workaround: mapping the range to a monospace font fixes it:

font-codepoint-map = U+2300-U+23FF=FreeMono

Ghostty Version

Ghostty 1.4.0
  - channel: stable
  - build mode    : .fast
  - app runtime   : .gtk
  - font engine   : .fontconfig_freetype
  - renderer      : renderer.generic.Renderer(renderer.OpenGL)
  - GTK version   : 4.22.4 (build and runtime)
  - libadwaita    : 1.9.1

Installed via snap (revision 1016). The previous snap revision 820 (1.3.1) does not have the problem.

OS Version Information

Ubuntu 24.04.5 LTS, kernel 7.0.0-42-generic

(Linux only) Display Server

X11

(Linux only) Desktop Environment/Window Manager

GNOME (ubuntu:GNOME)

Minimal Ghostty Configuration

font-family = JetBrainsMono Nerd Font

Additional Relevant Configuration

fc-match 'JetBrainsMono Nerd Font:charset=2315' → FreeSerif
fc-match 'JetBrainsMono Nerd Font:charset=23F5' → FreeSans

---

AI disclosure: I used Claude Code to narrow this down (comparing the two snap revisions and writing small printf tests) and to draft this report. I reproduced every result myself and edited the text.

I acknowledge that:

• I have reviewed the FAQ and confirm that my issue is NOT among them.
• I have searched the Ghostty documentation and confirm there doesn't exist a configuration option that solves my issue.
• 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.