You are not logged in.
Hello, I have recently installed Arch for the first time.
I had some issues along the way but was able to figure it out, but there's one thing keeping me awake at night: I can't, for the life of me, understand why '+c = ç everywhere in the system, including Firefox, Konsole, KWrite and any other app where I'm allowed to type, except chrome where it inputs: ć.
I really need some direction to understand what might be causing this
I've configured my keyboard layout to English US with dead keys.
I'm on Wayland + KDE Plasma 6.2.5
I've tried uninstalling and reinstalling Chrome, and at first, that works, but after closing it and opening it again, it goes back to inputting ć.
Any help would be greatly appreciated.
Last edited by Alvarojsr (2025-01-29 17:32:26)
Offline
Offline
Hello! Thanks for the reply.
I've added the following
/usr/share/X11/locale/en_US.UTF-8/Compose
<dead_acute> <s> : "'s"
<dead_acute> <S> : "'S"
<dead_acute> <t> : "'t"
<dead_acute> <T> : "'T"
<dead_acute> <V> : "'V"
<dead_acute> <v> : "'v"and
/etc/environment
GTK_IM_MODULE=cedilla
QT_IM_MODULE=cedillaHere's the results when typing a test on different browsers/KWrite:
Chromium:
Firefox:
Chrome:
KWrite:
As you can see only Chromium and KWrite output the intended words, with the caviat that this was right after a fresh chromium install, doing it now after restarting it it's outputting the same words as Firefox, I'm very confused.
Offline
Added where? That exact block is invalid in ~/.XCompose
And what's the output of "echo $GTK_IM_MODULE"?
Also nb. that the other user included "/usr/share/X11/locale/pt_BR.UTF-8/Compose" - I guess
I've configured my keyboard layout to English US with dead keys.
that's not your desire?
~/.XCompose
include "/usr/share/X11/locale/en_US.UTF-8/Compose"
<dead_acute> <c> : "ç"and leave the IM alone.
Chrome is from the AUR or a flatpak?
Offline
Also nb. that the other user included "/usr/share/X11/locale/pt_BR.UTF-8/Compose" - I guess
The system is in english, that file doesn't do anything apparently, but I tried.
Added where?
I edited "/usr/share/X11/locale/en_US.UTF-8/Compose", changed
<dead_acute> <s> : "ś" to
<dead_acute> <s> : "'s"and so on, changes made there applied to KWrite, but not on Firefox (where <'> + <c> = ç) nor Chrome (where <'> + <c> = ć), both still have ś.
Chrome is from the AUR or a flatpak?
Chrome is from the AUR
what's the output of "echo $GTK_IM_MODULE"?
$ echo $GTK_IM_MODULE
cedillainclude "/usr/share/X11/locale/en_US.UTF-8/Compose"
<dead_acute> <c> : "ç"That didn't make it work unfortunately.
edit:
just tested and on X11 <'> + <c> = ç works on Chrome, but <'> + S,T,V are still botched. Not sure what that might mean
Last edited by Alvarojsr (2025-01-28 15:41:18)
Offline
edited "/usr/share/X11/locale/en_US.UTF-8/Compose", changed
Undo that, do not edit global config file, also reset the IM, resp, try to set it to xim - the cedilla thing is most likely specific to the pt_BR situation (sorry, assumed you're falling into that category since this came up a lot lately)
In chrome, when you enter ctrl+shift+u do you get an underlined "u" that allows you to enter a unicode point?
Offline
Undo that, do not edit global config file
Yeah, I realize now that was probably a bad idea, I just reinstalled libx11 to fix it
In chrome, when you enter ctrl+shift+u do you get an underlined "u" that allows you to enter a unicode point?
Yes it does
Offline
That's not xim (or cedilla) does
killall chrome # think about it before typing that
GTK_IM_MODULE=xim chromechange anything about the situation?
Offline
That's not xim (or cedilla) does
killall chrome # think about it before typing that GTK_IM_MODULE=xim chromechange anything about the situation?
Hello again! Tried that now, ctrl+shift+u still gets me the underlined "u".
Offline
Update: after changing GTK_IM_MODULE=xim, everything works as it should on X11. Still not working on Wayland, a bummer
Offline
Is chrome on wayland a native window or an xwayland client?
https://wiki.archlinux.org/title/Chromi … nd_support
https://wiki.archlinux.org/title/Chromi … er_Wayland
(no idea whether those apply to chrome as well)
Offline
Hello Seth! Thank you so much!!!!! forcing the newer GTK by using --gtk-version=4 fixes the issue and allows chrome to run natively on wayland without messing with the inputs
Thank you a lot for all the help!
Offline
\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
Done, added KDE/WAYLAND to the subject as I assume this will make it easier for people facing something similar to come across this thread.
Thanks again!
Offline