issue #7421 : keyboard unresponsive during startup/shutdown of Hop GUI#7422
Closed
mattcasters wants to merge 1 commit into
Closed
issue #7421 : keyboard unresponsive during startup/shutdown of Hop GUI#7422mattcasters wants to merge 1 commit into
mattcasters wants to merge 1 commit into
Conversation
Contributor
Author
|
Getting some flashing when rendering, investigating further. |
Contributor
Author
|
It was a good idea but it causes too much flickering because of the xim back-end usage, which is really old. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
issue #7421
A fix for a super annoying issue on Linux desktops when starting/stopping the Hop GUI.
Adds option system variable
HOP_KEEP_A11Yand the documentation for it.Fix keyboard input stall on Linux Hop GUI startup/shutdown (#7421)
Problem
On Linux (especially Ubuntu/GNOME on X11 with many SWT plugins), Hop GUI can temporarily stop accepting keyboard input while starting up or shutting down. The AT-SPI accessibility bridge and IBus can block the X11 event loop during that window.
Solution
On Linux,
hop-gui.shand the mainhoplauncher now set these environment variables by default:NO_AT_BRIDGE=1GTK_IM_MODULE=ximIBUS_DISABLE=1This runs in the existing Linux
caseblock, before the Wayland workaround for #4252.Accessibility / IME opt-out
Users who need full accessibility or IBus-based input methods (e.g. screen readers, CJK IME) can opt out:
export HOP_KEEP_A11Y=1 ./hop-gui.shWhen
HOP_KEEP_A11Yis set to any non-empty value, none of the three variables above are exported.Files changed
Launcher scripts (code fix)
assemblies/static/src/main/resources/hop-gui.shassemblies/static/src/main/resources/hopUser manual (documentation)
docs/hop-user-manual/modules/ROOT/pages/hop-gui/linux-desktop.adocdocs/hop-user-manual/modules/ROOT/pages/snippets/variables/hop-keep-a11y.adocdocs/hop-user-manual/modules/ROOT/pages/hop-gui/index.adocdocs/hop-user-manual/modules/ROOT/nav.adocdocs/hop-user-manual/modules/ROOT/pages/installation-configuration.adocHOP_KEEP_A11Ysnippetdocs/hop-user-manual/modules/ROOT/pages/variables.adocHOP_KEEP_A11YsnippetTesting suggestions for reviewers
HOP_KEEP_A11Y=1— Confirm screen reader / IBus IME still works as before the change.GDK_BACKEND=x11still applies independently ofHOP_KEEP_A11Y.Related issues