onboard fails to start with F5 boot

[Henrik Nilsen Omma]

It turns out that the gnome AT startup functionality fails if AT-SPI is not enables, so the gconf value:

/desktop/gnome/accessibility/startup/exec_ats [onboard]

fails unless you also have:

/desktop/gnome/interface/accessibility true

I'm attaching a patch that fixes this.

[Henrik Nilsen Omma (henrik)]

Adds the line

 gct -s -t bool /desktop/gnome/interface/accessibility true

AT-SPI is not strictly needed for onboard, but IMO this is the simplest fix for now. We should work out something more general with gnome upstream.

[Tollef Fog Heen (tfheen)]

Fixed with Henrik's patch.

[Henrik Nilsen Omma (henrik)]

onBoard still does not start on the Live CD.

The line
gct -s -t list --list-type=string /desktop/gnome/accessibility/startup/exec_ats gok

must be changed to
gct -s -t list --list-type=string /desktop/gnome/accessibility/startup/exec_ats [onboard]

in the script 30accessibility

[Colin Watson (cjwatson)]

casper (1.76) edgy; urgency=low

  [ Colin Watson ]
  * Copy access=m2 accessibility changes into the corresponding ubiquity
    hook.
  * Remove spurious quoting from accessibility script.
  * Clear console-setup/layoutcode and console-setup/variantcode if they
    aren't supplied on the command line.

  [ Michael Vogt ]
  * scripts/casper-bottom/35fix_language_selector:
    - run fontconfig-voodoo if available to make sure that we have
      optimal fontconfig settings for the CJK languages (lp: #49334)

  [ Henrik Nilsen Omma ]
  * Fix a few accessibility items that were out of date, changing
    gnopernicus -> orca and gok -> onboard (the gok entry was missing some
    brackets as well; patch from Malone #58836, closes: Malone #65861).

 -- Colin Watson <email address hidden> Mon, 16 Oct 2006 20:20:15 +0100