Bug 431810
Summary: | doesn't stop the processes when IM is disabled on im-chooser | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Akira TAGOH <tagoh> |
Component: | scim | Assignee: | Peng Huang <phuang> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 9 | CC: | eng-i18n-bugs, petersen |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | F9 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-07-08 06:31:02 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: | |||
Bug Depends On: | 433578 | ||
Bug Blocks: |
Description
Akira TAGOH
2008-02-07 02:36:27 UTC
im-chooser is looking at PIDs when XIM_PROGRAM and AUXILIARY_PROGRAM is brought up. however /usr/bin/scim what currently scim.conf has for XIM_PROGRAM is bringing up multiple processes and exits after that. so that pid is invalid then. This is what's happening now. FYI. Fixed in 1.4.7-111 This change to scim-conf seems to break scim startup for some users. Probably starting up the XIM socket first may prevent SCIM starting up correctly sometimes. It might be a bug and/or race condition, and may depend on the speed of the machine perhaps... I modified scim.conf to use /usr/bin/scim to start scim related processe. In the new version scim.conf, scim will not start as a daemon. im-settings-daemon can close it by sending SIGINT or SIGTERM signal to scim processes. FIXED in version 1.4.7-12. Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |