Screen reader is not auto-enabled on first login if enabled when installing

Bug #1796275 reported by Andrea Azzarone on 2018-10-05
This bug affects 1 person
Affects Status Importance Assigned to Milestone
casper (Ubuntu)
ubiquity (Ubuntu)

Bug Description

As per iso testcase the screen-reader is supposed to be auto activated if the user enabled it when installing. This is not the case in the ISO (5oct2018)

Note: as of 19.04, the user session has the screen reader enabled, GDM though hasn't.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 5 12:58:47 2018
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity
InstallationDate: Installed on 2018-10-05 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Andrea Azzarone (azzar1) wrote :
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:

tags: added: iso-testing
tags: added: id-5bbf6b340c732e447bb27401
Sebastien Bacher (seb128) wrote :

The a11y handling has been buggy since we switched away from Unity and dropped a11y-profile-manager, casper/ubiquity still call to that tool which is not on the iso anymore.

That's not a regression from bionic and too much change to refactor that this cycle but we added a trello card to our backlog for next cycle

We don't want to add back the a11y-profile-manager tool because it's unmaintained, probably makes sense to revert the change that added it and go back to the old way of writting gsettings key (though that needs tweaking for lightdm->gdm)

Changed in ubiquity (Ubuntu):
importance: Undecided → High
status: New → Triaged
affects: ubiquity (Ubuntu Disco) → casper (Ubuntu Disco)
Brian Murray (brian-murray) wrote :

This was likely fixed with the following upload:

casper (1.403) disco; urgency=medium

  * bin/casper-a11y-enable, scripts/casper-bottom/30accessibility,
    - revert the code handling the a11y profiles to its pre-xenial version,
      the new a11y-profile-manager component which handled that in xenial
      had been deprecated and is not installed since bionic.

 -- Sebastien Bacher <email address hidden> Wed, 10 Apr 2019 16:08:10 +0200

This appears to work here; if I start with the screen reader enabled in the isolinux splash (F5,
 hit arrow down three times, enter).

Changed in casper (Ubuntu Disco):
status: Triaged → Fix Released
Sebastien Bacher (seb128) wrote :

(the casper changes were done but there is likely some more work that can/should be done on ubiquity)

Changed in ubiquity (Ubuntu Disco):
importance: Undecided → High
status: New → Triaged
Didier Roche (didrocks) on 2019-04-17
description: updated
Sebastien Bacher (seb128) wrote :

The remaining issue is with the login screen, the script has no logic for gdm, let's handle that in a new report, bug #1825112

Changed in ubiquity (Ubuntu Disco):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers