Comment 20 for bug 551515

Revision history for this message
Attila Hammer (hammera) wrote : Re: [Bug 551515] Re: [Lucid] need little modify the ubiquity-hooks/30accessibility script with gdm accessibility setting configuration part in Blindness profile

Luke, thank you apply my patch.
But now this final applyed patch not containing some importanter
modifications with fixing some Ubuntu-accessibility list described users
wroted problems and important fix with basic accessibility if v3 mode is
selected with official 10.04 Ubuntu release:
See my comment detailed:
Following code part fixing Jose wroted problem during installation. Jose
see an accessibility login/speech-dispatcher related problem. When he
associate with Ctrl+Alt+Backspace key combination with kill X Server and
use this key combination to logout, and logging again with installed
system, Orca is not talking when he logged in because Speech-dispatcher
is not restarted, he need manual kill speech-dispatcher process.
My following code fixing this problem with insert killall
speech-dispatcher to .bash_logout file in first created new user home
directory in target system, and insert this command in target system
/etc/gdm/PostSession/Default file:
echo killall speech-dispatcher >>/target/home/$TARGET_USERNAME/.bash_logout
echo "#!/bin/sh" >/target/etc/gdm/PostSession/Default
echo killall speech-dispatcher >>/target/etc/gdm/PostSession/Default
echo "exit 0" >>/target/etc/gdm/PostSession/Default
Need put this modifyed .bash_logout file to target system/etc/skel folder.
This fix resulting absolute stable work when Ctrl+Alt+Backspace is used
and Pulseaudio running default with /user session. Now, I think Ubuntu
default running Pulseaudio with /user session.

Another now missing part is synchronise with first created user
important accessibility settings from target system user home directory
to target system/etc/skel folder.
This is need I think if access=v3 option is used, because if the first
created admin user creating another users, now the new created users not
get any accessibility support if after logged in, need configuring
manual the accessibility support.
Of course, I absolute understand if not want you apply following simple
line my patch with doing this task now, possible I choose drastical but
simple way:
                          rsync -r /target/home/$TARGET_USERNAME/
/target/etc/skel/

You have another suggestion how can synchronise in target system during
the installation with first created user important accessibility related
settings and prowide basic enabled accessibility settings if the
access=v3 option is used? We copying important configuration directoryes
after one by one with Cp commands?
I welcome do any fix, but I think this is a need feature (now missing
this) with normal Ubuntu releases and future helps the integration with
visual impaired people if not want use specialized distributions.

Attila