https://bugzilla.redhat.com/show_bug.cgi?id=1730242
fujiwara <tfujiwar(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |needinfo?(pnemade(a)redhat.co
| |m)
--- Comment #2 from fujiwara <tfujiwar(a)redhat.com> ---
(In reply to Parag Nemade from comment #0)
2. reboot or you can ibus restart
(In reply to Parag Nemade from comment #1)
[UPDATE]
So after rebooting machine now, I can use ibus-sayura and also got output
So the description is not accurate?
Th reboot does not cause your issue but `ibus restart` causes your issue?
`ibus write-cache` writes the cache in the local directory.
`ibus list-engine` pulls the engines from ibus-daemon which loads in the local
directory.
I.e. you seems to have the different caches between the container and host.
And I also guess `ibus restart` does not update the PID of the ibus-daemon
because you run `ibus restart` in the container.
I think `ibus restart` does not allow in the container so you need to log out
and in the session again to update the caches in the host directory.
I also guess your desktop is GNOME.
Or a risk way would be to kill ibus-daemon and gnome-shell restart ibus-daemon.
One workaround would be to create a .desktop file of `ibus restart` and click
the menu item from application menu.
--
You are receiving this mail because:
You are on the CC list for the bug.