Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Mir Shell] running GTK apps makes at-spi2-registr hog CPU #1321

Closed
AlanGriffiths opened this issue Feb 25, 2020 · 2 comments · Fixed by #1322
Closed

[Mir Shell] running GTK apps makes at-spi2-registr hog CPU #1321

AlanGriffiths opened this issue Feb 25, 2020 · 2 comments · Fixed by #1322
Assignees
@AlanGriffiths

Comments

@AlanGriffiths
Copy link
Contributor

AlanGriffiths commented Feb 25, 2020 •
edited

Probably 20.04 only
@AlanGriffiths
Copy link
Contributor Author

AlanGriffiths commented Feb 25, 2020 •
edited

Workaround: Drop GTK_MODULES from the app environment:

$ cat ~/.config/miral-shell.config 
app-env=GDK_BACKEND=wayland:QT_QPA_PLATFORM=wayland:SDL_VIDEODRIVER=wayland:NO_AT_BRIDGE=-3:_JAVA_AWT_WM_NONREPARENTING=1:-GTK_MODULES

@AlanGriffiths AlanGriffiths changed the title [Mir Shell] running X11 apps makes at-spi2-registr hog CPU [Mir Shell] running GTK apps makes at-spi2-registr hog CPU Feb 25, 2020
@AlanGriffiths AlanGriffiths self-assigned this Feb 25, 2020
@AlanGriffiths
Copy link
Contributor Author

So the problem is that we don't want to "force" accessibility when we have no support in miral-shell.

One can force enabling accessibility (but ideally it should be automatic thanks to the property mentioned above):

export GTK_MODULES=gail:atk-bridge
export OOO_FORCE_DESKTOP=gnome
export GNOME_ACCESSIBILITY=1
export QT_ACCESSIBILITY=1
export QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1

https://www.freedesktop.org/wiki/Accessibility/AT-SPI2/

@AlanGriffiths AlanGriffiths mentioned this issue Feb 25, 2020
Merged
bors bot added a commit that referenced this issue Feb 25, 2020
@bors @AlanGriffiths
Merge #1322
57dc965 
1322: [miral] Unset any app environment variables that might force enabling accessibility r=wmww a=AlanGriffiths

[miral] Unset any app environment variables that might force enabling accessibility. (Fixes: #1321)

See https://www.freedesktop.org/wiki/Accessibility/AT-SPI2/ for a list of such variables.

Co-authored-by: Alan Griffiths <alan@octopull.co.uk>
@bors bors bot closed this as completed in 688b2a8 Feb 27, 2020
wmww pushed a commit that referenced this issue Apr 1, 2020
@bors @AlanGriffiths @wmww
Merge #1322
0218671 
1322: [miral] Unset any app environment variables that might force enabling accessibility r=wmww a=AlanGriffiths

[miral] Unset any app environment variables that might force enabling accessibility. (Fixes: #1321)

See https://www.freedesktop.org/wiki/Accessibility/AT-SPI2/ for a list of such variables.

Co-authored-by: Alan Griffiths <alan@octopull.co.uk>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AlanGriffiths AlanGriffiths

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[miral] Unset any app environment variables that might force enabling accessibility canonical/mir
1 participant
@AlanGriffiths