Red Hat Bugzilla – Bug 799571
After restarting ibus, Enable or disable ( with Control+space ) works.
Last modified: 2012-05-06 00:54:54 EDT
Description of problem: After restarting ibus, Enable or disable ( Control+space ) works. Version-Release number of selected component (if applicable): 1.4.99.20120203-3.fc17.x86_64 How reproducible: always Steps to Reproduce: 1. Login in GDM 2. Click Ctrl + space or Hangul key 3. ibus restarts Actual results: Expected results: Additional info: ibus-hangul-1.4.0-3.fc17.x86_64 $ gsettings get org.gnome.shell enabled-extensions ['ibus-indicator@example.com']
Additional info: Errors in Looking Glass Extesion "ibus-indicator@example" had errors: extesion is not compatible with current GNOME Shell and/or GJS ---- gjs-1.31.10-2.fc17.x86_64 gnome-shell-3.3.90-1.fc17.x86_64
Thanks for catching up this. The following is the tentative fixes: --- /usr/share/gnome-shell/extensions/ibus-indicator@example.com/metadata.json.orig +++ /usr/share/gnome-shell/extensions/ibus-indicator@example.com/metadata.json @@ -1,4 +1,4 @@ -{"shell-version": ["3.3.5", "3.3.4", "3.3.3", "3.2", "3.2"], +{"shell-version": ["3.3.90", "3.3.5", "3.3.4", "3.3.3", "3.2", "3.2"], "js-version": ["1.31.10", "1.31.6", "1.31.11", "1.30"], "uuid": "ibus-indicator@example.com", "name": "Input-Method Status Indicator", --- /usr/share/gnome-shell/js/ui/status/ibus/candidatePanel.js.orig +++ /usr/share/gnome-shell/js/ui/status/ibus/candidatePanel.js @@ -51,7 +51,7 @@ StCandidateArea.prototype = { }, _removeOldWidgets: function() { - this.actor.destroy_children(); + this.actor.destroy_all_children(); this._labels = []; this._labelBoxes = []; },
ibus-fbterm-0.9.1-14.fc17, ibus-qt-1.3.1-8.fc17, ibus-handwrite-2.1.4-4.fc17, sunpinyin-2.0.3-4.fc17, ibus-input-pad-1.4.0-7.fc17, eekboard-1.0.5-4.fc17, ibus-skk-1.4.0-3.fc17, ibus-sayura-1.3.1-4.fc17, ibus-rawcode-1.3.1.20100707-7.fc17, ibus-m17n-1.3.3-9.fc17, ibus-hangul-1.4.0-5.fc17, ibus-chewing-1.3.10-3.fc17, ibus-pinyin-1.4.0-14.fc17, ibus-1.4.99.20120304-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/FEDORA-2012-3532/ibus-fbterm-0.9.1-14.fc17,ibus-qt-1.3.1-8.fc17,ibus-handwrite-2.1.4-4.fc17,sunpinyin-2.0.3-4.fc17,ibus-input-pad-1.4.0-7.fc17,eekboard-1.0.5-4.fc17,ibus-skk-1.4.0-3.fc17,ibus-sayura-1.3.1-4.fc17,ibus-rawcode-1.3.1.20100707-7.fc17,ibus-m17n-1.3.3-9.fc17,ibus-hangul-1.4.0-5.fc17,ibus-chewing-1.3.10-3.fc17,ibus-pinyin-1.4.0-14.fc17,ibus-1.4.99.20120304-3.fc17
This issue still happens in ibus-1.4.99.20120304-3.fc17.x86_64.
(In reply to comment #1) > Additional info: > Errors in Looking Glass > Extesion "ibus-indicator@example" had errors: extesion is not compatible with > current GNOME Shell and/or GJS > > ---- > gjs-1.31.10-2.fc17.x86_64 > gnome-shell-3.3.90-1.fc17.x86_64 I think this problem is fixed in ibus-1.4.99.20120304-3 What is difference between this bug and bug 802054 ?
1. Login in GDM. 2. gedit start 3.Click ctrl + space or hangul key No reponse. 4. Click ibus tray icon with left button. empty 5. Click ibus tray icon with right button. Click restart
Did you install the new ibus-hangul? https://admin.fedoraproject.org/updates/FEDORA-2012-3532/
The first Control+Space try to launch each ibus engine so it would take time to enable hangul engine. Or maybe I don't understand your problem. I can use Control+Space after I log into the session.
ibus-fbterm-0.9.1-14.fc17, ibus-qt-1.3.1-8.fc17, ibus-handwrite-2.1.4-4.fc17, sunpinyin-2.0.3-4.fc17, ibus-input-pad-1.4.0-7.fc17, eekboard-1.0.5-4.fc17, ibus-skk-1.4.0-3.fc17, ibus-sayura-1.3.1-4.fc17, ibus-rawcode-1.3.1.20100707-7.fc17, ibus-m17n-1.3.3-9.fc17, ibus-hangul-1.4.0-5.fc17, ibus-chewing-1.3.10-3.fc17, ibus-pinyin-1.4.0-14.fc17, ibus-1.4.99.20120304-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
Created attachment 572967 [details] Bebefore restarting ibus
Created attachment 572969 [details] After restarting ibus Before restarting ibus, No Engine. After restarting ibus, Hangul Engine. --- ibus-1.4.99.20120317-1.fc17.x86_64 ibus-gtk2-1.4.99.20120317-1.fc17.x86_64 ibus-hangul-1.4.0-5.fc17.x86_64 ibus-libs-1.4.99.20120317-1.fc17.x86_64 ibus-gtk3-1.4.99.20120317-1.fc17.x86_64
Candidate patch is here. The order of the arguments is not correct. --- ibus-1.4.99.20120317/ui/gtk3/application.vala.orig 2012-04-13 18:25:28.627564978 +0900 +++ ibus-1.4.99.20120317/ui/gtk3/application.vala 2012-04-13 19:15:14.672724495 +0900 @@ -92,7 +92,10 @@ class Application { Variant parameters) { debug("signal_name = %s", signal_name); m_panel = new Panel(m_bus); - m_panel.set_config(m_config); + + if (m_config != null) { + m_panel.set_config(m_config); + } } private void bus_name_lost_cb(DBusConnection connection, @@ -113,7 +116,9 @@ class Application { Variant parameters) { debug("signal_name = %s", signal_name); string name, new_owner, old_owner; - parameters.get("(sss)", out name, out new_owner, out old_owner); + parameters.get("(sss)", out name, out old_owner, out new_owner); + debug("new_owner has name? %s", (new_owner != "").to_string()); + if (new_owner == "") { m_config = null;
https://github.com/ibus/ibus/commit/75df361698c7be58e33993784f2d6b9b0957fd44
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.