https://bugzilla.redhat.com/show_bug.cgi?id=1625187
fujiwara <tfujiwar(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |MODIFIED
--- Comment #3 from fujiwara <tfujiwar(a)redhat.com> ---
(In reply to Bhushan Barve from comment #0)
Description of problem: Tried to select an Emoji using mouse from the
emoji
category list window. After that, tried to invoke the same window again
using ctrl + shift + e. However, was not able to invoke it. Had to reboot.
This works fine with keyboard selection.
This is caused because gnome-shell does not send focus-in event to
ibus-extension-gtk3 because ibus emojier expects focus-en event and terminates
ctrl-shift-e feature.
But the ibus implementation causes this bug and now I changed it and ibus
terminates ctrl-shift-e feature immediately when an emoji is chosen whether
focus-in event comes or not.
https://github.com/ibus/ibus/commit/1c6565e205528a45e88a84ba2a328f9035875c8d
(In reply to Mike FABIAN from comment #1)
I see the same problem, also when selecting the emoji using the
keyboard
only and not using the mouse.
This includes three issues actually.
I did this:
- Type Ctrl-Shift-e Space to open the emoji category list
- Type Space again to go the "people" category
- Type Return to open the "people" category
- Type Return again to select the first smiley in that category
I don’t yet get that smiley inserted into gedit, I still see the
underlined "e"
This is caused because gnome-shell does not send focus-in event and it's filed
as
https://gitlab.gnome.org/GNOME/gnome-shell/issues/573 .
If you cannot cancel "e" with Escape key, it's caused because gnome-shell
does
not implement HidePreedit feature and it's filed as
https://gitlab.gnome.org/GNOME/gnome-shell/issues/431 .
at this moment
- Type space again
The smiley appears in the application (I am using gedit)
After you type anything, focus-in event comes and the emoji is output but the
wrong order causes SEGV.
--
You are receiving this mail because:
You are on the CC list for the bug.