You are not logged in.
Pages: 1
I've installed ibus for chinese pinyin input. It works in the terminal, but I was unable to get it work on chrome.
Any help is appreciated, happy to provide more debug info also.
I am using gnome and wayland.
$ pacman -Qs ^ibus*
local/ibus 1.5.28-4
Next Generation Input Bus for Linux
local/ibus-libpinyin 1.15.2-2
Intelligent Pinyin engine based on libpinyin for IBus
local/libibus 1.5.28-4
IBus support library
#
# ~/.bash_profile
#
[[ -f ~/.bashrc ]] && . ~/.bashrc
export GTK_IM_MODULE=ibus
export QT_IM_MODULE=ibus
export XMODIFIERS=@im=ibus
chrome://version
Command Line /app/extra/chrome --disable-features=WebAssemblyTrapHandler,DesktopPWAsRunOnOsLogin --gtk-version=4 --flag-switches-begin --ozone-platform-hint=wayland --enable-features=OverscrollHistoryNavigation --flag-switches-end --ozone-platform=wayland --origin-trial-disabled-features=WebGPU
Last edited by archnoob75 (2023-09-10 04:26:28)
Offline
Just use a different browser, Chrome is proprietary and against the free software philosophy. I recommend Librewolf. I can't speak for its Chinese input, but it is better than Chrome.
Offline
https://wiki.archlinux.org/title/Chromi … nd_support suggests that IM works better w/ gtk4, but https://aur.archlinux.org/packages/google-chrome doesn't depend on gtk4 but only gtk3
Is gtk4 installed at all?
nb. that the upstream bug suggests that gtk4 + ozone/wayland crashes chromium, what might affect chrome as well.
Also make sure that chrome isn't using xwayland (despite the switch)
Offline
Thanks for the link. It's a problem with ozone/wayland in chrome indeed. If I don't specify ozone/wayland, ibus is working fine. --gtk-version=4 indeed crashes chrome.
I switched to using firefox.
Offline
Pages: 1