[Fedora-i18n-bugs] [Bug 709836] [abrt] ibus-1.3.99.20110408-5.fc15: connection.py:630:call_blocking:DBusException: org.freedesktop.DBus.Error.Failed: Can not find engine xkb:layout:in:tel.

bugzilla at redhat.com bugzilla at redhat.com
Wed Jun 15 08:25:48 UTC 2011


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=709836

fujiwara <tfujiwar at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|                            |needinfo?(pahninsd at gmail.co
                   |                            |m)

--- Comment #14 from fujiwara <tfujiwar at redhat.com> 2011-06-15 04:25:47 EDT ---
(In reply to comment #11)
> " ps -ef | grep ibus-engine" this command
> and I got
> 500       4024  4015  0 13:04 pts/0    00:00:00 /usr/libexec/ibus-engine-m17n
> --ibus

It means your primary engine is m17n.
So I expect your reproducing steps are not accurate.
If you just type Control+Space, I think m17n is enabled.
I guess you choose Telugu xkb engine with mouse on ibus panel icon at first.

You could change the primary engine with 'ibus-setup' command.
If you select [Input Method] tab in ibus-setup, the engine lists are shown and
you could set 'Telugu' as primary if you move 'Telugu' engine with 'Up' button.

Then if you run ibus-daemon, ibus-engine-xkb will be executed at first.

> "./usr/libexec/ibus-engine-xkb"

OK but please run ibus-engine-xkb with '--ibus' argument at the moment in order
to get your problem exactly.

> Now everything is working and the ibus is runnig as demon but when I restarts
> it is executing /usr/libexec/ibus-engine-m17n again which I dont want
> so tell me how to change this or is it a bug?

I explained this above. I think it's your setting with ibus-setup.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the i18n-bugs mailing list