[Fedora-i18n-bugs] [Bug 796070] run ibus-setup produces IBUS-CRITICAL ** Traceback.

[bugzilla at redhat.com]

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=796070

--- Comment #14 from Daiki Ueno <dueno at redhat.com> 2012-02-23 20:36:05 EST ---
(In reply to comment #13)

> Yes, I noticed Gtk.MESSAGE_INFO after I updated this yesterday. But no
> self.__bus.destroy() is ok in my test. 

IBusBus is actually a singleton (see "_bus" variable in ibusbus.c) and need to
be destroyed to trigger reconnect.

>                  try:
> +                    if self.__bus != None:
> +                        self.__bus.destroy()
>                      self.__bus = IBus.Bus()
>                  except:
>                      continue

Hmm, this part still looks wrong.  Since IBus.Bus() does not raise any
exception when bus is not connected, you need to check
self.__bus.is_connected() and continue if it returns False.  Otherwise you will
see a successful message dialog even if ibus-daemon fails to start.

try:
    if self.__bus != None:
        self.__bus.destroy()
    self.__bus = IBus.Bus()
    if not self.__bus.is_connected():
        continue
except:
    continue

-- 
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.