Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=878352
--- Comment #15 from Akira TAGOH tagoh@redhat.com --- (In reply to comment #14)
I have looked at the issue more, indeed it doesn't autostart. I then tried starting it from a terminal and it still doesn't start ibus
It depends on your locale. we are running ibus by default for certain languages only so far. see /etc/X11/xinit/xinitrc.d/50-xinput.sh
I launch im-chooser and it offers to start ibus, these are the warnings in ~/.xsession-errors
** (im-chooser:1468): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
** (main.py:1909): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Well, this is because no at-spi2-registryd is running. and this is similar reason that MATE incompletely support AutostartCondition. see /etc/xdg/autostart/at-spi-dbus-bus.desktop how it's brought up.
i18n-bugs@lists.fedoraproject.org