Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 104296
Summary: | kinput2 inoperative after Candidate Selection window move | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Warren Togami <wtogami> |
Component: | kinput2 | Assignee: | Akira TAGOH <tagoh> |
Status: | CLOSED WONTFIX | QA Contact: | Bill Huang <bhuang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | eng-i18n-bugs |
Target Milestone: | --- | Keywords: | i18n |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-10-11 04:54:44 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Warren Togami
2003-09-12 08:53:56 UTC
It looks like similar bug with Bug#78017. and I can't reproduce this except gtk2 applications. Hmm, this sometimes causes kinput2 to fail totally and consume 100% CPU. Sometimes it fails completely only after several tries only in that individual application, and subsequently works again if you restart that application (like gedit). When it got stuck at 100% CPU usage, strace kept repeating this in a seemingly infinite loop: --- SIGPIPE (Broken pipe) @ 0 (0) --- select(6, [4 5], [], [], {0, 0}) = -1 EBADF (Bad file descriptor) getuid32() = 500 geteuid32() = 500 getuid32( kill failed to kill it. It took kill -9 to stop it. I suspect it's maybe another bug but it's just triggered by this. Could you please submit it as another bug and mention the sure way to reproduce the problem? Yes, I think the 100% CPU usage and kill -9 problem is a separate bug. Maybe Bug #114886. This is no longer imperative for FC3/RHEL4 as IIIMF is the preferred input method. Please verify that this is not an issue for RHEL3 customers. WONTFIX in RHEL3 Updates. |