Some special characters not working with us-intl layout

[iojea]

Issue Description

I am on Arch Linux, with Hyprland and keyboard layout set to:

  kb_layout = us
  kb_variant = intl

Recently Ghostty began to ignore some keys. For example, if I type ~ (Shift + `), nothing is shown. The same happens with " and ' (which I need for accents in Spanish). I think the problem began with v. 1.2.0, but I am not sure. The layout works properly on other programs, including other terminal emulators.

I can produce the desired results by typing Alt + a for á (and the other vocals too), Alt + Shift + ` for ~, Alt + ' for ' and Alt + Shift + ' for ". This only works with the right Alt key. But I am not used to this, so I would rather recover my usual method that was working until recently.

I also work with Ghostty (v. 1.2.0) on a MacBook Air but that works fine.

Expected Behavior

If I type ~ (Shift + `)," (Shift + '), ', I expect ~, ",' to be rendered (respectively).
If I type 'a I expect á to be rendered.

Actual Behavior

Typing ~, ',", nothing is shown (not even a space).
Typing 'a I obtain simply a.

Reproduction Steps

1. Open Ghostty.
2. Type ~, i.e.: Shift + ` or ' or " (Shift + ") or 'a.

Ghostty Logs

Nothing is added to the log when typing the problematic keys. I copy them anyway:


info: ghostty version=1.2.0-arch1
info: ghostty build optimize=ReleaseFast
info: runtime=apprt.Runtime.gtk
info: font_backend=font.main.Backend.fontconfig_freetype
info: dependency harfbuzz=11.5.1
info: dependency fontconfig=21701
info: renderer=renderer.generic.Renderer(renderer.OpenGL)
info: libxev default backend=io_uring
info(os_locale): setlocale from env result=C.UTF-8
info(gtk): GTK version build=4.18.6 runtime=4.20.1
info(gtk): libadwaita version build=1.7.7 runtime=1.8.0
info: reading configuration file path=/home/iojea/.config/ghostty/config
info(config): default shell source=env value=/usr/bin/nu
warning(gtk_ghostty_application): setting GDK_DEBUG=
warning(gtk_ghostty_application): setting GDK_DISABLE=gles-api,vulkan
info(gtk_ghostty_application): cgroup isolation disabled via config=config.Config.LinuxCgroup.single-instance
warning(gtk_ghostty_global_shortcuts): request failed=GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable (2)
info(opengl): loaded OpenGL 4.6
info(font_shared_grid_set): font regular: Noto Sans Mono Regular
info(font_shared_grid_set): font bold: Noto Sans Mono Bold
info(font_shared_grid_set): font italic: Noto Sans Mono Regular
info(font_shared_grid_set): font bold_italic: Noto Sans Mono Bold
info(io_exec): found Ghostty resources dir: /usr/share/ghostty
warning(io_exec): shell could not be detected, no automatic shell integration will be injected
warning(gtk_ghostty_application): unimplemented action=apprt.action.Action.Key.cell_size
info(io_exec): started subcommand path=/bin/sh pid=53548
info(io_exec): subcommand cgroup=-

### Ghostty Version

```text
Ghostty 1.2.0-arch1

Version
  - version: 1.2.0-arch1
  - channel: tip
Build Config
  - Zig version   : 0.14.1
  - 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.16.8-arch2-1
  - desktop env   : other
  - GTK version   :
    build         : 4.18.6
    runtime       : 4.20.1
  - libadwaita    : enabled
    build         : 1.7.7
    runtime       : 1.8.0
  - libX11        : enabled
  - libwayland    : enabled

OS Version Information

Arch Linux

(Linux only) Display Server

Wayland

(Linux only) Desktop Environment/Window Manager

No response

Minimal Ghostty Configuration

font-family= "JuliaMono" 
font-size=12

background-opacity=1.0

unfocused-split-opacity=0.75

window-padding-x=20
window-padding-y=6
theme = "colibri_nord"

quick-terminal-position=top

keybind=global:super+grave_accent=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.

[ItsLemmy]

Can confirm I'm affected too. This used to be a bug in early of version of ghostty and was fixed a long time ago, but it seems to have re-appeared.

This make the terminal pretty much unusable as we can't type any tilde or double quotes symbols.

[pluiedev]

This seems to be a dupe of #8899 - TL;DR upstream (GTK) now relies on the Wayland compositor's text input protocol to handle compose sequences since GTK 4.20, and there's nothing we could do about that.

[tsujigiri]

I'm not sure it's the same issue, but I'm using Sway on Wayland and for me it's the compose key that's not working in Ghostty since the most recent update. It works in other apps and in Ghostty when using Gnome.

Ghostty 1.2.0-arch1

Version
  - version: 1.2.0-arch1
  - channel: tip
Build Config
  - Zig version   : 0.14.1
  - 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.12.49-1-lts
  - desktop env   : other
  - GTK version   :
    build         : 4.18.6
    runtime       : 4.20.1
  - libadwaita    : enabled
    build         : 1.7.7
    runtime       : 1.8.0
  - libX11        : enabled
  - libwayland    : enabled

[pluiedev]

It does sound like #8899, indeed. You can either set the environment variable as suggested there or install a proper IME like iBus to handle dead keys for you.

[rhodes-b]

The the marked answer it applys to both compse and deadkeys.

It also tells you how to fix it.

You are using GTK 4.20 so you are effected by that change

Like stated in the answer if it works or not is going to be compositor specific. If you want it to go back to the previous behavior use the environment variable like stated

[Muramasa500]

I have the same problem. I am using Arch Linux, and Hyprland. And Swedih keyboard.
Can also not write tilde

[rhodes-b]

please read the marked answer