Feature #11428

"Screen Reader" does nothing in new Greeter

Added by sajolida 2016-05-17 14:38:57 . Updated 2020-04-15 06:01:14 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Accessibility
Target version:
Start date:
2016-05-17
Due date:
% Done:

100%

Feature Branch:
feature/8230-greeter-revamp-phase1
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Welcome Screen
Deliverable for:

Description

Either make it work or hide it for now.


Subtasks


History

#1 Updated by alant 2016-08-16 14:54:16

When launched in a desktop session (with some tweaks to make errors non-fatal), the greeter has some things being read by the screen reader. On the other hand, when launching gedit in the greeter session, nothing happens. So the greeter session seem to miss a required component for the screenreader to work. But ps shows that orca is working.

#2 Updated by alant 2016-08-16 15:29:22

I tried it add Debian-gdm to the audio group, as suggested by https://help.gnome.org/admin/gdm/stable/gdm.html#accessibility but it’s not enough.

#3 Updated by alant 2016-08-16 15:45:45

The screen reader works fine under a standard instralled debian jessie’s greeter. The same processes seem to be running…

#4 Updated by intrigeri 2016-08-17 00:26:43

> When launched in a desktop session (with some tweaks to make errors non-fatal), the greeter has some things being read by the screen reader. On the other hand, when launching gedit in the greeter session, nothing happens. So the greeter session seem to miss a required component for the screenreader to work. But ps shows that orca is working.

Did you look in the Journal, e.g. for firewall rejection messages? Our firewall grants access to TCP port 4101 to the amnesia user, but there’s no such thing about the Debian-gdm user.

#5 Updated by alant 2016-08-17 02:41:08

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA
  • Feature Branch set to feature/8230-greeter-revamp-phase1

#6 Updated by alant 2016-08-17 02:42:51

Allowing Debian-gdm access to port 4101 indeed fixed the issue. Thanks!

#7 Updated by alant 2016-08-19 05:28:11

  • Status changed from In Progress to Fix committed
  • Assignee deleted (alant)
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

#8 Updated by alant 2016-11-15 09:40:49

  • Status changed from Fix committed to Resolved

#9 Updated by intrigeri 2020-04-15 06:01:14

  • Affected tool changed from Greeter to Welcome Screen