Hi
Noticed that after the upgrade to 25.11 none of the “dead keys” are working in the Swedish layout (GNOME, it works with KDE).
Not a big thing but a bit annoying. I just added the “no dead keys” layout instead but I suspect this is a bug.
Anyone noticed something similar? or any other workaround?
Thanks in advance!
Michael
GNOME, it works with KDE
Uhm, it’s not the first time some XKB layout is broken or doesn’t appear in GNOME, and only GNOME. I’m not sure what’s going on here specifically, but I’m inclined to blame GNOME and not a configuration problem in X.org or Nixpkgs.
1 Like
GNOME people made some changes .
Enable ibus or fcitx5.
opened 05:54AM - 24 Nov 25 UTC
6.topic: nixos
6.topic: GNOME
6.topic: i18n
As the title says, I can't input some characters (such as áéíõã ~ and others) af… ter a recent update to my system nixpkgs version.
I am using the Portuguese keyboard, which, for all of these characters requires two keypresses (one for the accent and the second for the letter - so "é" would be typed as "´" + "e"). Before the update, the app would show an underline after pressing the first character, but now it doesn't show anything. After performing the sequence, only the second character is inserted (e.g. "e" instead of "é"). It's as if the app is not even registering the accent keypress.
I've tested this on some apps. For instance, Google Chrome, VS Code, and COSMIC Text Editor all still work. GNOME's Text Editor, GNOME's File Explorer, GNOME's Launcher Search bar, as well as ghostty, don't work. The results are the same when I test these apps on GNOME and COSMIC DE.
The most recent version of nixpkgs that I tested, and that still works, is 9da7f1c. On the other hand, de21549a840b is the earliest commit I was able to test that manifests this issue.
Changelog entry at https://gitlab.gnome.org/GNOME/gtk/-/commit/40fdcc688fd86b21cf10f6f1898217719de7c6dc#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8
Note: This release makes GTK rely on the Wayland text protocol
for input method support. For compositors without that protocol,
you can manually set GTK_IM_MODULE=simple to get back support for
X11-style compose sequences and dead keys.
I guess this envvar is the other option, but I’m not sure about the follow-on effects.
3 Likes