This ibus version fails to write some spellings and turns back to English immediately. For example, if I try to write েতা, I write tO, and it immediately turns back to English and becomes O

[HRIDOY-BUZZ]

[archisman-panigrahi]

What are your OS and desktop environment?

[HRIDOY-BUZZ]

What are your OS and desktop environment?

POP!_OS 22.04 DE Gnome 42

[abkarim]

I'm also facing this same problem

os: q4os (Debian based) environment: KDE plasma

[gunnarhj]

Works for me on Ubuntu 22.04: tO -> তো

[abkarim]

It works but I need to restart it every time it crashes, and it crashes after writing 3-5 words of text.

[gunnarhj]

@abkarim: Then your problem is of another nature than the specific problem as reported in this issue, right?

[abkarim]

yes, similar problem but not exactly like this.

[HRIDOY-BUZZ]

I use 2 PC. The problem occurs on different spellings on different pc. One pc can't right tO, another pc can. But that another pc Avro shows issues on different spelling...

[Rafiquzzaman420]

I was having the same issue. But I think this problem is linked to "Language support". On Ubuntu 20.04, this problem occurred to me. After installing the "Language support" or updating it, Avro was working completely fine. Hope this would be helpful.

[gunnarhj]

@Rafiquzzaman420 wrote:

On Ubuntu 20.04, this problem occurred to me. After installing the "Language support" or updating it, Avro was working completely fine.

While I don't think that Language Support itself is involved, Ubuntu's language-selector-gnome package depends on im-config, and that latter tool is highly relevant.

GNOME starts and configures ibus by itself if ibus is installed. But Previously, on both Ubuntu and Debian desktops, we let im-config override the GNOME way to do so. This was true as late as at the release of Ubuntu 20.04.

But then we changed that. The applicable Ubuntu bug is Let im-config back off if IBus on GNOME desktops. Since that bug was fixed as an update of Ubuntu 20.04, im-config no longer does anything when ibus is used on a GNOME desktop. We rather defer to GNOME's way to do it.

There were two significant changes in substance:

1. im-config started ibus via this command:

   /usr/bin/ibus-daemon --daemonize --xim
   

   But GNOME starts it via:

   /usr/bin/ibus-daemon --panel disable --xim
   

   (where the --xim flag is omitted for Wayland sessions).

2. im-config set the GTK_IM_MODULE environment variable, but GNOME does not set that variable.

This makes me think about the command for restarting ibus-daemon if a crash happens. One command often suggested for restarting ibus-daemon is:

ibus-daemon -rxd

But if you are on a GNOME desktop that command is not optimal. On GNOME you can do:

ibus-daemon -rxd --panel disable

or, in case of a Wayland session:

ibus-daemon -rd --panel disable

(i.e. drop the -x aka --xim part).

Hope this would be helpful.

At least it inspired me to write this comment. 🙂