[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 #16 from Daiki Ueno <dueno at redhat.com> 2012-02-24 18:33:32 EST ---
(In reply to comment #15)
> > 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.

> OK, revised.
> 

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

It has not changed from the previous version?  Anyway, I would suggest that you
should test it at least.  That shouldn't be hard I guess.  Though this bug
sounds not that important for you, I wonder if it isn't the case of the final
release criteria:

https://fedoraproject.org/wiki/Fedora_17_Final_Release_Criteria

* All applications listed under the Applications menu or category must start
successfully

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