[SOLVED] Compose key has some quirks now

QuickQuokka · 2024-03-15 07:43:46

SOLVED: Simply remove GTK_IM_MODULE="xim" from /etc/environment, and then symlink ~/.XCompose to point to /usr/share/X11/locale/en_US.UTF-8/Compose

Hello fellow Arch users!

For quite a long time, I have been using my right alt key as a compose key with little to no problems.

However, recently, I changed my locale in the KDE settings to Hebrew (Regional Settings > Region & Language > Language > Change Language > Hebrew), but then I changed it back to American English. Now I see that the compose key functionality doesn't work in all apps anymore. For example in Firefox, OnlyOffice, and Element.

Here are some of my locale config files:

/etc/locale.conf:

LANG=en_US.UTF-8
LC_CTYPE=C

/etc/locale.gen:

bg_BG.UTF-8 UTF-8  
en_US.UTF-8 UTF-8  
he_IL.UTF-8 UTF-8  
ja_JP.UTF-8 UTF-8  
ko_KR.UTF-8 UTF-8  
zh_CN.UTF-8 UTF-8

One thing I can confirm is that the right alt key is indeed registered as the multi key (verified by xev).

Last edited by QuickQuokka (2024-03-15 20:13:52)

seth · 2024-03-15 08:28:39

Your locale should™ not matter at all.

Because of KDE: did you change to wayland w/ plasma 6?

Otherwise: do you use an IM that's not XIM?
https://wiki.archlinux.org/title/Input_method

QuickQuokka · 2024-03-15 13:19:08

seth wrote:

Your locale should™ not matter at all.
Because of KDE: did you change to wayland w/ plasma 6?
Otherwise: do you use an IM that's not XIM?
https://wiki.archlinux.org/title/Input_method

Nope. Using XIM afaik, and definitely using X11.

Here's my /etc/environment (excluding comments):

GTK_IM_MODULE="xim"

Last edited by QuickQuokka (2024-03-15 13:19:50)

seth · 2024-03-15 14:16:21

FF seems to respond badly to this?
What if you unset the variable for firefox?
https://bugs.archlinux.org/task/73332

Ftr, none of the affected clients are flatsnapdockontainers?

QuickQuokka · 2024-03-15 16:36:29

seth wrote:

FF seems to respond badly to this?
What if you unset the variable for firefox?
https://bugs.archlinux.org/task/73332
Ftr, none of the affected clients are flatsnapdockontainers?

I have added and removed the parameter MOZ_USE_XINPUT=1, seemingly changing nothing, and yes, I have installed all of my packages with either Pacman or yay, not any sandboxed solution.

seth · 2024-03-15 16:50:53

The plan according to that bug would have been to unset GTK_IM_MODULE

QuickQuokka · 2024-03-15 17:49:42

seth wrote:

The plan according to that bug would have been to unset GTK_IM_MODULE

Umm... It works, but custom sequences I defined in /usr/share/X11/locale/en_US.UTF-8/Compose aren't working.

QuickQuokka · 2024-03-15 17:58:49

GOT IT!

Symlinked ~/.XCompose to /usr/share/X11/locale/en_US.UTF-8/Compose and it worked!

seth · 2024-03-15 18:18:07

You want ~/.XCompose to

include "/usr/share/X11/locale/en_US.UTF-8/Compose"

(and then add your custom stuff there)

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.

Arch Linux

#1 2024-03-15 07:43:46

[SOLVED] Compose key has some quirks now

#2 2024-03-15 08:28:39

Re: [SOLVED] Compose key has some quirks now

#3 2024-03-15 13:19:08

Re: [SOLVED] Compose key has some quirks now

#4 2024-03-15 14:16:21

Re: [SOLVED] Compose key has some quirks now

#5 2024-03-15 16:36:29

Re: [SOLVED] Compose key has some quirks now

#6 2024-03-15 16:50:53

Re: [SOLVED] Compose key has some quirks now

#7 2024-03-15 17:49:42

Re: [SOLVED] Compose key has some quirks now

#8 2024-03-15 17:58:49

Re: [SOLVED] Compose key has some quirks now

#9 2024-03-15 18:18:07

Re: [SOLVED] Compose key has some quirks now

Board footer