[ubuntu/trusty-proposed] casper 1.338 (Accepted)

[Luke Yelavich]

casper (1.338) trusty; urgency=medium

  * scripts/casper-bottom/30accessibility: If the user boots to the desktop,
    write a desktop file to /etc/xdg/autostart to set up the screen reader
    profile if the user launches Orca with a shortcut key. Gnome/Unity
    settings daemon takes priority over ubiquity with keygrabs, such
    that the profile setting code in ubiquity does not get executed when
    the shortcut is entered. Temporarily disabling the shortcut key also
    doesn't work, as Gnome/Unity settings daemon doesn't appear to notice
    the change when the gsettings key is changed on the command-line. As
    such, this is a cludge, until a better mechanism for handling
    accessibility profiles is implemented.

Date: Mon, 10 Mar 2014 14:59:02 +1100
Changed-By: Luke Yelavich <themuso at ubuntu.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://launchpad.net/ubuntu/trusty/+source/casper/1.338
-------------- next part --------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Mon, 10 Mar 2014 14:59:02 +1100
Source: casper
Binary: casper ubiquity-casper
Architecture: source
Version: 1.338
Distribution: trusty
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Luke Yelavich <themuso at ubuntu.com>
Description: 
 casper     - Run a "live" preinstalled system from read-only media
 ubiquity-casper - Configuration hooks for live installer
Changes: 
 casper (1.338) trusty; urgency=medium
 .
   * scripts/casper-bottom/30accessibility: If the user boots to the desktop,
     write a desktop file to /etc/xdg/autostart to set up the screen reader
     profile if the user launches Orca with a shortcut key. Gnome/Unity
     settings daemon takes priority over ubiquity with keygrabs, such
     that the profile setting code in ubiquity does not get executed when
     the shortcut is entered. Temporarily disabling the shortcut key also
     doesn't work, as Gnome/Unity settings daemon doesn't appear to notice
     the change when the gsettings key is changed on the command-line. As
     such, this is a cludge, until a better mechanism for handling
     accessibility profiles is implemented.
Checksums-Sha1: 
 d8b2a8d73296d3cf259075b04a245cc454206935 922 casper_1.338.dsc
 b0b29e592ef32b697abddf846b0d2b105a7dcdbd 103099 casper_1.338.tar.gz
Checksums-Sha256: 
 4ba748a6b9d2852837a876240465a4aa3f10f3f7a983960c400eea2cb3c627db 922 casper_1.338.dsc
 7e7496cbd1e80a6b3298a4d6b3a82c206f7d784b250a0cec2e89cf3997cc358e 103099 casper_1.338.tar.gz
Files: 
 86c1e9cb768db75b0106f35394c4851b 922 misc optional casper_1.338.dsc
 61fd6f715718d7ee819d8872ec86f76e 103099 misc optional casper_1.338.tar.gz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlMdONYACgkQjVefwtBjIM4RGACbBbCkDMZ75JWNsTo0iEEesFPy
91IAoL1Zo09nSz2jlx8UGPZxDS8RuH+k
=Jmog
-----END PGP SIGNATURE-----