Hi, On Mon, May 27, 2013 at 02:23:20AM +0800, Aron Xu wrote: > Package: im-config > Version: 0.21 > Severity: serious > > The problem is that im-config quits when trying to detect IM module > files that is written in data/??_*.rc, so no IM module is set > correctly and all are falling back to XIM. > > For example in data/22_fcitx.rc at line 16 and 17, there are two lines > to cover files in both MultiArch and non-MultiArch paths, and one of > them will match nothing. The line that matches nothing will lead the > script to quit because the script itself is set -e, causing the > trouble described before. The problem is valid for the detection code > of GTK2, GTK3, Qt4, and Clutter IM modules. > > 16 for IM_CONFIG_MARKER in /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so \ > 17 /usr/lib/gtk-2.0/*/immodules/im-fcitx.so ; do
Hmmm... this is design error .. since I did not install fcitx: $ echo /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so $ for x in /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so; do echo "$x"; done /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so $ for x in `ls /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so`; do echo "$x"; done ls: cannot access /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so: No such file or directory $ for x in `ls /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so 2>/dev/null`; do echo "$x"; done I see. > A working solution is to use ls command and ignore its output to > stderr, which means something looks like: > 16 for IM_CONFIG_MARKER in `ls > /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so 2>/dev/null` \ > 17 `ls > /usr/lib/gtk-2.0/*/immodules/im-fcitx.so 2>/dev/null` ; do >i > I also recommend to push a stable release update for this bug. It's been this way for good long time. Oh, well.. Let's fix this. Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
