Summary: | no easy way to wait until uim-xim is ready | ||
---|---|---|---|
Product: | UIM | Reporter: | d+bugzilla |
Component: | bridge: XIM | Assignee: | uim-bugs |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | enhancement | ||
Priority: | medium | CC: | d+bugzilla |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
patch to replace "unrealize" with "destroy"
non-sleep version of /usr/share/im-config/data/24_uim.rc patch for /usr/share/im-config/data/24_uim.rc |
Description
d+bugzilla
2011-07-14 18:26:37 UTC
Created attachment 60438 [details] [review] patch to replace "unrealize" with "destroy" I'm not sure what you want, but if you want to remove "sleep" from a rc file in im-config, this patch should work. Created attachment 60439 [details]
non-sleep version of /usr/share/im-config/data/24_uim.rc
Created attachment 60440 [details] [review] patch for /usr/share/im-config/data/24_uim.rc This patch for /usr/share/im-config/data/24_uim.rc * removes the sleep command * replaces uim-toolbar-qt with uim-toolbar-qt4 * adds a space just before `]' (2 places) I found that the uim helper applications (uim-toolbar-gtk-systray, uim-toolbar-gtk and uim-toolbar-qt4) aren't releated to the issue the original reporter mentioned in Debian BTS because the helper applications don't require uim-xim to launch (at least as for uim 1.8.0). Actually, when the 2 patches above are applied, even in my old box with 266MHz (not 2.66GHz) CPU, uim-toolbar-gtk-systray was successfully shown in a notification area without a sleep command. You can make sure that they don't require uim-xim by killing xim-uim and launch one of them: $ killall uim-xim $ uim-toolbar-gtk In my environment, the patch for uim-toolbar-gtk-systray is needed because without it, a uim-toolbar-gtk-systray process becomes a zombie (defunct) after login because systray_unrealize_cb() is called during a login process. FYI, for im-config, I filed 2 bug reports in Debian BTS. > I found that the uim helper applications (uim-toolbar-gtk-systray, > uim-toolbar-gtk and uim-toolbar-qt4) aren't releated to the issue the original > reporter mentioned in Debian BTS because the helper applications don't require > uim-xim to launch (at least as for uim 1.8.0). Actually, when the 2 patches > above are applied, even in my old box with 266MHz (not 2.66GHz) CPU, Ah, I just understood. I was confused what needed sleep command. > uim-toolbar-gtk-systray was successfully shown in a notification area without a > sleep command. You can make sure that they don't require uim-xim by killing > xim-uim and launch one of them: > $ killall uim-xim > $ uim-toolbar-gtk I tested in 1.5.7, 1.7.3 and 1.8.0, and confirmed. So, I will ask we can get rid of sleep commands from Debian im-config. > In my environment, the patch for uim-toolbar-gtk-systray is needed because > without it, a uim-toolbar-gtk-systray process becomes a zombie (defunct) after > login because systray_unrealize_cb() is called during a login process. > > FYI, for im-config, I filed 2 bug reports in Debian BTS. Thank you for your reporting. BTW, below, original report in Debian BTS, is still reproducible in 1.8.0. $ killall uim-xim $ uim-xim & xterm # <-- cannot use uim-xim in this xterm. $ killall uim-xim $ uim-xim & sleep 5 ; xterm # <-- can use uim-xim in this xterm -- im-config 0.18 does not need sleep anymore. So I cancel this bug report. Thank you. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.