https://bugzilla.redhat.com/show_bug.cgi?id=1142458
--- Comment #6 from Mike FABIAN <mfabian(a)redhat.com> ---
ibus-anthy uses this:
ibus_config = bus.get_config()
if ibus_config != None:
ibus_config.connect('value-changed',
self.__config_value_changed_cb)
i.e. it checks whether bus.get_config() returns “None”.
I could do that as well in ibus-table to prevent the traceback
and keep the program running.
But then of course the callback self.__config_value_changed_cb() is
not called when a dconf variable changes. I.e. ibus-table does not get
notified when one of its dconf variables gets changed. That means,
changing some setting with the setup tool of ibus-table “rusle”
would write to dconf but this would have no immediate effect on
ibus-table “rusle”, the setting would be used only after ibus restart.
That is not so nice, so I wonder why this can happen.
Apparently it is a timing issue.
Should I maybe retry bus.get_config() a few times?
I.e. if bus.get_config() returns None, then wait a few milliseconds
and try again, continue without connecting the callback only
if bus.get_config() still doesn’t work after some timeout.
Does this make sense? Or will bus.get_config() keep failing
when it failed once?
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=hGcHv89gkR&a=cc_unsubscribe