You are not logged in.
Hi there,
because i have two screens with different resolution and different scaling, i have to use chromium with wayland, otherwise i am unable to read anything on my second 4K screen.
But if i enable wayland, IME (ibus) no longer works. If i use chromium with gtk4, this issue is solved, but then the @-key no longer works.
Does anyone found a fix for this? I was able to make everything in Chromium work except the '@' Key... no idea why this key. I googled for it and found countless people with the same issue but not one single person with an solution, so this is my last resort
These are my chromium flags
--enable-features=VaapiVideoDecodeLinuxGL
--ozone-platform=wayland
--gtk-version=4
//EDIT: I just noticed that the Alt Gr Key doesn't work at all, no matter what key. This key is just dead in chromium and hence @ also doesn't work.
Last edited by Vamp898 (2024-02-27 15:36:04)
Offline
What "wayland" specifically, how is the keyboard configured and does altgr work in https://archlinux.org/packages/extra/x86_64/gtk4-demos/ ?
Offline
What "wayland" specifically, how is the keyboard configured and does altgr work in https://archlinux.org/packages/extra/x86_64/gtk4-demos/ ?
Oh sorry, its a standard GNOME Desktop with currently no extensions enabled.
The @ key works as expected in the gtk4-demos, everywhere else in GNOME and in Firefox
I am currently using two Keyboard Layouts i switch back and forth
German (E2)
日本語 (Mocz:あ)
I tired with both layouts, no difference
Last edited by Vamp898 (2024-02-27 15:47:05)
Offline
https://issues.chromium.org/issues/40239118 but that's supposed to be fixed, however chromium seems to have a bit of a history here…
https://issues.chromium.org/issues/40231794 (2012)
https://groups.google.com/a/chromium.or … nY12Ox5vFg (2013)
Maybe they simply fudged it again.
Does it even make a difference if you disable the IM?
Offline
https://issues.chromium.org/issues/40239118 but that's supposed to be fixed, however chromium seems to have a bit of a history here…
https://issues.chromium.org/issues/40231794 (2012)
https://groups.google.com/a/chromium.or … nY12Ox5vFg (2013)Maybe they simply fudged it again.
Does it even make a difference if you disable the IM?
Tried disabling IM, no difference. So there seems to be no relation to using IM.
https://issues.chromium.org/issues/327158031
Last edited by Vamp898 (2024-02-27 16:29:34)
Offline
Mozc is only via ibus, the hardware keyboard is a german qwertz (w/ AltGr and an "ß")?
Did you do anything like https://wiki.archlinux.org/title/mozc#U … se_systems and can you try to run the entire gnome session on the german layout only (not just disable the IM for chromium)?
(The idea being that chromium gets "confused" when guessing the layouts and neither jp nor us-qwerty have an iso level3 shift, aka AltGr, key)
Offline
Mozc is only via ibus, the hardware keyboard is a german qwertz (w/ AltGr and an "ß")?
Did you do anything like https://wiki.archlinux.org/title/mozc#U … se_systems and can you try to run the entire gnome session on the german layout only (not just disable the IM for chromium)?(The idea being that chromium gets "confused" when guessing the layouts and neither jp nor us-qwerty have an iso level3 shift, aka AltGr, key)
Exactly, mozc is only via ibus. The Hardware Keyboard is an German (ANSI) Keyboard with qwertz layout and an ß and äöü and so on^^ The only key missing is the one left of Y (which is why i am using E2) so to type an pipe, i have to type Alt Gr + [^] (which is working fine)
I configured the keyboard layouts only via the GNOME interface, nothing else. So all i did was install the corresponding ibus package and then added the layout via the GNOME Tool.
For the test, i removed the Japanese Keyboard layout and killed the ibus-daemon, so IM was no longer available anywhere including any other GNOME applications. No Change to chromium sadly.
Offline
You could test the behavior of the gtk4 backend under weston/sway (I assume there's no issue w/ an X11 session?) and a fresh user on gnome to rule out any local config problems and then probably will have to file a bug upstream - given the history, it's not implausible that this is a frequent bug in chromium.
Offline
You could test the behavior of the gtk4 backend under weston/sway (I assume there's no issue w/ an X11 session?) and a fresh user on gnome to rule out any local config problems and then probably will have to file a bug upstream - given the history, it's not implausible that this is a frequent bug in chromium.
I have not tested with X11 but tested the other things, without success. I'll try with X11 but i am pretty sure this is an upstream issue. As you mentioned, it is not the first time. I am wondering what exactly they are doing upstream that, more or less, regularly causes Chromium to no longer recognize the Alt Gr key... we'll see.
Offline
Apparently it's re-interpreted as Alt+Ctrl because of windows, but the last instance was actually a bug in gtk4
Offline