Bug 2110111

Summary: imsettings-daemon log spam due to fcitx5
Product: [Fedora] Fedora Reporter: nsk <wannabetheguy>
Component: imsettingsAssignee: Akira TAGOH <tagoh>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: i18n-bugs, tagoh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Fixed In Version: imsettings-1.8.3-5.fc37 imsettings-1.8.3-5.fc36 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-09 04:10:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
log with fcitx5 selected, then switched to ibus none

Description nsk 2022-07-23 17:29:54 UTC
Created attachment 1898954 [details]
log with fcitx5 selected, then switched to ibus

Description of problem:
I've recently been using Wayland more on Fedora 36 KDE. I've been using fcitx5 on x11, so I set that through im-chooser as that controls the configs in ~/.config/environment.d/.
After doing so, imsettings-daemon immediately starts using a non-zero amount of CPU and starts constantly writing to the disk around 100KiB/s. This appears to be to the log file at ~/.cache/imsettings/. When I discovered this, it had made a log file 9GiB.
Launching im-chooser again and selecting none or ibus, the logging immediately stops. However, that pops up with "Failed to switch Input Method - GDBus.Error:com.redhat.imsettings.Error : Couldn't send a signal to the main process successfully." though sets the environment.d configs successfully.

Version-Release number of selected component (if applicable):

How reproducible:
Happens every time.

Steps to Reproduce:
1. Set input method to fcitx5 with im-chooser
2. Watch log generate
3. Set input method to none or ibus  

Actual results:
Log spam due to fcitx5 dying and restarting?

Expected results:
imsettings-daemon not failing to handle fcitx5

Additional info:
Fedora 36 KDE, Wayland. The usability of fcitx5 doesn't seem to be affected by having im-chooser set to anything other than fcitx5, but I assumed that I would want it selected there. The fact it's present in im-chooser and causes this issue is still a problem.

Comment 1 Akira TAGOH 2022-08-04 09:14:15 UTC
imsettings has capability to stop restarting an input-method forever but it seems not working. I could increase a threshold though, the root cause for the loop of restarting isn't a problem in imsettings. as that log said, you may have fcitx process running already. someone brought it up and imsettings also tried. then, this state of conflict happened.

For some discussions around input method support on Wayland, imsettings doesn't work well there and/or no need to do something. I'll disable imsettings on Wayland.

Comment 2 Fedora Update System 2022-08-09 04:08:51 UTC
FEDORA-2022-b29c952f08 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b29c952f08

Comment 3 Fedora Update System 2022-08-09 04:10:35 UTC
FEDORA-2022-b29c952f08 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Fedora Update System 2022-08-09 04:28:47 UTC
FEDORA-2022-9d1289fe9d has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-9d1289fe9d

Comment 5 Fedora Update System 2022-08-10 01:38:28 UTC
FEDORA-2022-9d1289fe9d has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-9d1289fe9d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9d1289fe9d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2022-08-14 02:37:03 UTC
FEDORA-2022-9d1289fe9d has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.