As the title says, I can't input some characters (such as áéíõã ~ and others) after 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, de21549 is the earliest commit I was able to test that manifests this issue.
As the title says, I can't input some characters (such as áéíõã ~ and others) after 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, de21549 is the earliest commit I was able to test that manifests this issue.