You are not logged in.
I'm using ungoogled-chromium. Since my last upgrade the AltGr key has stopped functioning. This is maddening since I use it a lot to write accented characters like á ó é.
Anyone know anything about this?
Offline
What makes you believe it's the AltGr key itself and not the keyboard layout/IM?
X11, native wayland or xwayland?
What is your keybord layout config? (on X11, "setxkbmap -print -query" - this has limited value in any wayland context)
Do you use an IM (and which)?
Offline
Thanks for your reply.
I think it's a Chromium issue because the AltGr key works in the desired way on every other app including terminals, Firefox, Emacs.
I'm using dwm on X11. Qwerty layout. I don't use an input manager.
$ setxkbmap -print -query
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us+inet(evdev)+terminate(ctrl_alt_bksp)" };
xkb_geometry { include "pc(pc104)" };
};
rules: evdev
model: pc105+inet
layout: us
options: terminate:ctrl_alt_bkspOffline
Add to your ~/.config/chromium-flags.conf
--disable-gtk-imeLast edited by Huru-Ukko (2025-03-03 17:57:21)
Offline
That doesn't work, I'm afraid. Neither does it work as a command line argument.
It did lead me to this though. I tried several options there but to no avail.
https://wiki.archlinux.org/title/Chromium
From there I found two bug reports which seem related. I'll monitor them and report back here if there are any developments.
Offline
The default US layout has not 3rd-level shift, try
setxkbmap -variant intlMakes me wonder how and where and why altgr would work otherwise
Offline
Same here with chromium 135.0.7049.52-1 on GNOME/Wayland. Alt-Gr works everywhere but in Chromium, however the --disable-gtk-ime flag fixes it, thanks @Huru-Ukko ! My chromium-flags.conf is now
--ozone-platform-hint=auto
--use-gl=angle
--use-angle=vulkan
--enable-features=VaapiVideoEncoder,Vulkan,VulkanFromANGLE,DefaultANGLEVulkan,UseMultiPlaneFormatForHardwareVideo,VaapiIgnoreDriverChecks
--disable-gtk-ime(IIRC ozone-platform-hint is required for native Wayland support)
Offline
I was having the same issue but --disable-gtk-ime fixed it.
Offline