Bug 470524
Summary: | imsettings-daemon still not dead | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Matthias Clasen <mclasen> |
Component: | imsettings | Assignee: | Akira TAGOH <tagoh> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | tagoh |
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: | 2008-11-07 15:47:27 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: | |||
Bug Blocks: | 438943 |
Description
Matthias Clasen
2008-11-07 15:17:50 UTC
hmm, or maybe something else killed my settings daemon. I'd like to clarify: either imsettings-applet or imsettings-xim is invoked anyway regardless of whether IM is turned off, to allow people to switch IM on XIM dynamically. so I'm afraid I don't think it's not a good report to blame it emotionally from the reason it's just there and without certain information. I'm not quite sure what happened there though, I'm keen to investigate that issue if it often happens for you and there are any steps to reproduce it. please let me know if any. Yeah, sorry. This was a false alarm. I guess I was just not prepared for 3 or more im processes to run even if input methods are disabled. |