Your message dated Wed, 29 May 2013 12:48:44 +0000
with message-id <e1uhfo4-0004yv...@franck.debian.org>
and subject line Bug#709921: fixed in im-config 0.22-2
has caused the Debian Bug report #709921,
regarding im-config: cannot detect IM module files correctly
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
709921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: im-config
Source-Version: 0.22-2
We believe that the bug you reported is fixed in the latest version of
im-config, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 709...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Osamu Aoki <os...@debian.org> (supplier of updated im-config package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Wed, 29 May 2013 21:39:44 +0900
Source: im-config
Binary: im-config
Architecture: source all
Version: 0.22-2
Distribution: unstable
Urgency: low
Maintainer: Osamu Aoki <os...@debian.org>
Changed-By: Osamu Aoki <os...@debian.org>
Description:
im-config - Input method configuration framework
Closes: 709921
Changes:
im-config (0.22-2) unstable; urgency=low
.
* Fix wild card match logic error for all IM. Closes: #709921
Checksums-Sha1:
4138f5ec0447aabd15e489fcabfb47cd90265ce0 1143 im-config_0.22-2.dsc
12e2ebe89b3aa79965b6d5a41f410f6a6004c085 8630 im-config_0.22-2.debian.tar.gz
51cea630d8d32a5f77874924e35dc74744079e88 37060 im-config_0.22-2_all.deb
Checksums-Sha256:
c9c1dfcef5620b6ee54d7d65898ea6bf4aa1d25910f8c439fff4c9a22e17b8a9 1143
im-config_0.22-2.dsc
1d014cc2e17714342612d39a37fbf51a9d2c66312f665c481a25e0aef5dc3d6a 8630
im-config_0.22-2.debian.tar.gz
795e80939818917f777bf58c270fa4d905d5f8af8f32e1c07342db5243696952 37060
im-config_0.22-2_all.deb
Files:
ad96639b92423b46ae27bc4963e03e0b 1143 x11 optional im-config_0.22-2.dsc
b9edd1b01035497e2933ab9d08b32918 8630 x11 optional
im-config_0.22-2.debian.tar.gz
713c88bf1a6bf4cceaab10c7783fb509 37060 x11 optional im-config_0.22-2_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlGl+EsACgkQ6A/EwagGHzLi1ACeIFzcMGW2MR2IfS9mtlTwt4wu
DsUAniVzkITBRby5kxisM3eOYcVr0hRl
=5Q8s
-----END PGP SIGNATURE-----
--- End Message ---
