Package: uim-xim Version: 1:0.4.6final1-2 Severity: normal When using loading uim-xim and another program that needs to use it one right after the other (e.g. in an .xsession) programs started after uim-xim but before uim-xim is ready to service them can't use uim.
This comes up for me if I try to make an .xsession that looks something like this: uim-xim & xterm The xterm loads up after uim-xim has been started, but before it's ready to accept connections from XIM clients. I can fix this by doing: uim-xim & sleep N xterm Where N=1 on most machines (like this one, a new amd64), but N=2 or 3 on some really slow machines (notably, a heavily loaded PII-450 I have, so we're not just saying hypothetically!) It would be nice if there were an option to/wrapper for uim-xim that allowed it to daemonize itself and only return to the caller when it was not only daemonized, but actually ready to accept XIM clients. Then the proposed .xsession could be something like: uim-xim --daemonize xterm And everything would work nicely. =) -- System Information: Debian Release: 3.1 Architecture: amd64 (x86_64) Kernel: Linux 2.6.9-10-amd64-k8 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages uim-xim depends on: ii libatk1.0-0 1.8.0-4 The ATK accessibility toolkit ii libc6 2.3.2.ds1-20.0.0.1.pure64 GNU C Library: Shared libraries an ii libgcc1 1:3.4.3-12 GCC support library ii libglib2.0-0 2.6.3-1 The GLib library of C routines ii libgtk2.0-0 2.6.2-4 The GTK+ graphical user interface ii libpango1.0-0 1.8.1-1 Layout and rendering of internatio ii libstdc++5 1:3.3.5-12 The GNU Standard C++ Library v3 ii libuim0 1:0.4.6final1-2 Simple, secure, and flexible input ii libx11-6 4.3.0.dfsg.1-12 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-12 X Window System miscellaneous exte ii uim-common 1:0.4.6final1-2 Common files for uim ii uim-utils 1:0.4.6final1-2 Utilities for uim ii xlibs 4.3.0.dfsg.1-12 X Keyboard Extension (XKB) configu -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
