https://bugzilla.redhat.com/show_bug.cgi?id=1730242
Bug ID: 1730242 Summary: unable to see ibus-sayura in Region panel Product: Fedora Version: rawhide Status: NEW Component: ibus Assignee: tfujiwar@redhat.com Reporter: pnemade@redhat.com QA Contact: extras-qa@fedoraproject.org CC: i18n-bugs@lists.fedoraproject.org, shawn.p.huang@gmail.com, tfujiwar@redhat.com Target Milestone: --- Classification: Fedora
Description of problem: On Fedora 30 updated Silverblue system, I layered ibus-sayura package. Then tried to add it via Region panel. I cannot see it listed there.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce: 1. Layer ibus-sayura package 2. reboot or you can ibus restart 3. try to add Sayura input using Region panel
Actual results: There is no entry for Sayura in Region panel
Expected results: It should allow to select Sayura
Additional info: As I did not see Sayura, I executed "ibus write-cache"
Then, I executed [parag@f30sb ~]$ ibus read-cache|grep -i sayura <description>Sayura Component</description> <exec>/usr/libexec/ibus-engine-sayura --ibus</exec> <textdomain>ibus-sayura</textdomain> <path mtime="0" >/usr/share/ibus/component/sayura.xml</path> <name>sayura</name> <longname>Sayura</longname> <description>Sayura Input Method</description>
<icon>/usr/share/ibus-sayura/icons/ibus-sayura.png</icon>
Then, [parag@f30sb ~]$ ibus list-engine|grep -i sayura no output for above command
https://bugzilla.redhat.com/show_bug.cgi?id=1730242
--- Comment #1 from Parag Nemade pnemade@redhat.com --- [UPDATE]
So after rebooting machine now, I can use ibus-sayura and also got output [parag@f30sb ~]$ ibus list-engine|grep -i sayura sayura - Sayura [parag@f30sb ~]$
So, what can be done to have this "ibus write-cache" not to be executed manually?
https://bugzilla.redhat.com/show_bug.cgi?id=1730242
fujiwara tfujiwar@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(pnemade@redhat.co | |m)
--- Comment #2 from fujiwara tfujiwar@redhat.com --- (In reply to Parag Nemade from comment #0)
- 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.
https://bugzilla.redhat.com/show_bug.cgi?id=1730242
Parag Nemade pnemade@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |petersen@redhat.com, | |psatpute@redhat.com Component|ibus |ibus-sayura Assignee|tfujiwar@redhat.com |petersen@redhat.com Flags|needinfo?(pnemade@redhat.co | |m) |
--- Comment #3 from Parag Nemade pnemade@redhat.com --- So we discussed this on IRC and fix is to add %post scriptlet to have cache updated automatically when package gets installed on Silverblue.
https://bugzilla.redhat.com/show_bug.cgi?id=1730242
Parag Nemade pnemade@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Fixed In Version| |ibus-sayura-1.3.2-16.fc31 Resolution|--- |RAWHIDE Last Closed| |2019-07-17 05:36:07
https://bugzilla.redhat.com/show_bug.cgi?id=1730242
Parag Nemade pnemade@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |NEW Resolution|RAWHIDE |--- Keywords| |Reopened
--- Comment #4 from Parag Nemade pnemade@redhat.com --- I updated my F31 Silverblue system and saw that local cache got updated but no system cache file at all. also "ibus read-cache" command does not show Sayura in output.
https://bugzilla.redhat.com/show_bug.cgi?id=1730242
Ben Cotton bcotton@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|rawhide |31
--- Comment #5 from Ben Cotton bcotton@redhat.com --- This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
https://bugzilla.redhat.com/show_bug.cgi?id=1730242
--- Comment #6 from Ben Cotton bcotton@redhat.com --- This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
https://bugzilla.redhat.com/show_bug.cgi?id=1730242
Jens Petersen petersen@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |prigupta@redhat.com Flags| |needinfo?(pnemade@redhat.co | |m)
--- Comment #7 from Jens Petersen petersen@redhat.com --- I believe this is already fixed in ibus, no?
https://bugzilla.redhat.com/show_bug.cgi?id=1730242
Parag Nemade pnemade@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |NEXTRELEASE Flags|needinfo?(pnemade@redhat.co | |m) | Last Closed|2019-07-17 05:36:07 |2020-09-22 09:27:09
--- Comment #8 from Parag Nemade pnemade@redhat.com --- Yes this is fixed now. Just tested in my F33 Silverblue VM and I can add Sayura and use it immediately without any issue.
i18n-bugs@lists.fedoraproject.org
-
bugzilla＠redhat.com