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.