[Bug 1546317] Re: Accessibility indicator is missing from ubiquity-dm at the "Try Ubuntu" dialog

Luke Yelavich luke.yelavich at canonical.com
Tue Apr 5 06:51:19 UTC 2016


Ok, almost all implemented here, testing as I go.

I have a bit to do in casper too to make this all work, hense casper
being added as a task. As for ubiquity, the changes work, however seems
something is running in ubiquity on the mate live image that prevents
Orca from being launched with the shortcut key super + alt + S. The same
changed code works properly in the Ubuntu live environment for Unity, so
its either something running from mate that is intercepting the
keystroke, or for some reason, the super key is being interpreted
differently in ubiquity, why I don't know, but I did note that changing
a shortcut key in Mate's keyboard shortcuts shows the super key as Mod
4. Is there a remote chance that ubiquity running with the mate settings
daemon etc sees super as mod4, even though mate uses gtk 2 and ubiquity
uses GTK 3?

I should note that this applies when booting directly into the
installer, not loading the desktop first and then running the installer.

Anyway, will debug further tomorrow.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to casper in Ubuntu.
https://bugs.launchpad.net/bugs/1546317

Title:
  Accessibility indicator is missing from ubiquity-dm at the "Try
  Ubuntu" dialog

Status in gnome-orca:
  Invalid
Status in ubuntu-mate:
  Confirmed
Status in a11y-profile-manager package in Ubuntu:
  In Progress
Status in casper package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  In Progress
Status in ubuntu-gnome-meta package in Ubuntu:
  In Progress
Status in ubuntu-mate-meta package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:
  1. Boot from a media containing the 15.10 32-bit image. Let it just boot, do not select anything.
  2. After the bongo drum sound, select your language and click "Try Ubuntu".
  3. After the desktop has been loaded, start Orca screen reader with the dedicated Alt+Super+s combination.
  Expected: the screen reader comes up talking
  Actual: the system remains silent.
  4. Try starting Orca from a terminal (Ctrl-Alt-t) and also from the Run dialog (Alt+F2).
  Results are the same as for point 3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-orca/+bug/1546317/+subscriptions



More information about the foundations-bugs mailing list