Created attachment 1483333 [details] Screenshot showing 'Switch engine to kkc failed' message at console Description of problem: Typing Super-space and Super-space and Enter key to select 'kkc' IME on the switcher window, leads to 'Switch engine to kkc failed' message on the console Version-Release number of selected component (if applicable): ibus-fbterm-1.0.1-6.fc29 fbterm-1.7-15.fc29 kernel-4.18.5-300.fc29 How reproducible: Always Steps to Reproduce: 1. In GRUB menu, type "e" to edit the menu 2. Append 'vga=ask 3' of the line of "...vmlinuz..." to enable a frame buffer and set the runlevel 3 3. Press Ctrl-X to launch Linux 4. Select a screen size - say 1024x768x24 5. Log into the console 6. Run ibus-fbterm on the console shell 7. Type Super-space and Super-space and Enter key to select kkc IME on the switcher window Actual results: Switch engine to kkc failed Expected results: No error or warning message on console Additional info: Please see attachment for 'Switch engine to kkc failed' console message
Created attachment 1483334 [details] Sceenshot wherein typing Super-space causes other IME engine to switch succesfully at console Typing Super-space causes other IME engine (like xkb:us::eng, m17n:mr:inscript, libpinyin, quick, etc.) to switch successfully at console (without any warning/error messages at console)
I think fbterm itself cannot be launched with bug #1625207 and we cannot test ibus-fbterm.
OK, I can run fbterm in standalone machine and I found bug #1625207 is caused with VirtualBox. Now I can reproduce this issue.
Created attachment 1546804 [details] screenshot showing 'Switch engine to kkc failed' with ibus-fbterm-1.0.1-7.fc30
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.