From Ed Greshko: Stuart McGraw wrote:
I asked here a few days ago about ibus which broke after I did a yum update.
No one responded but I saw some other posts about different problems with ibus so I waited until some new updates appeared.
However after upgrading again just now, it is still broken -- still no input editor appears when I type the enable sequence. However now the (new) ibus icon says "no input window" when left-clicked.
Is ibus ever going to work? I write non- english emails everyday and Fedora is useless to me without a working ibus. At this point I wonder if I should blow off Fedora and and just return to Windows?
Working just fine here....
ibus-table-erbi-1.1.0.20090407-6.fc11.noarch ibus-m17n-1.2.0.20090617-2.fc11.i586 ibus-anthy-1.2.0.20090917-1.fc11.i586 ibus-table-cangjie-1.1.0.20090309-12.fc11.noarch ibus-devel-1.2.0.20090927-1.fc11.i586 ibus-table-yong-1.1.0.20090422-7.fc11.noarch ibus-hangul-1.2.0.20090617-2.fc11.i586 ibus-devel-docs-1.2.0.20090927-1.fc11.i586 ibus-table-wubi-1.1.0.20090327-7.fc11.noarch ibus-gtk-1.2.0.20090927-1.fc11.i586 ibus-chewing-1.2.0.20090917-2.fc11.i586 ibus-table-1.1.0.20090610-1.fc11.noarch ibus-sayura-1.2.0.20090703-1.fc11.i586 ibus-table-additional-1.1.0.20090610-1.fc11.noarch ibus-rawcode-1.2.0.20090703-1.fc11.i586 ibus-pinyin-1.2.0.20090915-1.fc11.noarch ibus-table-array30-1.2.0.20090729-1.fc11.noarch ibus-libs-1.2.0.20090927-1.fc11.i586 ibus-1.2.0.20090927-1.fc11.i586
Thanks (to you and also Craig White and Tait Clarridge) for confirming that the problem is likely specific to my machine. Those match the versions I have:
ibus-1.2.0.20090927-1.fc11.i586 ibus-anthy-1.2.0.20090917-1.fc11.i586 ibus-gtk-1.2.0.20090927-1.fc11.i586 ibus-libs-1.2.0.20090927-1.fc11.i586 anthy-9100h-8.fc11.i586 kasumi-2.4-2.fc11.i586
However.... I did "notice" the problem you reported. I didn't do too much investigation. But, may have a solution.
It seemed to me that the problem existed on a "saved session". I'm running KDE and when I logged out/in it brings up the previous windows, including a terminal session. What I did, without really thinking, was to close all open windows, logout and then login. When I did this, all was well.
I'm using Gnome but tried that and also tried a full reboot after the updates but that didn't help. I also "rpm -e" all the packages I listed and reinstalled them.
Last night I updated everything I could see that seemed related to gnome, gtk, pygtk, Xorg, etc., on the theory that there was perhaps some unrecognized dependency on a recent package but it didn't help. (Unfortunately I can't keep everything up to date over a 3KB/s modem connection that rarely runs unattended for more than a couple hours.)
The only other thing I notice is when I run ibus-daemon from a shell with "-v", I see lots of errors like the following that appear when it's started:
(ibus-daemon:21356): IBUS-DEBUG: From ::1.1 to :1.3, Error: org.freedesktop.DBus.Error.Failed : Can not get value [engine/anthy/shortcut/default->on_off] (ibus-daemon:21356): IBUS-DEBUG: From ::1.1 to :1.3, Error: org.freedesktop.DBus.Error.Failed : Can not get value [engine/anthy/shortcut/default->circle_input_mode] ... (ibus-daemon:21356): IBUS-DEBUG: From ::1.1 to :1.3, Error: org.freedesktop.DBus.Error.Failed : Can not get value [engine/anthy/shortcut/wnn->add_word] (ibus-daemon:21356): IBUS-DEBUG: From ::1.1 to :1.3, Error: org.freedesktop.DBus.Error.Failed : Can not get value [engine/anthy/shortcut/wnn->start_setup]
They all have in common a message about not getting a value from engine/anthy/shortcut/<something>. Perhaps these are normal? If not, do they ring a bell with anyone? I don't see any messages when I type the activate sequence (alt-grave) in some window.
FWIW, I saw your earlier query....but since all was working for me and I was unable to update to your level I just didn't answer.
IMHO, people shouldn't threaten to revert to Windows. It just sounds so hyperbolic and makes me think that the person isn't committed to Linux. Almost makes me not want to help them....
In retrospect it did sound a little pissy -- chalk it up to a high level of frustration. But I have to honestly say that I have more commitment to using a system that meets my needs than to FOSS political correctness.
On Fri, 2009-10-02 at 11:26 -0600, Stuart McGraw wrote:
In retrospect it did sound a little pissy -- chalk it up to a high level of frustration. But I have to honestly say that I have more commitment to using a system that meets my needs than to FOSS political correctness.
---- If you want a truly stable system, you should probably be using RHEL or CentOS.
Fedora is much closer to the development edge and a technology such as ibus which is still evolving is probably likely to cause some issues on occasion. It seems to me that your lack of commitment to the FOSS software means that either Fedora isn't the right distribution for you - or you should at least stay with the older version (i.e., Fedora 10 at this stage) to keep a greater distance from the edge where things can break.
Craig
Stuart McGraw wrote:
I'm using Gnome but tried that and also tried a full reboot after the updates but that didn't help. I also "rpm -e" all the packages I listed and reinstalled them.
Last night I updated everything I could see that seemed related to gnome, gtk, pygtk, Xorg, etc., on the theory that there was perhaps some unrecognized dependency on a recent package but it didn't help. (Unfortunately I can't keep everything up to date over a 3KB/s modem connection that rarely runs unattended for more than a couple hours.)
The only other thing I notice is when I run ibus-daemon from a shell with "-v", I see lots of errors like the following that appear when it's started:
(ibus-daemon:21356): IBUS-DEBUG: From ::1.1 to :1.3, Error: org.freedesktop.DBus.Error.Failed : Can not get value [engine/anthy/shortcut/default->on_off] (ibus-daemon:21356): IBUS-DEBUG: From ::1.1 to :1.3, Error: org.freedesktop.DBus.Error.Failed : Can not get value [engine/anthy/shortcut/default->circle_input_mode] ... (ibus-daemon:21356): IBUS-DEBUG: From ::1.1 to :1.3, Error: org.freedesktop.DBus.Error.Failed : Can not get value [engine/anthy/shortcut/wnn->add_word] (ibus-daemon:21356): IBUS-DEBUG: From ::1.1 to :1.3, Error: org.freedesktop.DBus.Error.Failed : Can not get value [engine/anthy/shortcut/wnn->start_setup]
They all have in common a message about not getting a value from engine/anthy/shortcut/<something>. Perhaps these are normal? If not, do they ring a bell with anyone? I don't see any messages when I type the activate sequence (alt-grave) in some window.
As a quick check....what I would do is to create a new user account and see if things work for that new user. This will then tell you if it is simply something that is related to your settings....
Ed
On 10/02/2009 02:20 PM, Ed Greshko wrote:
Stuart McGraw wrote:
I'm using Gnome but tried that and also tried a full reboot after the updates but that didn't help. I also "rpm -e" all the packages I listed and reinstalled them.
Last night I updated everything I could see that seemed related to gnome, gtk, pygtk, Xorg, etc., on the theory that there was perhaps some unrecognized dependency on a recent package but it didn't help. (Unfortunately I can't keep everything up to date over a 3KB/s modem connection that rarely runs unattended for more than a couple hours.)
The only other thing I notice is when I run ibus-daemon from a shell with "-v", I see lots of errors like the following that appear when it's started:
(ibus-daemon:21356): IBUS-DEBUG: From ::1.1 to :1.3, Error: org.freedesktop.DBus.Error.Failed : Can not get value [engine/anthy/shortcut/default->on_off] (ibus-daemon:21356): IBUS-DEBUG: From ::1.1 to :1.3, Error: org.freedesktop.DBus.Error.Failed : Can not get value [engine/anthy/shortcut/default->circle_input_mode] ... (ibus-daemon:21356): IBUS-DEBUG: From ::1.1 to :1.3, Error: org.freedesktop.DBus.Error.Failed : Can not get value [engine/anthy/shortcut/wnn->add_word] (ibus-daemon:21356): IBUS-DEBUG: From ::1.1 to :1.3, Error: org.freedesktop.DBus.Error.Failed : Can not get value [engine/anthy/shortcut/wnn->start_setup]
They all have in common a message about not getting a value from engine/anthy/shortcut/<something>. Perhaps these are normal? If not, do they ring a bell with anyone? I don't see any messages when I type the activate sequence (alt-grave) in some window.
As a quick check....what I would do is to create a new user account and see if things work for that new user. This will then tell you if it is simply something that is related to your settings....
Hadn't thought of that, good idea. Did so, enabled the IME and selected Anthy, but same problem exists in the new account.
Stuart McGraw wrote:
(ibus-daemon:21356): IBUS-DEBUG: From ::1.1 to :1.3, Error: org.freedesktop.DBus.Error.Failed : Can not get value [engine/anthy/shortcut/wnn->add_word] (ibus-daemon:21356): IBUS-DEBUG: From ::1.1 to :1.3, Error: org.freedesktop.DBus.Error.Failed : Can not get value [engine/anthy/shortcut/wnn->start_setup]
They all have in common a message about not getting a value from engine/anthy/shortcut/<something>. Perhaps these are normal? If not, do they ring a bell with anyone? I don't see any messages when I type the activate sequence (alt-grave) in some window.
As a quick check....what I would do is to create a new user account and see if things work for that new user. This will then tell you if it is simply something that is related to your settings....
Hadn't thought of that, good idea. Did so, enabled the IME and selected Anthy, but same problem exists in the new account.
The error messages I've not seen before....nor heard of. Almost sounds as if some other process has reserved the start/stop method. Since a new account would/should start out with a "blank" home directory without any .ibus or .dbus directories it would suggest that the problem is actually external to ibus. I'm going to presume that the .imsettings.log did not reveal anything either.....
You said you were running Gnome. Does the same thing happen under KDE?
Like you said....since it works for others then the problem is unique to your system. Even so, it would be a good idea to file a bugzilla. The developers may not read or pay much attention to this list and with a bugzilla may actually have the answer to your problem.
Ed Greshko wrote:
Stuart McGraw wrote:
(ibus-daemon:21356): IBUS-DEBUG: From ::1.1 to :1.3, Error: org.freedesktop.DBus.Error.Failed : Can not get value [engine/anthy/shortcut/wnn->add_word] (ibus-daemon:21356): IBUS-DEBUG: From ::1.1 to :1.3, Error: org.freedesktop.DBus.Error.Failed : Can not get value [engine/anthy/shortcut/wnn->start_setup]
They all have in common a message about not getting a value from engine/anthy/shortcut/<something>. Perhaps these are normal? If not, do they ring a bell with anyone? I don't see any messages when I type the activate sequence (alt-grave) in some window.
As a quick check....what I would do is to create a new user account and see if things work for that new user. This will then tell you if it is simply something that is related to your settings....
Hadn't thought of that, good idea. Did so, enabled the IME and selected Anthy, but same problem exists in the new account.
The error messages I've not seen before....nor heard of. Almost sounds as if some other process has reserved the start/stop method. Since a new account would/should start out with a "blank" home directory without any .ibus or .dbus directories it would suggest that the problem is actually external to ibus. I'm going to presume that the .imsettings.log did not reveal anything either.....
Would that survive a reboot under some conditions? I know some locks can get orphaned when problems occur. Is this something that could/should be cleared at boot?
You said you were running Gnome. Does the same thing happen under KDE?
Like you said....since it works for others then the problem is unique to your system. Even so, it would be a good idea to file a bugzilla. The developers may not read or pay much attention to this list and with a bugzilla may actually have the answer to your problem.
-
Bill Davidsen -
Craig White -
Ed Greshko -
Stuart McGraw