Public bug reported:
Binary package hint: casper
Dear Developers,
In Lucid, some blind users lot of time wroted following problem in
Ubuntu-Accessibility list:
When GDM is upgraded an installed system, ubiquity-casper 30accessibility
script preconfigured GDM accessible login settings during installation is
restored with default value. This is resulting problems with next restart,
because blind users impossible use accessible GDM login feature before not
setting manual all important GDM related gconf settings and restart the system.
The problem related with following:
Now, in blindness profile, gct_gdm using following method to configure GDM
accessible login feature:
gct_gdm() {
chroot /target sudo -u gdm gconftool-2 "$@"
gct_gdm -s -t bool
/desktop/gnome/interface/accessibility true
gct_gdm -s -t bool
/desktop/gnome/applications/at/visual/startup true
gct_gdm -s -t string
/desktop/gnome/applications/at/visual/exec orca
gct_gdm -s -t bool
/desktop/gnome/applications/at/screen_reader_enabled true
So, the ubiquity-hooks/30accessibility script set this feature related settings
with gdm user, not using system default setting method.
For example, Bill Cox Vinux Developer in Ubuntu Accessibility List suggest
following change:
"All of the 30-accessibility commands apply to gdm's local copy of
settings, not default system-wide settings. I would recommend that
they be changed to system wide. I already do that in Vinux.
I prefer to set this option as a global default value. That, when
users update their system and gdm is upgraded, they still have a
talking login. The command I use is:
gconftool-2 --direct --config-source
xml:readwrite:/etc/gconf/gconf.xml.defaults -s -t bool
/desktop/gnome/applications/at/screen_reader_enabled true
That should fix the problem long-term."
I make a change with ubiquity-hooks/30accessibility script with important
places, and setting all GDM related accessibility settings with system vide
settings in blindness profile.
Before I write this bugreport, I make my testing purpose a custom actual Lucid
live CD, with containing new patched ubiquity-casper package.
I do clean installation, and after this, I do a full apt-get dist-upgrade
command. I do this, because I known now happening this day a GDM upgrade, and
this is ideal situation for testing.
The good results is following:
My maked patched ubiquity-casper package is working absolute safe. When the
installation is finished, I restart the system. GDM is talking fine after
restart. I using blindness profile with screen reader support during
installation.
After I logged in first, I do full apt-get dist-upgrade and restart my system.
After restart is happened and GDM is present my display, accessible login
feature working absolute right, Orca is wonderful talking after GDM upgrade.
Please apply my patch if this is possible, because this patch resulting
longer time safe working accessible login feature with visual impaired
users if using Orca Screen Reader. This change not disturb non visual
imparied users, this change do 30accessibility script during
installation if accessible mode is v3.
Attila
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: casper 1.229
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic i686
Architecture: i386
Date: Tue Mar 30 10:27:31 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100129)
ProcEnviron:
LANGUAGE=hu_HU.UTF-8
LANG=hu_HU.UTF-8
SHELL=/bin/bash
SourcePackage: casper
** Affects: casper (Ubuntu)
Importance: Undecided
Status: New
** Tags: accessibility apport-bug i386 lucid
--
[Lucid] need little modify the ubiquity-hooks/30accessibility script with gdm
accessibility setting configuration part in Blindness profile
https://bugs.launchpad.net/bugs/551515
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
