Red Hat Bugzilla – Bug 488877
no response on xterm after switching IM
Last modified: 2009-11-24 00:48:56 EST
To keeps an issue in summary on track separately because the root cause is different.
+++ This bug was initially created as a clone of Bug #488773 +++
Created an attachment (id=334166)
X session errors caused by enabling SCIM
Description of problem:
After updating libgxim to release 0.3.2-4.fc10, xterm shows some regression: when running a program with a noticeable amount of text output (e.g. 'ls -R /'), then imsettings-applet starts grabbing a significant amount of CPU share of up to 10%. Note that SCIM is disabled at this point.
After opening GNOME menu item "Input Method" and enabling SCIM which is disabled by default, xterm does not accept any input from the keyboard anymore unlike gnome-terminal which continues to do so.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open GNOME session.
2. Start a program in an xterm window producing text output.
3. Run 'top' in a different window.
4. Open "Input Method" from GNOME menu and enable SCIM.
- Noticeable CPU load caused by imsettings-applet.
- Xterm unresponsive after enabling SCIM via "Input Method" dialog window.
Normal behaviour of xterm just as gnome-terminal.
Reverting libgxim to release 0.3.1-1.fc10 allows to restore normal operation.
Please note that IM won't still works without XIM reconnection support in applications because imsettings-applet, correctly XIM bridge in imsettings can't emulate XIM_CRAETE_IC event and bridge it after that properly because it's really hard to keep consistencies of input-method/input-context properties between new one and old one applications has.
GTK+ supports it with focus-in/out say. so switching IM works properly on GTK+ applications, but xterm doesn't.
After resolving this bug, you may want to file a bug again for xterm to support XIM reconnection.
Fixed in imsettings-0.106.2-1.fc11 for F-11. will backport a fix for F-10 after certain testing, FYI.
Do you want to push the backport?
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
We don't use XIM support in imsettings since F-11. close this as UPSTREAM.