Description of problem: After upgrade of ibus-typing-booster to version 2.0.0-1 the keyboard indicator in gnome-panel disappears. Version-Release number of selected component (if applicable): ibus-typing-booster-2.0.0-1.fc27.noarch.rpm How reproducible: Consistent Steps to Reproduce: 1. dnf update ibus-typing-booster 2. logoff gnome 3. login gnome Actual results: No keyboard indicator is displayed in the system tray. Expected results: The keyboard indicator should be displayed in the system tray. Additional info: FWIW, I have only 2 input sources defined under Region & Language: 1. English (US) 2. English (English - US (Typing Booster)) I only enable the typing booster when I want to type accents (e.g. Português). Workaround: 1. dnf downgrade ibus-typing-booster 2. logoff gnome 3. login gnome
You don’t see the rocket emoji in the gnome panel?: http://mike-fabian.github.io/ibus-typing-booster/images/gnome-select-ibus-typing-booster-in-the-panel.png ibus-typing-booster uses whatever keyboard layout was used before switching to ibus-typing-booster, it does not change the keyboard layout in any way. With ibus-typing-booster < 2.0.0, something like pt-BR or pt-PT was displayed in the Gnome panel because there were more than 70 different ibus-typing-booster engines for different languages. Now there is only one single ibus-typing-booster engine which works for *all* these languages and more. The 🚀 U+1F680 ROCKET character (an emoji) is shown for ibus-typing-booster in the gnome-panel now. Typically, by default, this emoji should be displayed using the "Noto Color Emoji" font and then it should look like in the screenshot I linked to above. If you have setup your system to use a different font for emoji, it could look somewhat different, but it should still look like a rocket. How does it look like in your case?
I'm not on my home pc right now, so I cannot provide a screenshot, but I will gladly do so in about 8 hours. The rocket emoji was not present, nor the drop-down arrow for selection of an "input source". Also, the Super-Space hotkey would not switch between my configured input sources. I verified that the ibus-typing-booster package was the source of the problem by downgrading the package. The selector/indicator re-appeared in gnome-panel after logout-login. I then re-upgraded the ibus-typing-booster to see if maybe it was just a glitch in the installation scripts but after logout-login the selector/indicator was gone again and the hotkey would not work either. I then re-downgraded the ibus-typing-booster and once again, after logout-login, the selector/indicator was present and working and the hotkey (Super-Space) worked as well. Thanks.
Thank you! Can you also please check whether there is anything in the log file? The log file is here: .local/share/ibus-typing-booster/debug.log
Created attachment 1450217 [details] debug.log Sorry about the delay. Here is the debug.log file. Screenshots to follow...
Created attachment 1450218 [details] screenshot from before upgrade ibus-typing-booster.noarch 1.5.33-1.fc27
Created attachment 1450219 [details] screenshot from after upgrade ibus-typing-booster.noarch 2.0.0-1.fc27 Not sure if it is significant, but I also notice that I lost my settings after the upgrade.
(In reply to Gregory Lee Bartholomew from comment #6) > Created attachment 1450219 [details] > screenshot from after upgrade > > ibus-typing-booster.noarch 2.0.0-1.fc27 Ah, I see the reason in that screenshot! See: https://github.com/mike-fabian/ibus-typing-booster/releases Which says: release-notes> Attention, this release merges all engines into one. Therefore, the release-notes> engine names had to change. The old engine names like “German - DE release-notes> (Typing Booster)”, “Hindi - HI (Typing Booster)” don’t exist anymore! release-notes> If one has entries for them in the Gnome Control Center or in release-notes> ibus-setup, one needs to remove these old entries and add the new release-notes> engine name "Other (Typing Booster)”. This is the only release-notes> ibus-typing-booster engine name which exists now, it has merged all release-notes> the features from the more than 75 ibus-typing-booster engines which release-notes> existed before. For the new, single engine, one can easily setup release-notes> multiple input methods and dictionaries with the graphical setup release-notes> tool. A lot more input methods and dictionaries are accessible with release-notes> the graphical setup tool now than before. In your screenshot I see “typing-booster:en_US” still setup in the Gnome control centre. This engine does not exist anymore. If ibus engines disappear, they are not automatically removed from the Gnome control centre, which is probably a good thing, if there is just a temporary problem and the engine comes back later, you don’t want to use your setting in the Gnome control centre. But in this case, the change is permanent, all “typing-booster:xx_YY” where “xx_YY” is a locale name like en_US, en_GB, de_DE, ..., are gone for good. Now there is only one single engine which is just called “typing-booster”. That is much better because the new unified engine supports all the languages and input methods in a single engine. And you can easily add and remove dictionaries and input methods in the setup tool. But you have to add the new engine manually to the Gnome control centre, unfortunately. How to do that is described here: http://mike-fabian.github.io/ibus-typing-booster/documentation.html#adding-gnome I.e. you add the engine “Other (Typing Booster)” in the Gnome control centre now instead of the old “English - US (Typing Booster)” you had before. > Not sure if it is significant, but I also notice that I lost my settings > after the upgrade. Yes, unfortunately the settings are not preserved during the update either. There could have been multiple engines of ibus-typing-booster before the update, possibly with conflicting settings. The important data, i.e. the data learned from your typing, is preserved during the update though.
Ah, I see. So it is not a bug then; I just needed to read the release notes. Sorry for the false alarm. I'll try to close the report out as not a bug... Thanks.
Thank you for testing! Reading the release notes is not obvious if you just do "dnf update". But I didn’t know how to make it more obvious in that case.