Ultimate plans for the sudo fix .orbitrc?

[Al Puzzuoli]

Hi Lukas,
Although the installer is one area where this issue is still a barrier to 
equal access, it is only one of many.  For example, consider a typical user 
who has just installed Ubuntu on their laptop.  One of the first things that 
user might want to do would be to configure wireless connectivity.  However, 
if said user relied on a screen reader, it would be impossible to access the 
network management utilities via the gui until the .orbitrc issue were 
resolved.  If we take this one step further, before our user could even 
begin to fix the .orbitrc, he or she would need to be aware that the issue 
existed in the first place.

Is there any way this process could be automated so that it were transparent 
to the user?  Perhaps the presence of these lines in /root/.orbitrc could be 
tied to the activation of the accessibility flag or something?

--Al


----- Original Message ----- 
From: "Lukas Loehrer" <listaddr1 at gmx.net>
To: "Ubuntu Accessibility Mailing List" 
<ubuntu-accessibility at lists.ubuntu.com>
Sent: Sunday, February 04, 2007 2:56 AM
Subject: Re: Ultimate plans for the sudo fix .orbitrc?


> Al Puzzuoli writes ("Ultimate plans for the sudo fix .orbitrc?"):
>> Just wondering how the Ubuntu team ultimately plans to handle the sudo 
>> accessibility stuff for the release of Feisty?   The fix to the Gnome 
>> components themselves is pretty much finished; but, there's still the 
>> issue of a couple esoteric settings that need to be added to the .orbitrc 
>> file of the root account's home directory in order for that fix to be 
>> relevant.
>> Granted, the task of jumping into gnome-terminal and hand creating the 
>> needed .orbitrc is quite painless for even moderately experienced users 
>> of Linux; However, if for a few moments, we look at this from the 
>> perspective of a newbie coming from windows, who has never even seen a 
>> dos prompt, and just wants to install ubuntu, or perhaps tweak some 
>> network settings on an already installed system... Well, you only get one 
>> chance to make a first impression.
>
> Maybe, it would be easier altogether to have a text based alternative 
> frontend
> for ubiquity on the live CD, that would simply ask a few questions, maybe 
> with
> completion wia readline for things like city and language. I do not
> mean a curses application but more like something "orca -t" does. I
> looked at the ubiquity source code and it seems one would simply have
> to implement a "Frontend" class that implements some interfaces,
> though I am not 100 % sure which ones are required for a minimal
> frontend. Things like partitioning would have to be done manually before
> starting ubiquity with this frontend, so it could be really simple.
>
> Best regards, Lukas
>
>
> -- 
> Ubuntu-accessibility mailing list
> Ubuntu-accessibility at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility