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 114886
Summary: | kinput2 100% CPU, kill -9, | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Warren Togami <wtogami> |
Component: | Canna | Assignee: | Akira TAGOH <tagoh> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | eng-i18n-bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-04-13 00:59:17 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
2004-02-04 00:21:57 UTC
One more odd thing... It does not fail and start looping if I launch it manually from the terminal in that sequence rather than launch it from a shell script. Triggering it could be a timing issue too... Hmm, even if I tried your step on my test machine, I couldn't reproduce this problem... so what version of Canna are you using? I saw similar bug on ia64 and not sure if it's the real fix, but Canna works again by that fix. I see pretty much this behaviour every time after a clean ja install of FC1 Test1/recent trees when running a GNOME session. I never see this failure on my machine either. FC2 test1 or all earlier.
Works very comfortable here, and no warning.
> Warning: Select failed; error code 9
Network issue? My setting is firewall off in the office.
Yesterday I translated gnumeric ja.po for several hours on my FC2 test1, gnome-terminal, vi and kinput2. And it didn't reproduce... I need to add to say this prob. is reported so many times on Fedora JP list too, but just doesn't happen for me... Ok, I can reproduce this problem now. and hopefully this problem would be fixed in the next release. This problem shouldn't appears on 3.7p1-4. please test it. Thanks, I haven't seen any more hanging of kinput2 recently. :-) |