[Bug 684474] New: screen reader doesn't read on the login screen

2 views
Skip to first unread message

orca

unread,
Sep 20, 2012, 8:53:55 AM9/20/12
to tel.conn...@gmail.com
https://bugzilla.gnome.org/show_bug.cgi?id=684474
orca | general | xdesktop

Summary: screen reader doesn't read on the login screen
Classification: Applications
Product: orca
Version: xdesktop
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: general
AssignedTo: orca-...@gnome.bugs
ReportedBy: mcl...@redhat.com
QAContact: orca-...@gnome.bugs
GNOME version: ---


When I flip the 'Screen Reader' switch on the login screen, nothing happens,
orca doesn't greet me :-(

Maybe the login screen session setup is somehow insufficient for a11y to work
fully ?

--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.

orca

unread,
Sep 20, 2012, 8:57:13 AM9/20/12
to tel.conn...@gmail.com
Matthias Clasen <mclasen> changed:

What |Removed |Added
----------------------------------------------------------------------------
GNOME target|--- |3.6

--- Comment #1 from Matthias Clasen <mcl...@redhat.com> 2012-09-20 12:57:08 UTC ---
Marking as a tentative blocker - having a11y work on the login screen is pretty
important.

orca

unread,
Sep 20, 2012, 12:07:23 PM9/20/12
to tel.conn...@gmail.com
André Klapper <a9016009> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |a901...@gmx.de

orca

unread,
Sep 20, 2012, 5:36:33 PM9/20/12
to tel.conn...@gmail.com
--- Comment #2 from Ray Strode [halfline] <rst...@redhat.com> 2012-09-20 21:36:31 UTC ---
Created an attachment (id=224864)
View: https://bugzilla.gnome.org/attachment.cgi?id=224864
Review: https://bugzilla.gnome.org/review?bug=684474&attachment=224864

data: at at-spi stuff to login session

In order for orca to work we need certain accessibility
services running. This commit adds those services.

orca

unread,
Sep 20, 2012, 5:36:52 PM9/20/12
to tel.conn...@gmail.com
Ray Strode [halfline] <rstrode> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |rst...@redhat.com

--- Comment #3 from Ray Strode [halfline] <rst...@redhat.com> 2012-09-20 21:36:50 UTC ---
something like attachment 224864 may help, but i haven't tested it yet.

orca

unread,
Sep 20, 2012, 5:54:00 PM9/20/12
to tel.conn...@gmail.com
--- Comment #4 from Ray Strode [halfline] <rst...@redhat.com> 2012-09-20 21:53:53 UTC ---
Created an attachment (id=224868)
View: https://bugzilla.gnome.org/attachment.cgi?id=224868
Review: https://bugzilla.gnome.org/review?bug=684474&attachment=224868

Matthias doesn't think the registryd bits should be needed.

Bastien points out these files aren't going to get AutostartCondition tested
since we use gnome-session -f.

One more (still untested) round:

data: at at-spi stuff to login session

In order for orca to work we need certain accessibility
services running. This commit adds those services.

orca

unread,
Sep 20, 2012, 6:57:29 PM9/20/12
to tel.conn...@gmail.com
--- Comment #5 from Matthias Clasen <mcl...@redhat.com> 2012-09-20 22:57:23 UTC ---
Grr, I was trying to use loginctl session-status to verify that the a11y bus
was launched in the gdm session. Looks like the a11y tools manage to escape the
cgroup ?! Not sure whats up with that.

Anyway, it still doesn't work, because orca relies on autostart conditions to
get launched, see /etc/xdg/autostart/orca-autostart.desktop.

orca

unread,
Sep 21, 2012, 6:06:59 PM9/21/12
to tel.conn...@gmail.com
Matthias Clasen <mclasen> changed:

What |Removed |Added
----------------------------------------------------------------------------
Depends on| |663721

gdm

unread,
Sep 21, 2012, 6:19:41 PM9/21/12
to tel.conn...@gmail.com
https://bugzilla.gnome.org/show_bug.cgi?id=684474
gdm | general | unspecified

Matthias Clasen <mclasen> changed:

What |Removed |Added
----------------------------------------------------------------------------
Component|general |general
Version|xdesktop |unspecified
AssignedTo|orca-...@gnome.bugs |gdm-...@gnome.bugs
Product|orca |gdm
QAContact|orca-...@gnome.bugs |gdm-...@gnome.bugs

--- Comment #6 from Matthias Clasen <mcl...@redhat.com> 2012-09-21 22:19:37 UTC ---
The patches in this bug are actually for gdm, so moving it there.
I've also added a dependency on the gnome-session bug that is the root cause.

gdm

unread,
Sep 22, 2012, 3:52:13 PM9/22/12
to tel.conn...@gmail.com
--- Comment #7 from Matthias Clasen <mcl...@redhat.com> 2012-09-22 19:52:11 UTC ---
Created an attachment (id=224995)
View: https://bugzilla.gnome.org/attachment.cgi?id=224995
Review: https://bugzilla.gnome.org/review?bug=684474&attachment=224995

don't run gnome-session in failsafe mode

gdm

unread,
Sep 22, 2012, 3:52:41 PM9/22/12
to tel.conn...@gmail.com
--- Comment #8 from Matthias Clasen <mcl...@redhat.com> 2012-09-22 19:52:36 UTC ---
Created an attachment (id=224996)
View: https://bugzilla.gnome.org/attachment.cgi?id=224996
Review: https://bugzilla.gnome.org/review?bug=684474&attachment=224996

add an autostart file for orca

gdm

unread,
Sep 22, 2012, 3:54:47 PM9/22/12
to tel.conn...@gmail.com
--- Comment #9 from Matthias Clasen <mcl...@redhat.com> 2012-09-22 19:54:42 UTC ---
These are more work-in-progress patches. They rely on the patches in the
blocking gnome-session bug. Even with these, I still haven't gotten orca to
start and stop correctly. I did see orca start once, but then it didn't stop
when I turned the switch off.

It seems as if gsettings monitoring doesn't work reliably. gnome-sessions debug
log did show my that the autostart condition monitor was triggering, but it
alway saw the same value. Maybe this is somehow caused by the bus being 'off to
the side' ?
Reply all
Reply to author
Forward
0 new messages