[u-a-dev] Hardy alpha4 problems with accessibility

Hammer Attila hammera at pickup.hu
Mon Feb 18 14:13:05 GMT 2008

	Dear developers!

I am not a perfect developer, but I like testing linux distributions.
I am a hungarian blind people, I am using linux operating system since 
2000 ago, and using Orca screen reader application synce 2007 summer.

I would like help testing this distribution with accessibility purposes.
   I vould like testing Ubuntu hardyheron alpha4 release in saturday.
The live cd booted, selected accessibility mode (screen reader when f5
key pressed).
started orca, and setup my preferences.
If I launched any administration applications or the ubiquity installer, 
there applications is inaccessible (sayd orca).
Few weeks ago, I generated my Ubuntu 7.10 live cd this steps, because 
the normal accessible install of Ubuntu 7.10 is very complicated my 
blind frend, and my frend not used linux newer:
  Decompressing the casper/filesystem.squashfs file with the target 
put the target directory/root folder the .orbitrc file this lines:
Regenerated the new casper/filesystem.squashfs file, generating the iso 
file, burned the cd.
The installation is work perfectly when accessible mode is selected (f5, 
If started orca with alt+f2 key (not start Orca if accessible mode is 
selected automaticaly), the normal desktop install icon is speech correctly.
After this, not need normal installation step if accessible install 
except launc orca alt+f2 and setup, writed the orca homepage e.g. ubuntu 
feisty installation:
1. Start the gnome-terminal.
2. type sudo su.
3. quit orca.
4. start orca with orca --no-setup --disable main-window &
5. ubiquity.
If the new installed system, put the /root/.orbitrc file, the system 
administration is work perfectly.

My frend using and like linux since tried my live cd.
In hardyheron alpha4, this solution is not work (generated new live cd 
with .orbitrc file /root folder).
Another installation steps (e.g. feyst installation writed orca
homepage) not work my computer.

I generated new live cd, enabled the root login with gdm with
gdm.conf-custom (added root password ubuntu), enabled the accessibility
support with root.
If i logged root, every administration applications work perfectly, and
speech the ubiquity installation.
But this is not good idea.

Hav any people with install Hardyheron alpha4 with accessible with Orca?

Tried monday, install hardy alpha4 my prepared live cd, the 
administration applications not speech with normal user.

It's very interesting, why not work the .orbitrc file the new system.
Not problem the new Policy kit feature?
Copying the short description this feature:

With Alpha 4, PolicyKit integration is visible in the administrative
user interfaces. PolicyKit makes it possible to run administrative
applications as
a normal user, and have them get a particular set of extra privileges
for certain operations, which allows fine-grained control over user
permissions and
enhances usability, as well as eliminating the security implications of
running the whole application as root. "

And this is the letter of ubuntu devel list archive:
"Hi all,

in Hardy we now use PolicyKit instead of gksu/sudo for authenticating
various sysadmin tasks, such as the GNOME system tools (users-admin,
network-admin), and mounting internal hard drives. The move to PK has
been described and justified in the spec [1].

The remaining unimplemented point is the "Migration" section of this
spec, which basically revolves around the question "What is the
definition of an admin?" Should it be "Everyone who is in the admin
group" or "Everyone who can execute arbitrary commands through sudo"?

The former case is implemented in PK right now. Implementing the
latter is very hard, since sudo does not easily give away any
information about who can do what, for good reasons.

Do you think that defining the group as authoritative is reasonable?

If not, then we need to engineer a pretty PK specific solution into
sudo itself, such as an option to "give me a list of all users who can
run arbitrary commands as root", which can only be called as user
"polkituser" (or root). Parsing /etc/sudoers is out of the question,
since it can get arbitrarily nested and complicated. Once we have
that, PK needs to get another authentication method, but that's
relatively easy then."
I would like help testing solutions, anybody thinks. I am translating 
hungarian language of Orca, my purpose:
I would like the hungarian average blind user (who is using windows this 
time) install Ubuntu linux easyest, e.g. my blind frend my 7.10 live cd.

Have you any idea this unaccessible problem?
Or have policy kit good preferences with system administration 
accessible with orca?
I am asking Ubuntu accessibility list my problem, but not find ansvers 
my questions.

What can I help with your work?


More information about the Ubuntu-accessibility-devel mailing list