Re: Accessible Login in 12.04?

2012-03-16 Thread Hammer Attila

Hy Luke,

CTRL+S works correct, thank you the answer.
I have got some question and experiences, sorri if my questions is 
trivial, but I now using first LightDM with accessible login feature.
1. How can possible choosing different user? If I press arrow keys, 
usual hear give my username password, or hear a button. Or this function 
is not full accessible yet?
Need enabling a GDM style user list in LightDm configuration? Possible 
doing this?
Oldest time in GDM login screen all awailable users present default a 
list, with possible choose required user to log in. If pressed ENTER key 
the selected user, possible write password, and switch session.


2. If I try using flat review in the Unity greeter, I think Orca is 
freezing. I unable to debug Orca level this situation yet. Possible 
changing local Orca execution command to generate Orca a debug.out file, 
or this is already known issue?


3. If I activate indicator menu in Unity greeter with F10 key, choosing 
some menu items and press ESCAPE key, the menue is doesn't leave, or 
Orca not refresh the screen content. My braille display this is absolute 
presenting.


4. What the difference with Unity Greeter and LightDm gtk greeter? 
LightDm Gtk greeter is possible using, this greeter more accessible?


Attila

--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility


Re: Accessible Login in 12.04?

2012-03-15 Thread Hammer Attila

Hy,

I see happened an upgrade with Casper package, to migrate LightDm a11y 
settings with GSettings, because Unity Greeter using GSettings.


When I try use an installed system in terminal the sudo -u lightdm 
gsettings set com.canonical.unity-greeter screen-reader false command, I 
get following error:
hammera@hammera-Satellite-L300:~$ sudo -u lightdm gsettings set 
com.canonical.unity-greeter screen-reader false


** WARNING **: Command line `dbus-launch 
--autolaunch=57457bea3de3d18c6e5b5034000d --binary-syntax 
--close-stderr' exited with non-zero exit status 1: No protocol 
specified\nNo protocol specified\nAutolaunch error: X11 initialization 
failed.\n


** WARNING **: Command line `dbus-launch 
--autolaunch=57457bea3de3d18c6e5b5034000d --binary-syntax 
--close-stderr' exited with non-zero exit status 1: No protocol 
specified\nNo protocol specified\nAutolaunch error: X11 initialization 
failed.\n

hammera@hammera-Satellite-L300:~$

Look what the result if I run sudo -u lightdm gsettings get 
com.canonical.unity-greeter screen-reader command:
hammera@hammera-Satellite-L300:~$ sudo -u lightdm gsettings get 
com.canonical.unity-greeter screen-reader

false

During installation this GSettings key with LightDm are setting properly?
How can possible enable an installed Ubuntu 12.04 system the screen 
reader support in login screen if this error is present? Temporary need 
sighted assistance?
Alan, when you tested the accessible login with screen reader when you 
reported the proper bug, how can enabled this function?


Attila

--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility


Re: Accessible Login in 12.04?

2012-03-15 Thread Luke Yelavich
On Thu, Mar 15, 2012 at 08:16:01PM EST, Hammer Attila wrote:
 Hy,
 
 I see happened an upgrade with Casper package, to migrate LightDm
 a11y settings with GSettings, because Unity Greeter using GSettings.
 
 When I try use an installed system in terminal the sudo -u lightdm
 gsettings set com.canonical.unity-greeter screen-reader false
 command, I get following error:
 hammera@hammera-Satellite-L300:~$ sudo -u lightdm gsettings set
 com.canonical.unity-greeter screen-reader false
 
 ** WARNING **: Command line `dbus-launch
 --autolaunch=57457bea3de3d18c6e5b5034000d --binary-syntax
 --close-stderr' exited with non-zero exit status 1: No protocol
 specified\nNo protocol specified\nAutolaunch error: X11
 initialization failed.\n
 
 ** WARNING **: Command line `dbus-launch
 --autolaunch=57457bea3de3d18c6e5b5034000d --binary-syntax
 --close-stderr' exited with non-zero exit status 1: No protocol
 specified\nNo protocol specified\nAutolaunch error: X11
 initialization failed.\n
 hammera@hammera-Satellite-L300:~$

The reason why that doesn't work is due to the way gsettings works. Gsettings 
supports multiple backend data storage formats, one of which is dconf. Dconf is 
the default data storage format, which is a database stored at the system/user 
level. When gsettings wants to use dconf, it communicates via dbus to a dconf 
service process that runs as the user. This dconf service process makes the 
requested changes. So the above doesn't work, because there is no dconf service 
running as the lightdm user when you are logged into the system as another user.

 Look what the result if I run sudo -u lightdm gsettings get
 com.canonical.unity-greeter screen-reader command:
 hammera@hammera-Satellite-L300:~$ sudo -u lightdm gsettings get
 com.canonical.unity-greeter screen-reader
 false

I have seen this myself. I suspect either there is some caching going on 
somewhere, or the gsettings dconf backend can read the database itself, but 
cannot write.

 During installation this GSettings key with LightDm are setting properly?

Yes, when the screen reader profile is enabled, this key now gets set. That was 
one of the changes in the updated casper package.

 How can possible enable an installed Ubuntu 12.04 system the screen
 reader support in login screen if this error is present? Temporary
 need sighted assistance?

Control + S should work in the unity-greeter, however there are some weird 
focus issues when unity-greeter first loads, which for some reason prevent 
control + S from working. If you tab to the session selection box, and 
shift-tab back to the password prompt or login button, and then press Control + 
S, Orca should load. When you press Control + S, the screen reader will be 
active for every subsequent use of unity-greeter, until its turned off again.

Luke

-- 
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility


Accessible Login in 12.04?

2012-03-04 Thread Dave Hunt

Hi,

Does the 12.04 Beta 1 have an accessible login greeter?  When last I 
used 11.10, lightdm was not accessible with orca.



Cheers,


Dave_H



--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility


Re: Accessible Login in 12.04?

2012-03-04 Thread Christopher Chaltain
I haven't brought up 12.04 in a little bit, but the last time I tried
Alpha 2, lightdm still wasn't accessible. I haven't taken a look at Beta
1 yet. BTW, because of this, I mostly just use auto log on now, although
I know that doesn't answer your question.

On 04/03/12 17:52, Dave Hunt wrote:
 Hi,
 
 Does the 12.04 Beta 1 have an accessible login greeter?  When last I
 used 11.10, lightdm was not accessible with orca.
 
 
 Cheers,
 
 
 Dave_H

-- 
Christopher (CJ)
chalt...@gmail.com

-- 
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility


Re: Accessible Login in 12.04?

2012-03-04 Thread José Vilmar Estácio de Souza

Hi.
I installed beta 1 yesterday and orca doesn't speak in the login.

On 03/04/2012 09:48 PM, Christopher Chaltain wrote:

I haven't brought up 12.04 in a little bit, but the last time I tried
Alpha 2, lightdm still wasn't accessible. I haven't taken a look at Beta
1 yet. BTW, because of this, I mostly just use auto log on now, although
I know that doesn't answer your question.

On 04/03/12 17:52, Dave Hunt wrote:

Hi,

Does the 12.04 Beta 1 have an accessible login greeter?  When last I
used 11.10, lightdm was not accessible with orca.


Cheers,


Dave_H




--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility