-
-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug(linux): v15.0.269 with Vietnamese keyboards not working with LibreOffice, Konsole, Firefox #7769
Comments
Newest beta I just downloaded, better on Libreoffice (still error if I press backspace to delete some character), still error on Firefox, Konsole |
Yes, Keyman uses surrounding text if the application supports it. |
Hmm, it works for me in LO and Firefox with ibus 15.0.269. Make sure that you reboot after installing a new version of ibus, otherwise the windowing system won't use the new binaries. Here's what I did:
15.0.269 doesn't work in Konsole which I wouldn't expect because I assume it doesn't support surrounding text. However, it also doesn't work in 16.0.108 where I'd expect it to work. 16.0.108 works correctly for me in LO Writer. @zenfas You mention problems with backspace - what problems are you getting exactly? With 16.0.108 in Firefox, things work in the address bar, but not in a text field on a page. Definitely something to look into. Thanks for reporting the problems, @zenfas. Can you please run |
I see a lot of applications in linux not support surrounding text good. According to @wengxt, we have some bugs in upstream QT, GTK or compositor about surrounding text and input method support. I really like to use surrounding text in Linux to come back and can edit text that already committed like on Windows, but surrounding text is not good enough and can't daily usage at the moment. In LO Writer, I test again, it's ok.
|
Indeed, surrounding text support is mixed on all of the major desktop platforms -- Windows, macOS, and Linux. Keyman on all three of these platforms works hard to fall back to injecting backspaces to emulate editing surrounding text but it can never be quite as reliable:
Surrounding text support can also be somewhat tricky for apps to get right. For example, Chrome on Android for some time deleted entire clusters instead of single codepoints when replacing content. We'll keep persevering and submitting patches to apps to support surrounding-text as best as we can. |
@ermshiperete : I tested with newest beta on PPA (
|
You should install the
By default Firefox is installed as a snap package on current Ubuntu versions. This comes with it's own version of the ibus libraries and thus doesn't have the patched ibus version. You'll have to use the non-snap version of Firefox, see e.g. https://askubuntu.com/a/1404401 for instructions.
We'll deal with that problem in due time. There are various options, but all are not pretty since they'd involve a lot of work. |
This is caused by running Firefox as a snap package. Because that brings it's own version of the ibus libraries it's missing the patched ibus version with the serialized output patch. Please remove the Firefox snap package and install the regular .deb package from the Firefox PPA - see https://www.omgubuntu.co.uk/2022/04/how-to-install-firefox-deb-apt-ubuntu-22-04 |
Describe the bug
I try Keyman on ibus-keyman and fcitx5-keyman with keyboard Vietnamese_telex or Vietnamese_vni and not work normally. (those keyboard work normal on Windows and Android). Other IM of ibus or fcitx5 work normally on my PC.
My OS: Kubuntu 22.10, install all relate keyman from official repo
On Kate app, it works normal
Reproduce the bug
Change to keyman keyboard on ibus or fcitx5 and type
Expected behavior
Work normally like keyman on Windows or Android
Related issues
No response
Keyman apps
Keyman version
15.0.269-1
Operating system
Kubuntu 22.10
Device
Laptop
Target application
LibreOffice, Konsole, Firefox...
Browser
Firefox 106
Keyboard name
vietnamese_telex, vietnamese_vni
Keyboard version
1.05
Language name
Vietnamese
Additional context
No response
The text was updated successfully, but these errors were encountered: