Arch Linux

0BADC0DE

Member

From: Regnum Utriusque Siciliae

Registered: 2018-02-21

Posts: 326

chromium 105+wayland="English (US, alt. intl.)" doesn t work

Since 105.0.5195.52-1 I cannot use my beloved "English (US, alt. intl.)" keyboard layout any more as all dual-stroke characters used by this layout cannot be entered any more.
The dual-stroke initial character are not even taken into account, as if they were not typed.
All other programs, both qt- and gtk-based just work fine, like code, firefox, dolphin etc.
Namely:

• ` (back-quote, for grave-accent letters)

• ~ (tilde, for tilde de la eñe)

• ^ (caret, for circumflex-accent letters)

• '  (single quote, for acute-accent letters)

• " (double quotes, for letters with diaeresis)

simply are not  listened to, as if they were not hit on the keyboard, so not only I cannot enter them in chromium, but I cannot also enter those two-strokes letters allowed by the layout.
Those characters can be entered by hitting ALT-Gr plus the corresponding key (with SHIFT if needed). Dual-stroke accented letters aren't available any more.

I just discovered that by disabling Wayland support in chromium by removing "--enable-features=UseOzonePlatform --ozone-platform=wayland" from the launcher script brings the old behavior back at the cost of using xwayland.
Specifying "--ozone-platform-hint=auto" doesn't help.
Something clearly changed from v104 to v105 in Wayland support.
Mine is just a workaround.
How to I bring back Wayland support and a working "English (US, alt. intl.)" keyboard layout?

With "old style" Wayland support enabled, this is what I get when I hit single-quote in the URL bar:

[28141:28141:0902/151853.938076:ERROR:browser_main_loop.cc(269)] Gdk: gdk_keymap_translate_keyboard_state: assertion 'GDK_IS_KEYMAP (keymap)' failed
[28141:28141:0902/151853.938111:ERROR:browser_main_loop.cc(269)] Gdk: gdk_keymap_add_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed
[28141:28141:0902/151853.938128:ERROR:input_method_context_impl_gtk.cc(122)] Cannot translate a Keyevent to a GdkEvent.
[28141:28141:0902/151854.103803:ERROR:browser_main_loop.cc(269)] Gdk: gdk_keymap_translate_keyboard_state: assertion 'GDK_IS_KEYMAP (keymap)' failed
[28141:28141:0902/151854.103834:ERROR:browser_main_loop.cc(269)] Gdk: gdk_keymap_add_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed
[28141:28141:0902/151854.103849:ERROR:input_method_context_impl_gtk.cc(122)] Cannot translate a Keyevent to a GdkEvent.

Useless to say I don't get any log entry when I disable Wayland support as mentioned earlier.
Using the
I hope this sheds more light on the problem.

Last edited by 0BADC0DE (2022-09-05 06:26:29)

---

Maybe Computers Will Never Become As Intelligent
As Humans. Surely They Won't Ever Become So Stupid.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,841

Re: chromium 105+wayland="English (US, alt. intl.)" doesn t work

It's a bug: https://bugs.chromium.org/p/chromium/is … id=1346881

0BADC0DE

Member

From: Regnum Utriusque Siciliae

Registered: 2018-02-21

Posts: 326

Re: chromium 105+wayland="English (US, alt. intl.)" doesn t work

Current latest release (105.0.5195.102-1) DOESN'T work yet.

I forgot to re-enable the  "--enable-features=UseOzonePlatform --ozone-platform=wayland"  options in the launcher.

AFAIK, also v106 will still have this bug! :-(

Last edited by 0BADC0DE (2022-09-05 06:27:33)

---

Maybe Computers Will Never Become As Intelligent
As Humans. Surely They Won't Ever Become So Stupid.

gabriel144

Member

Registered: 2020-08-25

Posts: 3

Re: chromium 105+wayland="English (US, alt. intl.)" doesn t work

Try to run chromium with the flag --gtk-version=4. That fixes part of the problem (Symbols created with AltGr does not work).

Font: https://bugs.chromium.org/p/chromium/is … 1360070#c6

0BADC0DE

Member

From: Regnum Utriusque Siciliae

Registered: 2018-02-21

Posts: 326

Re: chromium 105+wayland="English (US, alt. intl.)" doesn t work

Nope. Adding --gtk-version=4 to the commandline  doesn't help.
Mine is now 105.0.5195.125-3.

---

Maybe Computers Will Never Become As Intelligent
As Humans. Surely They Won't Ever Become So Stupid.

mrvik

Member

Registered: 2019-12-27

Posts: 2

Re: chromium 105+wayland="English (US, alt. intl.)" doesn t work

Nope. Adding --gtk-version=4 to the commandline  doesn't help.
Mine is now 105.0.5195.125-3.

You need to have the gtk4 package for this to work. Otherwise it silently fall back to gtk3.

Seems it'll be fixed in 106: https://crbug.com/1359676

jaerri

Member

Registered: 2024-05-05

Posts: 2

Re: chromium 105+wayland="English (US, alt. intl.)" doesn t work

I'm still facing this problem in 124. For anyone needing it, adding --enable-wayland-ime along with --ozone-platform=wayland fixed it for me.

Refer to: https://fcitx-im.org/wiki/Using_Fcitx_5 … F_Electron

darkbasic

Member

Registered: 2015-06-22

Posts: 45

Re: chromium 105+wayland="English (US, alt. intl.)" doesn t work

Removing --gtk-version=4 did the trick for me.