https://bugzilla.redhat.com/show_bug.cgi?id=1472607
fujiwara <tfujiwar(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |needinfo?(angavrilov@gmail.
| |com)
--- Comment #15 from fujiwara <tfujiwar(a)redhat.com> ---
(In reply to Alexander Gavrilov from comment #14)
Initially: there is no ibus icon in the tray, keyboard layout is
wrong,
hotkey doesn't work, ibus-setup pops up the window.
You didn't attach a log file as I noted in comment 13.
Also I wonder attachment 1300880 is not correct.
I also need the $HOME/.cache/imsettings/log before you restart ibus.
Killing and manually starting ibus-ui-gtk3 shows up the icon, but
hotkey
still doesn't work. Trying to switch layouts by clicking on the icon doesn't
really work either, probably because I have it configured so that every app
has separate selected layout, and clicking on the icon switches focus to the
tray temporarily so it doesn't change the layout of the really active app.
OK.
but the question is what breaks it in the first place.
Probably it's my question to you since you didn't give the exact info.
As I just remember now, probably you configure keyboard settings with KDE
instead of IBus.
Can you confirm to run systemsettings5 ?
"System Settings" -> "Hardware" -> "Input Devices"
-> "Keyboard" -> "Layouts"
And disable "Configure layouts".
Re race condition, it is just a guess as it's a likely cause of a
heisenbug
appearing under high load conditions; and I imagine it as a race between
different interdependent components of ibus and kde trying to start up at
the same time, possibly even in different processes. I actually see app
windows appear on the screen before the panel with the icon tray shows up
and pushes them aside, so the whole thing obviously isn't starting up in
completely orderly fashion.
Maybe it's not true.
--
You are receiving this mail because:
You are on the CC list for the bug.