https://bugzilla.redhat.com/show_bug.cgi?id=858980
--- Comment #1 from Mike FABIAN mfabian@redhat.com --- Created attachment 616716 --> https://bugzilla.redhat.com/attachment.cgi?id=616716&action=edit ibus-typing-booster-setup-enabled.png
As the screenshot shows, the setup button becomes enabled if one adds a desktop file "ibus-setup-en_US.desktop", which I did by creating a symbolic link:
ibus-setup-en_US.desktop -> ibus-setup-typing-booster.desktop
[root@localhost applications]# cat ibus-setup-typing-booster.desktop [Desktop Entry] Name=IBus Typing Booster Setup Comment=Set ibus-typing-booster Preferences Exec=/usr/libexec/ibus-setup-typing-booster Icon=/usr/share/ibus-typing-booster/icons/ibus-hunspell-table.svg NoDisplay=true Type=Application StartupNotify=true [root@localhost applications]#
So one would need to create many symbolic links for the many different languages ibus-typing-booster supports. Symlinks because the contents would all be identical, there is only one setup application /usr/libexec/ibus-setup-typing-booster for all of them.
The same problem occurs for the m17n input methods:
gnome-control-center searchs for files like
ibus-setup-m17n:t:latn-post.desktop
i.e. different files for all the input methods from m17n although all of them have the same setup application ā/usr/libexec/ibus-setup-m17nā.
I think instead of creating all these symbolic links, it is probably better to improve function
static GDesktopAppInfo * setup_app_info_for_id (const gchar *id) { GDesktopAppInfo *app_info; gchar *desktop_file_name;
desktop_file_name = g_strdup_printf ("ibus-setup-%s.desktop", id); app_info = g_desktop_app_info_new (desktop_file_name); g_free (desktop_file_name);
return app_info; }
from gnome-region-panel-input.c and make it find the correct .desktop file.