http://bugzilla.opensuse.org/show_bug.cgi?id=941052 http://bugzilla.opensuse.org/show_bug.cgi?id=941052#c1 Fuminobu Takeyama changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |i@marguerite.su, | |ledest@gmail.com Assignee|bnc-team-screening@forge.pr |ftake@geeko.jp |ovo.novell.com | --- Comment #1 from Fuminobu Takeyama --- CC related maintainers -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=941052 http://bugzilla.opensuse.org/show_bug.cgi?id=941052#c3 --- Comment #3 from Marguerite Su --- Hi, ftake, I am not familiar with differences between sh and bash, can you please help fix for fcitx? Marguerite -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=941052 http://bugzilla.opensuse.org/show_bug.cgi?id=941052#c5 --- Comment #5 from John Jiang --- (In reply to Takashi Iwai from comment #4)

Doesn't it really start at all, or "may not" start? I thought we've always used bash as the primary shell unlike Debian.

It doesn't start automatically with the system. I could open it manually, while it shows "no input window". I am new of linux, unfamiliar with the kernel and only have to wait for help. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=941052 http://bugzilla.opensuse.org/show_bug.cgi?id=941052#c7 --- Comment #7 from Fuminobu Takeyama --- Please remind that if "#!/bin/sh" is specified, bash works in POSIX mode. Under the POSIX mode, /etc/X11/xim causes syntax error at line 173. I could find the following error in ~/.xsession-errors* /etc/X11/xim: 173 行: [: : 単項演算子が予期されます I've fixed /etc/X11/xim. https://build.opensuse.org/request/show/321468 This problem will be resolved soon in Tumbleweed at least for IBus or Fcitx. As far as I checked, IBus and Fcitx have bashisms, which are the "-p" option of "type" command. Fortunately, it works for bash's POSIX mode. I have not checked other input methods yet. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=941052 http://bugzilla.opensuse.org/show_bug.cgi?id=941052#c9 --- Comment #9 from Marguerite Su --- "#!/bin/sh" == "#!/usr/bin/bash --posix" :-( so we have to make our scripts with pure sh (not only for bash in posix mode, but also for other possibilities, just in case), so I think the if type -p fcitx >/dev/null 2&>1 ; then stuff should be changed to if [ -x /usr/bin/fcitx ] ; then and "return 0" should be changed to "exit 0" :-( You can use "bash --posix -x /etc/X11/xim.d/fcitx" to test if that script is compatible with sh. Marguerite -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=941052 http://bugzilla.opensuse.org/show_bug.cgi?id=941052#c11 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@suse.com --- Comment #11 from Takashi Iwai --- I submitted the revert the shebang of xim to /bin/bash via SRID 321639. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=941052 http://bugzilla.opensuse.org/show_bug.cgi?id=941052#c13 --- Comment #13 from Fuminobu Takeyama --- Marguerite, I am not sure but this new script works as expected? It seems that the script does not exit when fcitx is not found (it just refers to a undefined variable). "/etc/X11/xim.d/fcitx" is sourced (i.e. ". /etc/X11/xim.d/fcitx") form the xim script. My understanding is that we can use "return" statement in such script to go back from a sourced script to sourcing script with a return value. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=941052 http://bugzilla.opensuse.org/show_bug.cgi?id=941052#c15 --- Comment #15 from Fuminobu Takeyama --- I updated to the latest Tumbleweed. /etc/X11/xim is still broken. Maybe it fails to find an appropriate IMF. Marguerite,

1. These kind of scripts come and go with IMF packages...I can't get the reason to still check the availibility of the IMFs...

I also think so.

2. I wrote a warning in the check sentence, if fcitx is not found, there should be something being logged. But I couldn't find such messages anywhere...

At least, for kdm, the script now need to print messages into stderr to keep the messages in ~/.xsession-errors*. The behavior of kdm was changed recently. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=941052 http://bugzilla.opensuse.org/show_bug.cgi?id=941052#c17 --- Comment #17 from Fuminobu Takeyama --- No error message (stdout is filtered out by kdm) If INPUT_METHOD=ibus is specified in ~/.i18n then IBus starts as expected. There seems to be some problems with auto selecting depending on the locale. INPUT_METHOD= LANG=ja_JP.UTF-8 QT_IM_MODULE=xim XMODIFIERS=@im=local GTK_IM_MODULE=cedilla QT_IM_SWITCHER=imsw-multi Clearly, /etc/X11/xim.d/none is selected for my environment. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=941052 http://bugzilla.opensuse.org/show_bug.cgi?id=941052#c19 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ftake@geeko.jp Flags| |needinfo?(ftake@geeko.jp) --- Comment #19 from Takashi Iwai --- Do you have ~/.i18n with empty $INPUT_METHOD? If so, do you see whether the problem remains after removing ~/.i18n? It seems that the code evaluating ~/.i18n that was recently added breaks the later evaluation of $tmplang. -- You are receiving this mail because: You are on the CC list for the bug.