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(a)redhat.com
Reporter: wannabetheguy(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)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.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2110111