If I try to type with ibus-typing-booster in Qt applications and commit a word by typing space, no space is inserted after the word. For example:
QT_IM_MODULE=ibus kate &
Select the English engine of ibus-typing-booster and type some word like "test",
type space to commit. The word "test" is committed into kate, but no space
appears after the word, the cursor is directly behind the word "test".
This is because this line
self.forward_key_event(key.val, key.code, key.state)
in hunspell_table.py from ibus-typing-booster does nothing anymore.
This line in context in the source code is here:
(By the way, when trying “XMODIFIERS=@im=ibus QT_IM_MODULE=xim kate”, input does not work at all, so this cannot be used as a workaround).
(In reply to Mike FABIAN from comment #0)
> (By the way, when trying “XMODIFIERS=@im=ibus QT_IM_MODULE=xim kate”, input
> does not work at all, so this cannot be used as a workaround).
Apparently Qt5 does not support XIM anymore:
forwardKeyEvent seems to be not implemented in Qt5:
A similar bug about another function which is not implemented in Qt5 was
“Qt5 IBus input context does not implement hide_preedit_text()”
Thanks for filing the bug but it's late. Now the git head is 5.8.
Maybe the target is f26.
I investigated qt5-qtbase and I found 'ForwardKeyEvent' signal is defined correctly but the QT5 module cannot receive that signal in QIBusInputContextProxy::qt_static_metacall().
I have no idea and will file a bug in upstream.
Also QT5 module does not have an API likes gdk_keyval_to_unicode().
XLookupString() will be used?
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.
Peng Wu fixed this recently.
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.