Ubuntu
ubiquity package

screen reader does not read ubiquity window after it is launched in "Try Ubuntu" session

  1. Mantic (23.10)
  2. Bug #1923052
Bug #1923052 reported by Norbert
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
at-spi2-core (Ubuntu)
Status tracked in Mantic
Jammy
Incomplete
Undecided
Unassigned
Mantic
Incomplete
Undecided
Unassigned
orca (Ubuntu)
Status tracked in Mantic
Jammy
Incomplete
Undecided
Unassigned
Mantic
Incomplete
Undecided
Unassigned
ubiquity (Ubuntu)
Status tracked in Mantic
Jammy
Confirmed
High
Unassigned
Ubuntu ubuntu-22.04
Mantic
Confirmed
High
Unassigned
Ubuntu ubuntu-22.04

Bug Description

Steps to reproduce:
1. Run Ubuntu MATE 21.04 installation media
2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info testcase by pressing <Alt>+<Super>+<S> to activate screenreader with shown Ubiquity window, press <Tab> to select some button

Expected result:
* screen reader reads ubiquity window

Actual result:
* screen reader does not read ubiquity window

Note: screen reader actually works, it reads other windows - for example the terminal opened by <Ctrl>+<Alt>+<T>.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.14
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu61
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.461
Date: Thu Apr 8 13:01:30 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

See original description
Revision history for this message
Norbert (nrbrtx) wrote :
Norbert (nrbrtx)
description: updated
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1923052

tags: added: iso-testing
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in at-spi2-core (Ubuntu):
status: New → Confirmed
Changed in orca (Ubuntu):
status: New → Confirmed
Changed in ubiquity (Ubuntu):
status: New → Confirmed
Norbert (nrbrtx)
tags: added: impish
Revision history for this message
Norbert (nrbrtx) wrote :

Impish is still affected, tested on

Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20211002)

Revision history for this message
Brian Murray (brian-murray) wrote :

I seem to recall somebody saying that this was a permissions issue with the way ubiquity is launched from the live desktop environment. I think the comment was along the lines of ubiquity running as root but the desktop session is not so orca can't read the screen.

tags: added: rls-jj-incoming
Revision history for this message
Sebastien Bacher (seb128) wrote :

The issue was reported on hirsute and sounds similar to bug #1231091 which was fixed in 21.10, is that still an issue on the current daily image? is that flavor specific or do you get the issue on the ubuntu ISO?

Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
Changed in orca (Ubuntu):
status: Confirmed → Incomplete
Changed in at-spi2-core (Ubuntu):
status: Confirmed → Incomplete
Brian Murray (brian-murray)
Changed in ubiquity (Ubuntu):
importance: Undecided → High
Revision history for this message
Brian Murray (brian-murray) wrote :

I tested this following the instructions in test case 1309 and did not hear the screen reader read the ubiquity window after choosing Try Ubuntu. The screen reader was working though and happily read other windows.

Changed in ubiquity (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

I also tested this with an Ubuntu 21.10 image and observed the same behavior as with Jammy.

tags: removed: rls-jj-incoming
tags: added: fr-2159
Brian Murray (brian-murray)
Changed in ubiquity (Ubuntu Jammy):
milestone: none → ubuntu-22.04
Revision history for this message
Brian Murray (brian-murray) wrote :

I tested this again today with an Ubuntu desktop legacy image dated 20230918 and encountered the same bug where the screenreader works with ubiquity if you do not choose "Try Ubuntu" and launch the installer again.

If this isn't going to be fixed or isn't fixable then I suggest we close this out as "Won't Fix" and release the issue.

tags: added: rls-mm-incoming
Brian Murray (brian-murray)
summary: - screen reader does not read ubiquity window
+ screen reader does not read ubiquity window after it is launched in "Try
+ Ubuntu" session
Revision history for this message
Tim Holmes-Mitra (timhm) wrote :

Not a release blocker.

tags: added: rls-mm-notfixing
removed: rls-mm-incoming
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.