https://bugzilla.redhat.com/show_bug.cgi?id=1472607
fujiwara tfujiwar@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(angavrilov@gmail. | |com)
--- Comment #21 from fujiwara tfujiwar@redhat.com --- (In reply to Alexander Gavrilov from comment #20)
(In reply to fujiwara from comment #19)
Why don't you attach the log as I noted in comment 13 ?
I mean the ibus-daemon kicked by imsettings saves that log. This might include any warnings when you get your issue.
I'll try to make one next time it happens.
FYI: % cp /etc/X11/xinit/xinput.d/ibus.conf $HOME/.config/imsettings/xinputrc % vi $HOME/.config/imsettings/xinputrc XIM_ARGS="-r --xim --verbose"
And then imsettings log will save the ibus verbose log.
Also I wonder why you always got m17n info in your imsettings log. The info should be saved in one time when you run ibus-daemon after you install ibus-m17n.
No idea. One thing is that I have been upgrading my system for years without full reinstall, so there potentially might be some stale configuration somewhere confusing things.
I mean your ibus component files might be broken or you have no permission in cache dir and should be reviewed.