Package: im-config Version: 0.18~quantal1 Severity: normal Tags: upstream (Sorry for report it from ubuntu) im-config 0.18 uses im-launch to fix some old problem, but also brought some new problem. in current initialization sequence, the final command will be:
dbus-launch im-launch command-for-start-up This ignore the fact that dbus-daemon launched by dbus-launch is not covered under required im environment variable. In some case, dbus-daemon will be used to start process by dbus service name, those application can also be GUI application, and it will make those application running with no im environment variable set. For example, ktp-text-ui (kde telepathy text ui) is suffering from this problem. The fix to this problem is simple, keep the code that start input method in im-launch, but move the environment setting code to 70im-config_launch, so dbus-daemon will be also set with those environment variable, and so will those process started by dbus-daemon. -- System Information: Debian Release: wheezy/sid APT prefers quantal-updates APT policy: (500, 'quantal-updates'), (500, 'quantal-security'), (500, 'quantal'), (100, 'quantal-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5.0-18-generic (SMP w/3 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages im-config depends on: ii dialog 1.1-20120215-2ubuntu1 ii gettext-base 0.18.1.1-9ubuntu1 ii zenity 3.4.0-2 Versions of packages im-config recommends: ii dialog 1.1-20120215-2ubuntu1 ii x11-common 1:7.7+1ubuntu4 im-config suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
