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
feat(linux): Add support for Wayland #4273
Comments
This happens on Debian Buster 10.7. On Ubuntu 20.04 things work in gedit, but not in gnome-terminal. To see whether Wayland or X11 is used, run:
(or easier: To allow Wayland login on Ubuntu 20.04, edit |
A little more research shows that Keyman 14.0 kind of works with Wayland: it doesn't survive an ibus restart, which means after installing it's necessary to reboot (or maybe logout/login would be sufficient). But even then things don't work properly: With Eurolatin, typing I was testing this in a VM, and I just noticed that my host machine behaves strangely, so that might have an impact... Note that Debian Buster has neither |
Is this a pre-requisite for releasing packages on 21.04? See https://community.software.sil.org/t/how-does-one-go-about-installing-keyman-14-on-ubuntu-21-04/4728 |
Hello / Is there a the roadmap for wayland integration ? |
Yes, if everything goes as planned Keyman will work with Wayland in the upcoming version 15. We're currently working on it. In fact, most things already seem to work when using Wayland, but there seems to be a bug in ibus that prevents surrounding text from working properly which results in characters not being replaced. |
This change skips the four failing Wayland tests so that the builds pass on CI. They will have to be re-enabled once Wayland support is implemented (#4273). Also remove `run-tests.sh` which got moved to `scripts/run-tests.sh` but I forgot to delete the old one when I did the move.
This change skips the four failing Wayland tests so that the builds pass on CI. They will have to be re-enabled once Wayland support is implemented (#4273). Also remove `run-tests.sh` which got moved to `scripts/run-tests.sh` but I forgot to delete the old one when I did the move.
When using Wayland `im-wayland.so` (which is part of libgtk) gets loaded into the client app instead of `im-ibus.so`. This means that our ordered output doesn't work with Wayland. This change works around a problem with keyboards that use multiple consecutive backspace actions. Because method calls get processed asynchronously some backspaces get lost. In clients that support surrounding text we can count the consecutive backspaces and then do one call to delete surrounding text with the appropriate number of characters. This can be tested with "Khmer Angkor" keyboard by typing `xEjmr`, or with "Vedic Sanskrit Devanagari Phonetic (ITRANS)" keyboard by typing `shrI`. Part of #4273.
# Keyman Conventional Commit suggestions: # - Consider appending the text ". Fixes #4273" to your commit message.
Another problem with the Eurolatin(SIL) keyboard where the context is wrong: |
# Keyman Conventional Commit suggestions: # - Consider appending the text ". Fixes #4273" to your commit message.
# Keyman Conventional Commit suggestions: # - Consider appending the text ". Fixes #4273" to your commit message.
Follow-up of code review comments. # Keyman Conventional Commit suggestions: # - Consider appending the text ". Fixes #4273" to your commit message.
This will be available in Keyman 17. |
Currently Keyman doesn't work properly when Wayland instead of X11 is used (see #4122).
The text was updated successfully, but these errors were encountered: