Bug 522048

Created attachment 360183 [details]
File: backtrace

I think it is in ibus-anthy.

Please get the latest RPM.

*** This bug has been marked as a duplicate of bug 522047 ***

$ rpm -qa | grep ibus
libuser-0.56.12-1.fc12.i686
ibus-1.2.0.20091024-1.fc12.i686
ibus-libs-1.2.0.20091024-1.fc12.i686
libuser-python-0.56.12-1.fc12.i686
libusb-0.1.12-22.fc12.i686
ibus-pinyin-1.2.0.20090915-1.fc12.noarch
libusb1-1.0.3-1.fc12.i686
ibus-gtk-1.2.0.20091024-1.fc12.i686
libusb-devel-0.1.12-22.fc12.i686


Are these the lastest ones?  Crash still happen.

(In reply to comment #4)
> Are these the lastest ones?  Crash still happen.  

Did you check your backtrace?
This bug explains 'thumb' module is not found in the backtrace. I've fixed to install /usr/share/ibus-anthy/engine/thumb.py in f12.

(In reply to comment #5)
> (In reply to comment #4)
> > Are these the lastest ones?  Crash still happen.  
> 
> Did you check your backtrace?
> This bug explains 'thumb' module is not found in the backtrace. I've fixed to
> install /usr/share/ibus-anthy/engine/thumb.py in f12.  

I will try to yum install ibus-anthy. And thanks a lot.

No, It crashed again after I install ibus-anthy.

and backtrack as follows:

backtrace
-----
Summary: TB08997608 connection.py:630:call_blocking:DBusException: org.freedesktop.IBus.NoEngine: can not find engine with name pinyin

Traceback (most recent call last):
  File "/usr/share/ibus/ui/gtk/panel.py", line 425, in __im_menu_item_activate_cb
    self.__focus_ic.set_engine(engine)
  File "/usr/lib/python2.6/site-packages/ibus/inputcontext.py", line 238, in set_engine
    return self.__context.SetEngine(engine.name)
  File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking
    message, timeout)
DBusException: org.freedesktop.IBus.NoEngine: can not find engine with name pinyin

Local variables in innermost frame:
byte_arrays: False
self: <dbus.connection.Connection object at 0x84b656c>
args: (dbus.String(u'pinyin'),)
utf8_strings: False
bus_name: org.freedesktop.IBus
get_args_opts: {'byte_arrays': False, 'utf8_strings': False}
object_path: /org/freedesktop/IBus/InputContext_205
timeout: -1.0
signature: None
dbus_interface: None
message: <dbus.lowlevel.MethodCallMessage object at 0x83fbf60>
method: SetEngine

(In reply to comment #7)
> No, It crashed again after I install ibus-anthy.

>   File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in
> call_blocking
>     message, timeout)
> DBusException: org.freedesktop.IBus.NoEngine: can not find engine with name
> pinyin
> 

Your backtrace is different from this bug. I.e. Your issue is not this bug.
It seems pinyin is not found from your backtrace.
Did you install the latest ibus-pinyin ?
Please file a new bug for ibus-pinyin with your backtrace as I don't reproduce
your issue.

(In reply to comment #8)
> (In reply to comment #7)
> > No, It crashed again after I install ibus-anthy.
> 
> >   File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in
> > call_blocking
> >     message, timeout)
> > DBusException: org.freedesktop.IBus.NoEngine: can not find engine with name
> > pinyin
> > 
> 
> Your backtrace is different from this bug. I.e. Your issue is not this bug.
> It seems pinyin is not found from your backtrace.
> Did you install the latest ibus-pinyin ?
> Please file a new bug for ibus-pinyin with your backtrace as I don't reproduce
> your issue.  

I myself think it in same way. But the abrt tool think it's just the same.  And, yes, I have ibus-pinyin installed and this happend when I chat with friend using pidgin.

What should I do next?

(In reply to comment #9)
> I myself think it in same way. But the abrt tool think it's just the same. 

I mean I manage ibus-anthy and don't touch pinyin so it would be good to file a bug in ibus-pinyin if you want the proper helps.
I renamed the bug synopsis to clarify this bug.

Now I noticed there are "PinYin" and "pinyin" modules in ibus.
I guess your "pinyin" is ibus-m17n instead of ibus-pinyin.

1. Did you install m17n-db-chinese ?
2. Did you see the process of ibus-engine-m17n after you type "Ctrl + Space" ?
3. Did you see any warning messages after you kill the process of ibus-engine-m17n and run '/usr/libexec/ibus-engine-m17n --ibus' by manual ?

When first time I got this error, I even not installed ibus-anthy. I just use the abrt tool to report this bug. And I have no idea why it was emerged to this bug report.

1. No, my "pinyin" is ibus-pinyin and I have not installed m17n-db-chinese.
2. No , there is no such proces.
3. No, there is no file named "ibus-engine-m17n" in my system.

maybe it's another bug of abrt tool?

(In reply to comment #11)
> And I have no idea why it was emerged to this bug report.

Hmm.., I don't understand the meaning that your abrt report was merged to this report as I don't see any duplicated bug reports of yours.

> maybe it's another bug of abrt tool?  

Maybe. It would be good to file a bug by manual if your abrt has any troubles.
Also you could check any warning messages with the following command line after you kill ibus-pinyin.

% env IBUS_PINYIN_LOCATION=/usr/share/ibus-pinyin python /usr/share/ibus-pinyin/engine/main.py

(In reply to comment #11)
> I just use the abrt tool to report this bug. 

This bug was reported by Jens Petersen originally, wasn't it?

Yes, but one of my report was marked as duplicated with this one... .

(In reply to comment #14)
> Yes, but one of my report was marked as duplicated with this one... .  

Did you remember your bugid? If not, I think your issue might be new.
I cannot find the duplicated bug ids on this bug report.

Not really.  And I have delete all the response of bugzilla in my Gmail account....= =;

I will report the bug separately.. Thanks a lot dude..