Enabling screen reader and on-screen keyboard options from the a11y indicator do not start the application in question.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity Greeter |
Fix Released
|
High
|
Unassigned | ||
unity-greeter (Ubuntu) |
Fix Released
|
High
|
Michael Terry |
Bug Description
affects ubuntu/
affects unity-greeter
tag a11y
When choosing either the screen reader or on-screen keyboard options from the accessibility indicator in the lightdm unity greeter, one would expect the associated applications, orca and onboard to start, however this is not the case. The greeter sets the appropriate gsettings keys, but nothing more occurs. It also appears that at-spi is also not launched.
From some further investigation, I have determined that the session manager launches these applications, based on the given gsettings keys in the relevant desktop files. The unity greeter needs to load these applications itself, however they cannot be hard-coded into the greeter itself, so that people can change the tools they use, particularly in the on-screen keyboard usecase.
Related branches
- Unity Greeter Development Team: Pending requested
-
Diff: 40 lines (+19/-4)1 file modifiedsrc/user-list.vala (+19/-4)
Changed in unity-greeter: | |
status: | New → Triaged |
Changed in unity-greeter (Ubuntu): | |
status: | New → Triaged |
Changed in unity-greeter: | |
importance: | Undecided → High |
Changed in unity-greeter (Ubuntu): | |
importance: | Undecided → High |
Changed in unity-greeter (Ubuntu): | |
assignee: | nobody → Michael Terry (mterry) |
Changed in unity-greeter (Ubuntu): | |
status: | Triaged → In Progress |
Changed in unity-greeter: | |
status: | Triaged → Fix Committed |
Changed in unity-greeter (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in unity-greeter: | |
status: | Fix Committed → Fix Released |
So trunk loads onboard correctly (though it is hardcoded right now). Screen reader still isn't done. I'm looking into it.