Created attachment 362977 [details]
example for xinput file
Description of problem:
bringing up XIM with the different locale to the system locale ends up to raise an error like, "No such input method on your system: blahblahblah". but it appears in the list.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.put attached into /etc/X11/xinit/xinput.d/
2.ln -s xcompose /etc/X11/xinit/xinput.d/pt_BR
3.LANG=pt_BR.UTF-8 imsettings-start "X locale compose"
it raises an error.
IM should start.
LANG=pt_BR.UTF-8 imsettings-list shows that as available.
Dunno if we still need this with the support for XIM @im=none
added to none.conf?
you mean GTK_IM_MODULE=xim.
Well, I don't still think it's the right solution widely, without XIM support in imsettings at least, because it effects all of the users and switching from/to something to/from it requires restarting the desktop. plus, the worst thing may be for CIJK users who tentatively wants to disable IM say. in this case, it works on GTK+ applications but the native X applications and Qt applications etc still connects to IM through XIM, because XMODIFIERS still points to IM's.
Since we missed the way of fixing that issue in the gtk immodule, we should try to find out the better way for everyone.
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.
More information and reason for this action is here:
This should be fixed in imsettings-1.0.0-1.fc15.