Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: no response on xterm after switching IM
https://bugzilla.redhat.com/show_bug.cgi?id=488877
Summary: no response on xterm after switching IM
Product: Fedora
Version: 10
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: imsettings
AssignedTo: tagoh(a)redhat.com
ReportedBy: tagoh(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: jfrieben(a)hotmail.com, tagoh(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Depends on: 488773
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Clone Of: 488773
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)
--> (
https://bugzilla.redhat.com/attachment.cgi?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):
libgxim-0.3.2-4.fc10.x86_64
How reproducible:
Always.
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.
Actual results:
- Noticeable CPU load caused by imsettings-applet.
- Xterm unresponsive after enabling SCIM via "Input Method" dialog window.
Expected results:
Normal behaviour of xterm just as gnome-terminal.
Additional info:
Reverting libgxim to release 0.3.1-1.fc10 allows to restore normal operation.
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.