Keyboard dead_acute composition stopped working

Draiken · 2021-04-01 20:50:15

Whenever I type <dead_acute> followed by <space> I get an acute accent ´
In all my life this was supposed to generate an apostrophe '.

After years using my setup without issues, today after what I must assume was an update to a package, my keyboard composition changed this behavior.
I checked the list of installed/upgraded packages and couldn't spot any obvious culprits.

I use GDM with Xorg starting i3. Very simple .xinitrc

setxkbmap us intl
exec i3

This is my xkbmap

setxkbmap -print -verbose 10
Setting verbose level to 10
locale is C
Trying to load rules file ./rules/evdev...
Trying to load rules file /usr/share/X11/xkb/rules/evdev...
Success.
Applied rules from evdev:
rules:      evdev
model:      pc105
layout:     us
variant:    intl
options:    Compose
Trying to build keymap using the following components:
keycodes:   evdev+aliases(qwerty)
types:      complete
compat:     complete
symbols:    pc+us(intl)+inet(evdev)
geometry:   pc(pc105)
xkb_keymap {
	xkb_keycodes  { include "evdev+aliases(qwerty)"};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc+us(intl)+inet(evdev)"	};
	xkb_geometry  { include "pc(pc105)"	};
};

This is my X keyboard config

Section "InputClass"
        Identifier "system-keyboard"
        MatchIsKeyboard "on"
        Option "XkbLayout" "us"
        Option "XkbModel" "pc105"
        Option "XkbVariant" "intl"
	Option "XkbOptions" "Compose" # This was set after on another failed attempt to fix this
EndSection

I checked my $LANG and it's en_US.UTF-8, so in theory /usr/share/X11/locale/en_US.UTF-8/Compose should be the file being read for compositions.
However, looking at that file, what I described as the expected behavior is there:

<dead_acute> <space>             	: "'"   apostrophe # APOSTROPHE

So this must not be used for some reason.

I tried creating a new .XCompose file to no success

include "%L"

Tried searching for a solution to this for hours today and couldn't figure out the issue. Right now the only way I can print an apostrophe is to use AltGr+´

Please, any help is appreciated

seth · 2021-04-01 22:19:04

In what context? (Is it limted to specific clients?)
"xev -event keyboard"? xterm?

Do you use an extended input method (fcitx etc.)?

Draiken · 2021-04-02 10:51:52

seth wrote:

In what context? (Is it limted to specific clients?)
"xev -event keyboard"? xterm?
Do you use an extended input method (fcitx etc.)?

This is happening on all text, not just terminal or GUIs.

I don't use any extended input methods AFAICT.

Ran xev -event keyboard and now I'm even more confused:

KeyPress event, serial 28, synthetic NO, window 0x4200001,
    root 0x1eb, subw 0x0, time 1663090, (426,167), root:(3015,1139),
    state 0x0, keycode 48 (keysym 0xfe51, dead_acute), same_screen YES,
    XLookupString gives 2 bytes: (c2 b4) "´"
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: True

KeyRelease event, serial 28, synthetic NO, window 0x4200001,
    root 0x1eb, subw 0x0, time 1663150, (426,167), root:(3015,1139),
    state 0x0, keycode 48 (keysym 0xfe51, dead_acute), same_screen YES,
    XLookupString gives 2 bytes: (c2 b4) "´"
    XFilterEvent returns: False

KeyPress event, serial 28, synthetic NO, window 0x4200001,
    root 0x1eb, subw 0x0, time 1663840, (426,167), root:(3015,1139),
    state 0x0, keycode 65 (keysym 0x20, space), same_screen YES,
    XLookupString gives 1 bytes: (20) " "
    XmbLookupString gives 1 bytes: (20) " "
    XFilterEvent returns: True

KeyPress event, serial 28, synthetic NO, window 0x4200001,
    root 0x1eb, subw 0x0, time 1663840, (426,167), root:(3015,1139),
    state 0x0, keycode 0 (keysym 0x27, apostrophe), same_screen YES,
    XKeysymToKeycode returns keycode: 48
    XLookupString gives 0 bytes: 
    XmbLookupString gives 1 bytes: (27) "'"
    XFilterEvent returns: False

KeyRelease event, serial 28, synthetic NO, window 0x4200001,
    root 0x1eb, subw 0x0, time 1663930, (426,167), root:(3015,1139),
    state 0x0, keycode 65 (keysym 0x20, space), same_screen YES,
    XLookupString gives 1 bytes: (20) " "
    XFilterEvent returns: False

It shows an apostrophe after the combination of <dead_acute> <space>. But typing that on the terminal, browser, etc I don't see an apostrophe!
I do notice that it only shows the KeyPress event, not the KeyRelease. Maybe that's related?
Unfortunately I tested with <dead_acute> <a> and it also only shows a key press event for á (<aacute>), so it must be unrelated

seth · 2021-04-02 11:00:54

echo "<type dead_acute+space>" | od -x  # the quotes are gonna be required in case this backtick is actually a single quote that just looks weird

Also, sanity check:

localectl; locale; locale -a

I don't use any extended input methods AFAICT.

loginctl session-status

bartim · 2021-04-02 15:56:26

This seems to be a bug in GTK 3.24.28, will be fixed in 3.24.29. See here: https://gitlab.gnome.org/GNOME/gtk/-/issues/3807

domx93 · 2021-04-03 10:58:16

bartim wrote:

This seems to be a bug in GTK 3.24.28, will be fixed in 3.24.29. See here: https://gitlab.gnome.org/GNOME/gtk/-/issues/3807

Ok, so we just need to wait, thanks!
In case it can be useful for other people: in the meantime, I'm using AltGr+' to have the '

Arch Linux

#1 2021-04-01 20:50:15

Keyboard dead_acute composition stopped working

#2 2021-04-01 22:19:04

Re: Keyboard dead_acute composition stopped working

#3 2021-04-02 10:51:52

Re: Keyboard dead_acute composition stopped working

#4 2021-04-02 11:00:54

Re: Keyboard dead_acute composition stopped working

#5 2021-04-02 15:56:26

Re: Keyboard dead_acute composition stopped working

#6 2021-04-03 10:58:16

Re: Keyboard dead_acute composition stopped working

Board footer