Public bug reported:
Binary package hint: casper
Dear Developers,
In Lucid or next developing cicle, my openion need default enable the
accessibility support in installed system with all future created users,
if the installation is happened for example with screen reader mode
(access=v3 parameter use with boot).
Now, following think is happening after installation if visual impaired
user installing the system with screen reader support:
In Lucid, wonderful have accessible GDM screen, the first created user
have wonderful accessibility support. But, if the first admin right user
creating a new user, new user does'nt get accessibility support,
accessibility support related settings is default disabled. If a blind
user would like using the system, need hand enabling following g-conf
settings in terminal without any screen reader support, gct now means
gconftool-2 command:
gct -s -t bool /desktop/gnome/interface/accessibility
true
gct -s -t bool /apps/gksu/disable-grab true
gct -s -t string
/desktop/gnome/applications/window_manager/default /usr/bin/metacity
gct -s -t bool
/desktop/gnome/applications/at/visual/startup true
gct -s -t string
/desktop/gnome/applications/at/visual/exec orca
gct -s -t string /apps/empathy/conversation/theme
classic
This copyed code part is present in casper source 30accessibility script
in blindness profile.
Of course, first admin right user possible do this
commands when logging in with new user account in terminal, but very
need this if a screen reader choosed installation is happened?
How can possible fix this problem if you want?
1. Possible not elegant, but during installation after happened
accessibility setting configuration with first created user in target
system, need copying important configuration folders in target system
created first user home directory to target system /etc/skel folder. But, this
step I think is resulting more redundant cp lines.
2. A more useful, simple, tested fix method:
Need using system default configurations, not user based configurations
when installer configuring with accessibility related settings, for
example following command replace the old user based
/desktop/gnome/interface/accessibility configuration:
Original command is following:
gconftool-2 -s -t bool /desktop/gnome/interface/accessibility true
This command enable accessibility mode only with actual user.
Replaced command is following:
gconftool-2 --direct --config-source
xml:readwrite:/etc/gconf/gconf.xml.defaults -s -t bool
/desktop/gnome/interface/accessibility true
This command enables systemwide default the GNOME accessibility setting.
I now tryed the second fix way with patched old gct function in
ubiquity-hooks/30accessibility script in casper source package, and do a clean
installation. The second suggested fix way work wonderful, next comment I
writing the test results, and sending the patch.
Attila
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: casper (not installed)
ProcVersionSignature: Ubuntu 2.6.32-21.31-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Thu Apr 15 12:33:27 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100412)
ProcEnviron:
LANG=hu_HU.utf8
SHELL=/bin/bash
SourcePackage: casper
** Affects: casper (Ubuntu)
Importance: Undecided
Status: New
** Tags: accessibility apport-bug i386 lucid
--
[Lucid or Maverick] When Ubuntu installation is happening with accessibility
mode, need default enabled the accessibility support with future created users
in installed system
https://bugs.launchpad.net/bugs/563717
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
