[Bug 1848144] Re: Screen reader isn't enabled on login screen or user session after installation
Ćukasz Zemczak
1848144 at bugs.launchpad.net
Wed Oct 16 11:46:15 UTC 2019
Looking at the casper code, it seems to me that it actually was never
written to properly work. The ubiquity-hooks/30accessibility hook
basically only really acts on accessibility options passed via the
cmdline. There is some strange code that seems to be for like a second
pass for $UBIQUITY_A11Y_PROFILE, but it seems to be only set in /usr/bin
/casper-a11y-enable - which is only ran if there are kernel cmdline
options set.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1848144
Title:
Screen reader isn't enabled on login screen or user session after
installation
Status in ubiquity package in Ubuntu:
Confirmed
Bug description:
ISO 20191014
After enabling the screen reader for an installation, the screen
reader isn't enabled on GDM or on the user's session.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1848144/+subscriptions
More information about the foundations-bugs
mailing list