Bug#709921: im-config: cannot detect IM module files correctly
reopen 709921 severity 709921 normal notfound 709921 0.21 notfound 709921 0.22-1 notfound 709921 0.22-2 notfound 709921 0.22-3 thanks (I think this was not bug of im-config after all) On Tue, Jun 04, 2013 at 12:51:53AM +0800, Aron Xu wrote: ... Did you restarted X session before testing? I am a bit lost ... Got it working after rebooting the machine, restart X seems does not work. I'm using systemd as init, but not sure whether this can be related. This made me think again. I initially thought Aron's analysis is 100% right. | 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 I agree this may make some people worry. When I implemented, I knew what I was doing. But after a while, I forgot that kind of details. So when Aron said, I even got tricked myself. These *s, if they do not much produce /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so as is. But the following lines check if they really exist. So bogus name with * means file does not exist and keep on checking.i So the code in stable 0.21 is OK. Of course, starting subshell with $(...) makes program slower. I think that was why I chose this style of coding. But now that I think of this, speed is non-critical and easy to understand code is good for maintenance. Here is my check for 0.21 it works to set up fcitx :-) $ dpkg -l im-config Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii im-config 0.21 all Input method configuration framew $ env|grep fcitx XMODIFIERS=@im=fcitx QT4_IM_MODULE=fcitx GTK_IM_MODULE=fcitx Regards, Osamu PS: Once I see this updates BTS, I will close this bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
Hi, On Tue, Jun 04, 2013 at 12:51:53AM +0800, Aron Xu wrote: On Sun, Jun 2, 2013 at 11:15 PM, Osamu Aoki os...@debian.org wrote: Hi, Here, I installed fcitx to wheezy while installing 0.22-2 of im-config. I do not see the problem. $ set|grep GTK GTK_IM_MODULE=fcitx $ set|grep fcitx GTK_IM_MODULE=fcitx QT4_IM_MODULE=fcitx XMODIFIERS=@im=fcitx $ dpkg -l im-config Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii im-config 0.22-2 all Input method configuration framew Did you restarted X session before testing? I am a bit lost Osamu Got it working after rebooting the machine, restart X seems does not work. I'm using systemd as init, but not sure whether this can be related. Well, this may be. We need to restart X start-up code. Systemd may require more than re-login to get X restarted. Anyway, this confirms im-config 0.22-2 fix issues. Question is what patch to push to stable. Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
Hi, Can you post few things: - $ dpkg -S im-fcitx.so fcitx-frontend-gtk3:amd64: /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-fcitx.so fcitx-frontend-gtk2:amd64: /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-fcitx.so fcitx-frontend-qt4:amd64: /usr/lib/x86_64-linux-gnu/qt4/plugins/inputmethods/qtim-fcitx.so $ env |grep '\(IM_MODULE\|XMODIFIERS\)' CLUTTER_IM_MODULE=xim XMODIFIERS=@im=fcitx QT4_IM_MODULE=fcitx GTK_IM_MODULE=fcitx $ cat ~/.xinputrc # im-config(8) generated on Mon, 03 Jun 2013 00:08:38 +0900 run_im fcitx # im-config signiture: 8d9d23893836bdcfc8766d8d55e1033d - $ - Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
On Sun, Jun 2, 2013 at 11:15 PM, Osamu Aoki os...@debian.org wrote: Hi, Here, I installed fcitx to wheezy while installing 0.22-2 of im-config. I do not see the problem. $ set|grep GTK GTK_IM_MODULE=fcitx $ set|grep fcitx GTK_IM_MODULE=fcitx QT4_IM_MODULE=fcitx XMODIFIERS=@im=fcitx $ dpkg -l im-config Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii im-config 0.22-2 all Input method configuration framew Did you restarted X session before testing? I am a bit lost Osamu Got it working after rebooting the machine, restart X seems does not work. I'm using systemd as init, but not sure whether this can be related. Regards, Aron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
Am I correct? $ im-config -d + shift + '[' -n '' ']' + '[' X = X ']' + '[' '!' -x /usr/bin/zenity ']' + '[' x:0 = x ']' ++ active_im ++ '[' '!' -r /home/aron/.xinputrc ']' ++ check_md5sum /home/aron/.xinputrc ++ '[' -r /home/aron/.xinputrc ']' +++ head -n -1 /home/aron/.xinputrc +++ md5sum +++ tail -n 1 /home/aron/.xinputrc ++ '[' '# im-config signiture: 714704ce7c216b2637069531e1e21e72 -' = '# im-config signiture: 714704ce7c216b2637069531e1e21e72 -' ']' ++ true +++ sed -n -e 's/^run_im \([^ ]*\) *$/\1/p' ++ IM_CONFIG_ACTIVE_IM=fcitx ++ '[' -z fcitx ']' ++ '[' -r /usr/share/im-config/data/22_fcitx.conf ']' ++ echo fcitx + IM_CONFIG_ACTIVE=fcitx + '[' fcitx = custom ']' + IM_CONFIG_NUMBER=0 + IM_CONFIG_AVAIL= + for IM_CONFIG_PATH in '$IM_CONFIG_DATA/[12345678][0123456789]_*.rc' ++ name_im /usr/share/im-config/data/20_ibus.rc ++ local x ++ x=ibus.rc ++ x=ibus ++ x=ibus ++ echo -n ibus + IM_CONFIG_NAME=ibus + avail_menu ibus + '[' -r /usr/share/im-config/data/20_ibus.conf ']' + . /usr/share/im-config/data/20_ibus.conf +++ gettext 'activate Intelligent Input Bus (IBus)' ++ IM_CONFIG_SHORT='activate Intelligent Input Bus (IBus)' +++ gettext 'Intelligent Input Bus (IBus) * Required for all: ibus * Language specific input conversion support: * Japanese: ibus-mozc (best) or ibus-anthy or ibus-skk * Korean: ibus-hangul * Simplified Chinese: ibus-pinyin or ibus-sunpinyin or ibus-googlepinyin * Traditional Chinese: ibus-chewing * Thai: ibus-table-thai * Vietnamese: ibus-unikey or ibus-table-viqr * X Keyboard emulation: ibus-xkbc * Generic keyboard translation table: ibus-m17n or ibus-table* packages * Application platform support: * GNOME/GTK+: ibus-gtk and ibus-gtk3 (both) * KDE/Qt: ibus-qt4 * Clutter: ibus-clutter * EMACS: ibus-el' ++ IM_CONFIG_LONG='Intelligent Input Bus (IBus) * Required for all: ibus * Language specific input conversion support: * Japanese: ibus-mozc (best) or ibus-anthy or ibus-skk * Korean: ibus-hangul * Simplified Chinese: ibus-pinyin or ibus-sunpinyin or ibus-googlepinyin * Traditional Chinese: ibus-chewing * Thai: ibus-table-thai * Vietnamese: ibus-unikey or ibus-table-viqr * X Keyboard emulation: ibus-xkbc * Generic keyboard translation table: ibus-m17n or ibus-table* packages * Application platform support: * GNOME/GTK+: ibus-gtk and ibus-gtk3 (both) * KDE/Qt: ibus-qt4 * Clutter: ibus-clutter * EMACS: ibus-el' + package_menu + package_status ibus + PACKAGE_NAME=ibus ++ LANG=C ++ dpkg-query -l ibus ++ sed -n '6s/\([^ ]*\) .*$/\1/p' + '[' '' = ii ']' + return 1 + for IM_CONFIG_PATH in '$IM_CONFIG_DATA/[12345678][0123456789]_*.rc' ++ name_im /usr/share/im-config/data/22_fcitx.rc ++ local x ++ x=fcitx.rc ++ x=fcitx ++ x=fcitx ++ echo -n fcitx + IM_CONFIG_NAME=fcitx + avail_menu fcitx + '[' -r /usr/share/im-config/data/22_fcitx.conf ']' + . /usr/share/im-config/data/22_fcitx.conf +++ gettext 'activate Flexible Input Method Framework (fcitx)' ++ IM_CONFIG_SHORT='activate Flexible Input Method Framework (fcitx)' +++ gettext 'Flexible Input Method Framework (fcitx) * Required for all: fcitx * Language specific input conversion support: * Simplified Chinese: fcitx-pinyin or fcitx-sunpinyin or fcitx-googlepinyin * Generic keyboard translation table: fcitx-table* packages * Application platform support: * GNOME/GTK+: fcitx-frontend-gtk2 and fcitx-frontend-gtk3 (both) * KDE/Qt4: fcitx-frontend-qt4' ++ IM_CONFIG_LONG='Flexible Input Method Framework (fcitx) * Required for all: fcitx * Language specific input conversion support: * Simplified Chinese: fcitx-pinyin or fcitx-sunpinyin or fcitx-googlepinyin * Generic keyboard translation table: fcitx-table* packages * Application platform support: * GNOME/GTK+: fcitx-frontend-gtk2 and fcitx-frontend-gtk3 (both) * KDE/Qt4: fcitx-frontend-qt4' + package_menu + package_status fcitx-bin + PACKAGE_NAME=fcitx-bin ++ LANG=C ++ sed -n '6s/\([^ ]*\) .*$/\1/p' ++ dpkg-query -l fcitx-bin + '[' ii = ii ']' + return 0 + '[' fcitx '!=' none ']' + IM_CONFIG_NUMBER=1 + IM_CONFIG_AVAIL=' fcitx' + for IM_CONFIG_PATH in '$IM_CONFIG_DATA/[12345678][0123456789]_*.rc' ++ name_im /usr/share/im-config/data/24_uim.rc ++ local x ++ x=uim.rc ++ x=uim ++ x=uim ++ echo -n uim + IM_CONFIG_NAME=uim + avail_menu uim + '[' -r /usr/share/im-config/data/24_uim.conf ']' + . /usr/share/im-config/data/24_uim.conf +++ gettext 'activate universal input method (uim)' ++ IM_CONFIG_SHORT='activate universal input method (uim)' +++ gettext 'universal input method (uim) * Required for all: uim * Language specific input conversion support: * Japanese: uim-mozc (best) or uim-anthy or uim-skk * Korean: uim-byeoru * Simplified Chinese: uim-pinyin * Traditional Chinese: uim-chewing * Vietnamese: uim-viqr * General-purpose M17n: uim-m17nlib * Application platform support: * XIM: uim-xim * GNOME/GTK+: uim-gtk2.0 and uim-gtk3 (both) * KDE/Qt4: uim-qt * EMACS:
Bug#709921: im-config: cannot detect IM module files correctly
HI, II think I figured out. On Sat, Jun 01, 2013 at 01:21:57AM +0800, Aron Xu wrote: On Wed, May 29, 2013 at 8:47 PM, Osamu Aoki os...@debian.org wrote: I uploaded one for unstable. Please check what I am doing is right. If it is good, I will backport this. Osamu Seems GTK_IM_MODULE still show up as xim, and QT4_IM_MODULE is correct. But I don't know what's wrong with GTK. I tried to add some echo to 22_fcitx.rc and it shows that the two `ls` command returns nothing to the variable, while it works for Qt... Sorry, I overlooked important message here. What im-config does. $ ls /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.sols /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.so ls: cannot access /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.sols: No such file or directory /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-fcitx.so $ ls /usr/lib/gtk-3.0/*/immodules/im-fcitx.so ls: cannot access /usr/lib/gtk-3.0/*/immodules/im-fcitx.so: No such file or directory But where are they really $ dpkg -L fcitx-frontend-gtk2 /. /usr /usr/share /usr/share/doc /usr/share/doc/fcitx-frontend-gtk2 /usr/share/doc/fcitx-frontend-gtk2/changelog.Debian.gz /usr/share/doc/fcitx-frontend-gtk2/changelog.gz /usr/share/doc/fcitx-frontend-gtk2/copyright /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/gtk-2.0 /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0 /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-fcitx.so $ dpkg -L fcitx-frontend-gtk3 /. /usr /usr/share /usr/share/doc /usr/share/doc/fcitx-frontend-gtk3 /usr/share/doc/fcitx-frontend-gtk3/changelog.Debian.gz /usr/share/doc/fcitx-frontend-gtk3/changelog.gz /usr/share/doc/fcitx-frontend-gtk3/copyright /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/gtk-3.0 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-fcitx.so So I should change these new dorectories for new multiarch packages to: /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.so Was this directory change new thing? Then I will just add new ones to support bacck port. If this has been always so, I will change path. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
On Sun, Jun 2, 2013 at 9:02 PM, Osamu Aoki os...@debian.org wrote: HI, II think I figured out. [...] So I should change these new dorectories for new multiarch packages to: /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.so Was this directory change new thing? Then I will just add new ones to support bacck port. If this has been always so, I will change path. I don't think we've ever changed the directory except for Multi-Arch. Regards, Aron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
Hi, On Sun, Jun 02, 2013 at 09:57:46PM +0800, Aron Xu wrote: On Sun, Jun 2, 2013 at 9:02 PM, Osamu Aoki os...@debian.org wrote: HI, II think I figured out. [...] So I should change these new dorectories for new multiarch packages to: /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.so Was this directory change new thing? Then I will just add new ones to support bacck port. If this has been always so, I will change path. I don't think we've ever changed the directory except for Multi-Arch. I see but as I look again carefully, I may have jumped on conclusion too early. Do you have both fcitx-frontend-gtk2 and fcitx-frontend-gtk3 installed? Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
On Sun, Jun 2, 2013 at 10:31 PM, Osamu Aoki os...@debian.org wrote: Hi, On Sun, Jun 02, 2013 at 09:57:46PM +0800, Aron Xu wrote: On Sun, Jun 2, 2013 at 9:02 PM, Osamu Aoki os...@debian.org wrote: HI, II think I figured out. [...] So I should change these new dorectories for new multiarch packages to: /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.so Was this directory change new thing? Then I will just add new ones to support bacck port. If this has been always so, I will change path. I don't think we've ever changed the directory except for Multi-Arch. I see but as I look again carefully, I may have jumped on conclusion too early. Do you have both fcitx-frontend-gtk2 and fcitx-frontend-gtk3 installed? Of course: $ ls /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.so /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-fcitx.so $ ls /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-fcitx.so $ ls /usr/lib/*/qt4/plugins/inputmethods/qtim-fcitx.so /usr/lib/x86_64-linux-gnu/qt4/plugins/inputmethods/qtim-fcitx.so $ dpkg -l | grep fcitx-frontend ii fcitx-frontend-all 1:4.2.4.1-7 all Flexible Input Method Framework - frontends metapackage ii fcitx-frontend-gtk2:amd64 1:4.2.4.1-7 amd64Flexible Input Method Framework - GTK+ 2 IM Module frontend ii fcitx-frontend-gtk3:amd64 1:4.2.4.1-7 amd64Flexible Input Method Framework - GTK+ 3 IM Module frontend ii fcitx-frontend-qt4:amd64 1:4.2.4.1-7 amd64Flexible Input Method Framework - QT 4 IM Module frontend Thanks, Aron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
Hi, On Sun, Jun 02, 2013 at 10:36:25PM +0800, Aron Xu wrote: On Sun, Jun 2, 2013 at 10:31 PM, Osamu Aoki os...@debian.org wrote: Hi, On Sun, Jun 02, 2013 at 09:57:46PM +0800, Aron Xu wrote: On Sun, Jun 2, 2013 at 9:02 PM, Osamu Aoki os...@debian.org wrote: HI, II think I figured out. [...] So I should change these new dorectories for new multiarch packages to: /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.so Was this directory change new thing? Then I will just add new ones to support bacck port. If this has been always so, I will change path. I don't think we've ever changed the directory except for Multi-Arch. I see but as I look again carefully, I may have jumped on conclusion too early. Do you have both fcitx-frontend-gtk2 and fcitx-frontend-gtk3 installed? Of course: $ ls /usr/lib/*/gtk-3.0/*/immodules/im-fcitx.so /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-fcitx.so $ ls /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-fcitx.so $ ls /usr/lib/*/qt4/plugins/inputmethods/qtim-fcitx.so /usr/lib/x86_64-linux-gnu/qt4/plugins/inputmethods/qtim-fcitx.so $ dpkg -l | grep fcitx-frontend ii fcitx-frontend-all 1:4.2.4.1-7 all Flexible Input Method Framework - frontends metapackage ii fcitx-frontend-gtk2:amd64 1:4.2.4.1-7 amd64Flexible Input Method Framework - GTK+ 2 IM Module frontend ii fcitx-frontend-gtk3:amd64 1:4.2.4.1-7 amd64Flexible Input Method Framework - GTK+ 3 IM Module frontend ii fcitx-frontend-qt4:amd64 1:4.2.4.1-7 amd64Flexible Input Method Framework - QT 4 IM Module frontend Here, I installed fcitx to wheezy while installing 0.22-2 of im-config. I do not see the problem. $ set|grep GTK GTK_IM_MODULE=fcitx $ set|grep fcitx GTK_IM_MODULE=fcitx QT4_IM_MODULE=fcitx XMODIFIERS=@im=fcitx $ dpkg -l im-config Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii im-config 0.22-2 all Input method configuration framew Did you restarted X session before testing? I am a bit lost Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
On Wed, May 29, 2013 at 8:47 PM, Osamu Aoki os...@debian.org wrote: I uploaded one for unstable. Please check what I am doing is right. If it is good, I will backport this. Osamu Seems GTK_IM_MODULE still show up as xim, and QT4_IM_MODULE is correct. But I don't know what's wrong with GTK. I tried to add some echo to 22_fcitx.rc and it shows that the two `ls` command returns nothing to the variable, while it works for Qt... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
Hi, On Sat, Jun 01, 2013 at 01:21:57AM +0800, Aron Xu wrote: On Wed, May 29, 2013 at 8:47 PM, Osamu Aoki os...@debian.org wrote: I uploaded one for unstable. Please check what I am doing is right. If it is good, I will backport this. Osamu Seems GTK_IM_MODULE still show up as xim, and QT4_IM_MODULE is correct. But I don't know what's wrong with GTK. I tried to add some echo to 22_fcitx.rc and it shows that the two `ls` command returns nothing to the variable, while it works for Qt... Please run im-config with -d) # debug trace mode :-) undocumented. IM_CONFIG_SETMODE=-x set $IM_CONFIG_SETMODE and send us the log. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
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
Bug#709921: im-config: cannot detect IM module files correctly
I just checked subshell error does not cause script to stall. But to be safe, I am thinking to use || true $ cat xxx;xxx #!/bin/sh # vim:se tw=0 sts=4 ts=4 et si: set -e echo START with -e echo /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so; echo FOO echo #1: $? for x in /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so; do echo $x; done; echo FOO echo #2: $? for x in `ls /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so`; do echo $x; done; echo FOO echo #3: $? ls /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so || true; echo FOO echo #4: $? ls /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so; echo FOO echo #5: $? START with -e /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so FOO #1: 0 /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so FOO #2: 0 ls: cannot access /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so: No such file or directory FOO #3: 0 ls: cannot access /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so: No such file or directory FOO #4: 0 ls: cannot access /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so: No such file or directory $ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
I uploaded one for unstable. Please check what I am doing is right. If it is good, I will backport this. Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709921: im-config: cannot detect IM module files correctly
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 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 also recommend to push a stable release update for this bug. Thanks, Aron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
