FS#75766 - [chromium] Dead keys don't work on Wayland

Attached to Project: Arch Linux
Opened by Júlio Dutra (dutrajulio) - Wednesday, 31 August 2022, 20:28 GMT
Last edited by Evangelos Foutras (foutrelis) - Tuesday, 27 September 2022, 18:25 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Dead keys doesn't works on the latest version of Chromium web browser

Additional info:
* Version: 105.0.5195.52-1
* There is a similar bug in upstream however is related to OS variant, not browser, of Chromium (https://bugs.chromium.org/p/chromium/issues/detail?id=1351723#c_ts1661958841)

Steps to reproduce:
- Open Chromium in a system with locale "pt_BR.UTF-8" and keyboard as "Portguese (Brazil)"
- Try to use dead keys to input characters like á, ã, é, ê, ó

As workaround i downgraded to version 104.0.5112.101-1
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Tuesday, 27 September 2022, 18:25 GMT
Reason for closing:  Fixed
Additional comments about closing:  Should be fixed with today's Chromium 106 release. Please re-open if the issue persists.
Comment by Evangelos Foutras (foutrelis) - Thursday, 01 September 2022, 15:39 GMT
Can't reproduce the issue on Xfce. Dead keys work fine with both Greek and Brazilian Portuguese layouts.

What desktop environment / window manager are you seeing this with?
Comment by Júlio Dutra (dutrajulio) - Thursday, 01 September 2022, 16:42 GMT
Wayland + GNOME 42.4

chromium-flags.conf
--enable-gpu
--enable-features=UseOzonePlatform
--ozone-platform=wayland
Comment by Evangelos Foutras (foutrelis) - Thursday, 01 September 2022, 18:53 GMT
Based on the info from [1] it's likely reproducible only on Wayland. The error from that upstream issue matches the one quoted in [2].

Since it's reproducible with regular Chrome as well, it will likely get fixed sooner or later (assuming it gets some attention from upstream).

[1] https://crbug.com/1346881
[2] https://www.reddit.com/r/archlinux/comments/x38rwm/
Comment by Johannes Löthberg (demize) - Tuesday, 06 September 2022, 14:30 GMT
This also breaks compose key functionality. But installing gtk4 and making Chromium use gtk4 instead of gtk3 works around that.

Loading...