https://bugzilla.redhat.com/show_bug.cgi?id=2110111
Bug ID: 2110111 Summary: imsettings-daemon log spam due to fcitx5 Product: Fedora Version: 36 Hardware: x86_64 Status: NEW Component: imsettings Assignee: tagoh@redhat.com Reporter: wannabetheguy@gmail.com QA Contact: extras-qa@fedoraproject.org CC: i18n-bugs@lists.fedoraproject.org, tagoh@redhat.com Target Milestone: --- Classification: Fedora
Created attachment 1898954 --> https://bugzilla.redhat.com/attachment.cgi?id=1898954&action=edit 21 second 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): imsettings-1.8.3-2.fc36
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.
https://bugzilla.redhat.com/show_bug.cgi?id=2110111
Akira TAGOH tagoh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Doc Type|--- |If docs needed, set a value Status|NEW |ASSIGNED
--- Comment #1 from Akira TAGOH tagoh@redhat.com --- 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.
https://bugzilla.redhat.com/show_bug.cgi?id=2110111
Red Hat One Jira (issues.redhat.com) redhat-one-jira@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Link ID| |Red Hat Issue Tracker | |FC-563
https://bugzilla.redhat.com/show_bug.cgi?id=2110111
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |MODIFIED
--- Comment #2 from Fedora Update System updates@fedoraproject.org --- FEDORA-2022-b29c952f08 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b29c952f08
https://bugzilla.redhat.com/show_bug.cgi?id=2110111
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |CLOSED Fixed In Version| |imsettings-1.8.3-5.fc37 Resolution|--- |ERRATA Last Closed| |2022-08-09 04:10:35
--- Comment #3 from Fedora Update System updates@fedoraproject.org --- 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.
https://bugzilla.redhat.com/show_bug.cgi?id=2110111
--- Comment #4 from Fedora Update System updates@fedoraproject.org --- FEDORA-2022-9d1289fe9d has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-9d1289fe9d
https://bugzilla.redhat.com/show_bug.cgi?id=2110111
--- Comment #5 from Fedora Update System updates@fedoraproject.org --- 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.
https://bugzilla.redhat.com/show_bug.cgi?id=2110111
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed In Version|imsettings-1.8.3-5.fc37 |imsettings-1.8.3-5.fc37 | |imsettings-1.8.3-5.fc36
--- Comment #6 from Fedora Update System updates@fedoraproject.org --- 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.
i18n-bugs@lists.fedoraproject.org