Bug#1121791: gnome-text-editor: Compose key does not work when starting editor via Nautilus
Ralf Jung
post at ralfj.de
Tue Dec 2 21:09:01 GMT 2025
Package: gnome-text-editor
Version: 49.0-1
Severity: important
Dear Maintainer,
Some recent update seems to have broken the compose key. On my system, that is
configured to be caps-lock, and it works fine in every other application I use
(including other GNOME applications) -- except for the GNOME Text Editor. Even
there it used to work fine until maybe a few months ago, but then it got broken
by an update.
Very confusingly, I just realized that if I start the editor from my terminal or
via the gnome-session launcher, compose works fine! But when I double-click a
text file in Nautilus and that opens the editor, it does not work.
There's an upstream bugreport at
<https://gitlab.gnome.org/GNOME/gnome-text-editor/-/issues/823> which however
got closed since apparently, it suffices to install ibus. ibus is installed
here, so there must be something else going on.
Kind regards,
Ralf
-- System Information:
Debian Release: forky/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.17.8+deb14-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gnome-text-editor depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.49.0-2
ii libadwaita-1-0 1.8.1-1
ii libc6 2.41-12
ii libeditorconfig0 0.12.10+~0.17.1-3
ii libglib2.0-0t64 2.86.2-1
ii libgtk-4-1 4.20.3+ds-2
ii libgtksourceview-5-0 5.18.0-2
ii libpango-1.0-0 1.56.3-2
ii libspelling-1-2 0.4.9-1
gnome-text-editor recommends no packages.
gnome-text-editor suggests no packages.
-- no debconf information
More information about the pkg-gnome-maintainers
mailing list