orca should automatically get started when braille is activated

Bug #122024 reported by Samuel thibault on 2007-06-24
6
Affects Status Importance Assigned to Milestone
casper (Ubuntu)
Medium
Unassigned

Bug Description

When booting e.g. the 7.10 tribe1 CD, whatever the way braille gets
activated (boot menu, "brltty=" trick or USB auto-detection), orca
should automatically get started. For instance, you can try on a
box that has a serial port:

- boot the liveCD
- press F5 (accessibility)
- choose Braille Terminal
- really boot the CD
When it prompts for the braille device configuration,
- answer s to the kind of connection (serial)
- answer 0 to the number of the serial port
- answer vs to the device type
- then it starts the gnome desktop

On the serial port, you'll notice this: >CREEN NOT IN TEXT MODE. That
means that brltty is correctly started, but that orca wasn't started
and hence a blind user can't read the gnome desktop.

Other ways to start braille that should be supported are as follows:

- plug a USB braille device
- just let boot the liveCD without typing anything at boot menu
- udev detects the USB braille device and starts brltty

- boot the liveCD
- press F6
- type brltty=vs,ttyS0
- really boot the CD
- brltty automatically gets started

Luke Yelavich (themuso) wrote :

This is partially fixed in my casper accessibility tree. When selecting braile from the boot menu, and choosing configuration options, Orca should now start when the GNOME desktop loads.

Loading orca when a USB device is somewhat less trivial, and I will need to talk to some core devs about this, which will have to wait till after tribe 2 is released.

http://bazaar.launchpad.net/~themuso/casper/a11y

Changed in casper:
importance: Undecided → Medium
status: New → In Progress
Luke Yelavich (themuso) wrote :

That should be, starting Orca when a USB Braille device is connected is somewhat less trivial.

Mmm, maybe it could be implemented as "if brltty is alive, start orca"? That should handle all three cases: boot braille optiont, brltty= kernel command line, and USB-triggered.

Luke Yelavich (themuso) wrote :

Don't forget that there is the issue that the GNOME accessibility framework has to be enabled for the user session, requiring a logout and log back in. At least with what I have done re the boot menu, and activating Orca, all that stuff gets set in gconf before the desktop is loaded.

I don't see how we could do it any other way, unless accessibility was enabled by default.

Mmm, but brltty is started _before_ X is started. Can't the automatic decision to enable accessibility be performed the gnome session gets started?

Luke Yelavich (themuso) wrote :

Ok, I'm with you.

I think the best way to handle this would be for the BrlTTY init script
to test whether its being booted in the live environment, and if so, set
up Orca. The only difficulty that we may have, is detecting the username
of the user that the live system creates.

Once tribe 2 is released, I'll talk to the devs about the best way to
implement this.

Changed in casper:
assignee: nobody → themuso
Colin Watson (cjwatson) wrote :

Luke, I've merged your partial fix into mainline; thanks.

Brian Murray (brian-murray) wrote :

Luke - is this still being worked on?

tags: added: a11y
Stéphane Graber (stgraber) wrote :

Well, Precise has been released a while ago now ;) what's the status of this bug Luke?

Luke Yelavich (themuso) on 2012-10-02
Changed in casper (Ubuntu):
assignee: Luke Yelavich (themuso) → nobody
status: In Progress → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers