Description of problem: This might be an issue with the cinnamon keyboard indicator but it would be nice to get it working with ibus IMEs. The gnome config is shared and the IMEs are listed (without symbols rendering) but can't be activated. How reproducible: 100% Steps to Reproduce: 1. start cinnamon session 2. enable ibus with im-chooser 3. add some IME in ibus-setup or gnome-control-center eg Japanese (Anthy) or Chinese (libpinyin) 4. restart desktop to get ibus running fully (seems imsettings not working in cinnamon over gnome-settings-daemon) Actual results: Keyboard applets appears including ibus IMEs from gnome config but their icon symbols are not rendered correctly, and IMEs can't be activated or deactivated from the applet. They can from the ibus applet. Expected results: IME input source selection to work from the keyboard applet indicator.
Created attachment 694402 [details] cinnamon-ibus-anthy.png I noticed this problem as well, here is a screenshot. There is an input method selector thing in the panel which looks similar to the one in gnome-shell. But it doesn’t work. As you can see in the picture, I have selected cangjie3 there, but am actually using ibus-anthy in the gnome-terminal above. There is a second input-method selector thing in the panel, to the left of the date, which shows the anthy icon in the above screenshot. This one actually works.
just to clarify: (In reply to comment #0) > 4. restart desktop to get ibus running fully (seems imsettings not > working in cinnamon over gnome-settings-daemon) This issue fixed in git: https://bitbucket.org/tagoh/imsettings/commits/ed53d92d60b7fc68e7736de5d27dfd65 You can self-backport it for testing :) FWIW I did fresh install and see similar issue. the initial setup for the input source for ibus according to the locale works fine but g-s-d seems not bringing up ibus. even though I tried to run ibus manually, b-s-d seems not communicating with it. dunno why. so switcher doesn't take effects at all I suppose. For a workaround (of this confusion, because ibus itself is working fine with imsettings on Cinnamon - though it would be ideal if g-s-d and ibus works without imsettings on even Cinnamon, but anyway), removing the input sources related to ibus from gnome-control-center simply works, because there are no more input sources on the switcher applet...
I've updated imsettings in git to allow NOT_RUN=cinnamon. so everything can go if we can fix this issue.
The fallback mode needs to be disabled in cinnamon to enable/disable IMEs. And it seems the fallback mode was removed in gnome-settings-daemon HEAD. --- gnome-settings-daemon-3.6.4/plugins/keyboard/gsd-keyboard-manager.c.orig +++ gnome-settings-daemon-3.6.4/plugins/keyboard/gsd-keyboard-manager.c @@ -351,7 +351,8 @@ got_session_name (GObject *ob g_variant_get (variant, "&s", &session_name); - if (g_strcmp0 (session_name, "gnome") == 0) + if (g_strcmp0 (session_name, "gnome") == 0 || + g_strcmp0 (session_name, "cinnamon") == 0 ) manager->priv->session_is_fallback = FALSE; g_variant_unref (variant); Transferring to gnome-settings-daemon. (In reply to comment #0) > from gnome config but their icon symbols are not > rendered correctly, and IMEs can't be activated The renderring issue is caused by cinnamon keyboard/applet.js and please file another bug.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
I still see problems so moving to cinnamon-settings-daemon and f20.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.