Description of problem: Enable ibus-indicator extension -> Enable or disable shortkey doesn't work with Hangul Key Version-Release number of selected component (if applicable): 1.4.99.20120304-3.fc17.x86_64 How reproducible: always Steps to Reproduce: 1. gsettings set org.gnome.shell enabled-extensions "['ibus-indicator']" 2. gnome-shell restart 3. Click Hangul Key Actual results: Expected results: Additional info: After disable ibus-indicator extension -> Hangul Key works well.
As you may notice, GTK ibus icon provides Hangul hotkey on ko locale. But the shell ibus icon doesn't work with Hangul hotkey because it seems mutter keybinding requires a modifier key likes Control. So I added a workaround in GTK ibus icon only. Probably this would be difficult to be fixed in F17 release since it's handled out of ibus. We need to fix mutter. The current workaround is to use GTK ibus icon unfortunately.
*** Bug 802054 has been marked as a duplicate of this bug. ***
I investigated this issue. It seems meta_display_add_keybinding() works with one short cut key only but I bus supports multiple shortcut keys. If I assigned Zenkaku_Hankaku only on ibus-setup and removed the shift reverse, I could use Zenkaku_Hankaku key with gnome-shell. The following is the suggested fix: https://github.com/fujiwarat/ibus-gjs/commit/ae5767b24395147d3f29a9945cddb512d1ac6de3
ibus-1.4.99.20120428-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/ibus-1.4.99.20120428-1.fc17
Package ibus-1.4.99.20120428-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ibus-1.4.99.20120428-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-6889/ibus-1.4.99.20120428-1.fc17 then log in and leave karma (feedback).
ibus-1.4.99.20120428-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.