# Aurora IBus Wayland doesn't work in Chrome

**URL:** https://universal-blue.discourse.group/t/aurora-ibus-wayland-doesnt-work-in-chrome/3432
**Category:** Bluefin
**Created:** [August 7, 2024, 3:10am UTC](https://universal-blue.discourse.group/t/aurora-ibus-wayland-doesnt-work-in-chrome/3432 "2024-08-07T03:10:16Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![mel226](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/mel226/32/1577_2.png) [@mel226](https://universal-blue.discourse.group/u/mel226)
#### Post date: [August 7, 2024, 12:23pm UTC](https://universal-blue.discourse.group/t/aurora-ibus-wayland-doesnt-work-in-chrome/3432/2 "2024-08-07T12:23:35Z")

</div>

Since you’re on Aurora (KDE), can you try running this via the terminal: `flatpak run org.chromium.Chromium --enable-wayland-ime --gtk-version=4` and see if it works then? (If `--gtk-version=4` doesn’t work, maybe try `--gtk4`). If it works, you can add them to the Chromium config file, like so:

```auto
~/.var/app/org.chromium.Chromium/config 
> cat chromium-flags.conf
## enable wayland & hardware acceleration
--ozone-platform-hint=auto
--enable-features=VaapiVideoDecodeLinuxGL,WebRTCPipeWireCapturer
## input method
--enable-wayland-ime
--gtk-version=4

```

If it doesn’t work, you might want to try Fcitx5 instead of ibus. According to [this](https://discussion.fedoraproject.org/t/is-it-really-impossible-to-make-ibus-fcitx5-work-with-chromium-browsers-running-natively-on-wayland/126217/3) Fcitx5 input switching should work fine with Chromium (and most likely Electron apps) if you’re using KDE. (It doesn’t work yet in GNOME, unfortunately).

---

_[View the full topic](https://universal-blue.discourse.group/t/aurora-ibus-wayland-doesnt-work-in-chrome/3432)._