GDM 2.28 a11y issues

[Willie Walker]

Hi All:

I've not had much of a chance to experiment with the new GDM 2.28 until
recently.  Here is a summary my experiments with GDM 2.28 from over the
weekend on my OpenSolaris b125 box.  It's a semi-exhaustive list, but I
don't guarantee I didn't miss anything.

The "+" items are good things.  The "-" entries are bad things.  I sent
this feedback to Brian Cameron just this morning, but it seems as though
I should also share it with the gdm team and then transform it into bugs
in bugzilla once we've determined things aren't pilot error on my part.

+ Keyboard navigation works.

+ The high contrast selection works.

+ The larger font selection works.

- A metacity error dialog appears when I log in.  The dialog contains a
table.  The title of the table is 'These windows do no support "save
current setup" and will have to be restarted manually next time you log
in.'   The table consists of two columns. The first column is 'Class'
and the second column is 'Window'.  The sole entry in the table is
'Login Window'/'Gdm-simple-greeter'.

- The a11y icon should be in a corner of the screen to allow for more
easy mouse access.  Right now, it's tucked somewhere in the middle of
the panel.

- The a11y icon should allow a 'hover' operation similar to the icon
used to enable MouseTweaks in the MouseTweaks applet.  When the icon is
activated via a hover operation, MouseTweaks should be enabled in 'hover
mode' and the a11y dialog should open.

- There are no keyboard shortcuts or mouse gestures to launch the a11y
dialog.  Instead, need to Ctrl+Alt+Tab to panel and navigate to the icon
and activate it.

- There are no shortcuts to launch any assistive technology.  We
probably need a community discussion about these if the same gestures
are to be available at the login screen and the user session.

- The magnifier launches the 'magnifier' application instead of Orca
(Orca's magnification is preferred because it follows keyboard focus).
The magnifier also comes up in split screen mode instead of full screen
mode.

- The gdm screen is launched without accessibility enabled.  As a
result, GTK+ does not appear to load the a11y modules and the
at-spi-registryd is not launched.  This yields the login screen
inaccessible.  a11y probably should be enabled by default for the gdm
screen, and this would hopefully fix the issues.

- SlowKeys and BounceKeys features don't seem to work, but StickyKeys does.

- When any of the AccessX keys are enabled, the "Keyboard Accessibility
Status" applet should appear in the panel (it currently does not).  This
applet provides the user with AccessX feedback, such as which modifiers
are latched/locked.

- Ctrl+Alt+Backspace doesn't seem to work any more (maybe an X Server
configuration issue?).

- Entering Ctrl, Alt, Tab in sequence when StickyKeys is enabled doesn't
seem to permit the selection of the bottom panel.  It should.

- The GOK keyboard does not reflect the physical keyboard layout (it
probably should -- if not possible, it probably should reflect a
PC-101/PC-102/etc. layout).  Instead, it's a minimal A-Z keyboard.  This
simplified keyboard does not include an "Alt" key.

- No audio cues seem to be given.  We should have a login screen sound
enabled by default.  This might be an audio permissions or configuration
problem on my machine.

- Speech doesn't work.  It seems to launch, but no output is sent to the
speakers.  Running 'test-speech' as the gdm user from a shell logged in
via a different machine also seems to result in no speech.  Note that
the speech synthesis process runs, so this might be an audio permissions
or configuration issue.

- It would be nice if we could agree on a single a11y icon.  I prefer
some form of the vitruvian man -
http://live.gnome.org/Accessibility?action=AttachFile&do=get&target=logo.png

Thanks!

Will
_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[Matthias Clasen-2]

On Mon, Oct 19, 2009 at 4:30 PM, Willie Walker

>
> - A metacity error dialog appears when I log in.  The dialog contains a
> table.  The title of the table is 'These windows do no support "save current
> setup" and will have to be restarted manually next time you log in.'   The
> table consists of two columns. The first column is 'Class' and the second
> column is 'Window'.  The sole entry in the table is 'Login
> Window'/'Gdm-simple-greeter'.

Curious, this was supposed to be fixed with
https://bugzilla.gnome.org/show_bug.cgi?id=580189


> - There are no shortcuts to launch any assistive technology.  We probably
> need a community discussion about these if the same gestures are to be
> available at the login screen and the user session.

We do have the framework in place for these now. If you open the
keybinding capplet, there is a section for 'Accessibility' shortcuts,
with
'Toggle magnifier', 'Toggle screen reader' and 'Toggle on-screen keyboard'.
We just need to set suitable values for these and enable them in the
gdm session. We also added a mechanism to lock down the keybinding
gconf keys so that we can safely turn this on in the login session
without opening up security holes.

> - The gdm screen is launched without accessibility enabled.  As a result,
> GTK+ does not appear to load the a11y modules and the at-spi-registryd is
> not launched.  This yields the login screen inaccessible.  a11y probably
> should be enabled by default for the gdm screen, and this would hopefully
> fix the issues.

This is should be just a matter of setting
/desktop/gnome/interface/accessibility in the gdm session.


> - Ctrl+Alt+Backspace doesn't seem to work any more (maybe an X Server
> configuration issue?).

This got converted from a server configuration thing to a regular xkb action.

> - The GOK keyboard does not reflect the physical keyboard layout (it
> probably should -- if not possible, it probably should reflect a
> PC-101/PC-102/etc. layout).  Instead, it's a minimal A-Z keyboard.  This
> simplified keyboard does not include an "Alt" key.

Seems that maybe we just need a different onscreen keyboard than gok ?
Our on-screen keyboard story is not particularly clear to me. In
Fedora, our input-method guys wrote their own, which looks a lot more
like a real keyboard (but has other issues).


Thanks for looking into this !

Matthias
_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[Brian Cameron]

Willie:

> I've not had much of a chance to experiment with the new GDM 2.28 until
> recently.  Here is a summary my experiments with GDM 2.28 from over the
> weekend on my OpenSolaris b125 box.  It's a semi-exhaustive list, but I
> don't guarantee I didn't miss anything.

Thanks for checking this.  Some comments below.

> - A metacity error dialog appears when I log in.  The dialog contains a
> table.  The title of the table is 'These windows do no support "save
> current setup" and will have to be restarted manually next time you log
> in.'   The table consists of two columns. The first column is 'Class'
> and the second column is 'Window'.  The sole entry in the table is
> 'Login Window'/'Gdm-simple-greeter'.

This is related to bugzilla bugs #587732 and #598235.  On Solaris, I
backed out the fix for bug #587732 on Solaris since losing focus in
the login GUI is a serious problem.

If you rebuild SUNWgnome-wm.spec on Solaris, then the problem should go
away.  It has been modified to remove the dialog until a better fix for
the above problems is found.

> - The a11y icon should be in a corner of the screen to allow for more
> easy mouse access.  Right now, it's tucked somewhere in the middle of
> the panel.

This sounds like something that we should file a bug about.

> - The a11y icon should allow a 'hover' operation similar to the icon
> used to enable MouseTweaks in the MouseTweaks applet.  When the icon is
> activated via a hover operation, MouseTweaks should be enabled in 'hover
> mode' and the a11y dialog should open.

We should have better hover support.  Is the right fix to make GDM just
work this way and respond to hover directly, or would it make more sense
to just integrate MouseTweaks so that it always runs with GDM?

> - There are no keyboard shortcuts or mouse gestures to launch the a11y
> dialog.  Instead, need to Ctrl+Alt+Tab to panel and navigate to the icon
> and activate it.

That does seem awkward.  There should be a nicer way to launch the
dialog via a keyboard shortcut, I think.  This sounds like something
that we should file a bug about.

> - There are no shortcuts to launch any assistive technology.  We
> probably need a community discussion about these if the same gestures
> are to be available at the login screen and the user session.

I think these issues would really best be fixed by addressing the
problems in gnome-control-center and gnome-settings-daemon so that
these sorts of features work in the user session as well as the GDM
login session.  See here:

   https://bugzilla.gnome.org/show_bug.cgi?id=531595
   https://bugzilla.gnome.org/show_bug.cgi?id=531596

> - The magnifier launches the 'magnifier' application instead of Orca
> (Orca's magnification is preferred because it follows keyboard focus).
> The magnifier also comes up in split screen mode instead of full screen
> mode.

This should just involve modifying the file
/usr/share/gdm/autostart/LoginWindow/gnome-mag.desktop to call the
appropriate program instead of calling "magnifier -v -m".  If you
want to propose a patch, I would think this would get accepted upstream
without much issue.

> - The gdm screen is launched without accessibility enabled.  As a
> result, GTK+ does not appear to load the a11y modules and the
> at-spi-registryd is not launched.  This yields the login screen
> inaccessible.  a11y probably should be enabled by default for the gdm
> screen, and this would hopefully fix the issues.

If you want to enable a11y in GDM by default, you just need to set the
GConf key to turn it on for the "gdm" user.  The same key that gets
set when you run Preferences->Assistive Technologies and click the
checkbox next to "Enable assistive technologies".

I am not sure if this sort of change makes sense to go upstream for all
distros, but it is the sort of change that would be easy to make on a
per-distro basis, I would think.

> - SlowKeys and BounceKeys features don't seem to work, but StickyKeys does.

Do they not work at all, or they just do not work via the a11y menu?
Don't these features support Xserver hotkeys to launch them?  Do the
hotkeys work?  Do they work once the user session starts?  In other
words, are they only broken at the GDM login screen?

Since GDM starts the normal user Xserver the same way that it starts the
Xserver used by GDM, it would be odd that it works in the user session,
but not in the GDM session.

> - When any of the AccessX keys are enabled, the "Keyboard Accessibility
> Status" applet should appear in the panel (it currently does not).  This
> applet provides the user with AccessX feedback, such as which modifiers
> are latched/locked.

That seems a reasonable enhancement request, and something that would be
good to file a bug about.

> - Ctrl+Alt+Backspace doesn't seem to work any more (maybe an X Server
> configuration issue?).

This is not really a GDM issue.  This is managed by the Xserver
configuration.

> - Entering Ctrl, Alt, Tab in sequence when StickyKeys is enabled doesn't
> seem to permit the selection of the bottom panel.  It should.

Again, this sounds like an Xserver issue.

> - The GOK keyboard does not reflect the physical keyboard layout (it
> probably should -- if not possible, it probably should reflect a
> PC-101/PC-102/etc. layout).  Instead, it's a minimal A-Z keyboard.  This
> simplified keyboard does not include an "Alt" key.

Is this an issue specific to launching GOK when GDM is running, or is
this a problem in the user session as well?

> - No audio cues seem to be given.  We should have a login screen sound
> enabled by default.  This might be an audio permissions or configuration
> problem on my machine.

I am not sure, but I do not think this feature was ever ported to the
new GDM.  If it has, you might be running into the audio permissions
issue I mention below.

> - Speech doesn't work.  It seems to launch, but no output is sent to the
> speakers.  Running 'test-speech' as the gdm user from a shell logged in
> via a different machine also seems to result in no speech.  Note that
> the speech synthesis process runs, so this might be an audio permissions
> or configuration issue.

If you are testing on Solaris, it might be a permissions issue.  The old
GDM used to call /usr/bin/setfacl to add the gdm user to the /dev/audio
and /dev/audioctl device permissions.  I wonder if that needs to be
ported to the new GDM also.

> - It would be nice if we could agree on a single a11y icon.  I prefer
> some form of the vitruvian man -
> http://live.gnome.org/Accessibility?action=AttachFile&do=get&target=logo.png 

That seems a reasonable request, so I think a bug should be filed.

Brian
_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[Willie Walker]

Thanks Brian and Mattias:

>> - A metacity error dialog appears when I log in.  The dialog contains
>> a table.  The title of the table is 'These windows do no support "save
>> current setup" and will have to be restarted manually next time you
>> log in.'   The table consists of two columns. The first column is
>> 'Class' and the second column is 'Window'.  The sole entry in the
>> table is 'Login Window'/'Gdm-simple-greeter'.
>
> This is related to bugzilla bugs #587732 and #598235.  On Solaris, I
> backed out the fix for bug #587732 on Solaris since losing focus in
> the login GUI is a serious problem.
>
> If you rebuild SUNWgnome-wm.spec on Solaris, then the problem should go
> away.  It has been modified to remove the dialog until a better fix for
> the above problems is found.

The rebuild/install of SUNWgnome-wm.spec fixed the problem.  Thanks!

>> - The a11y icon should be in a corner of the screen to allow for more
>> easy mouse access.  Right now, it's tucked somewhere in the middle of
>> the panel.
>
> This sounds like something that we should file a bug about.
>
>> - The a11y icon should allow a 'hover' operation similar to the icon
>> used to enable MouseTweaks in the MouseTweaks applet.  When the icon
>> is activated via a hover operation, MouseTweaks should be enabled in
>> 'hover mode' and the a11y dialog should open.
>
> We should have better hover support.  Is the right fix to make GDM just
> work this way and respond to hover directly, or would it make more sense
> to just integrate MouseTweaks so that it always runs with GDM?

Integrating MouseTweaks in the panel is a great idea, and I think that
would be a sufficient solution.  In addition, the MouseTweaks 'hover'
area is probably the thing that we'd want to put in the lower left
instead of the a11y icon.

I can open an RFE for this if this seems reasonable to everyone.

>> - There are no keyboard shortcuts or mouse gestures to launch the a11y
>> dialog.  Instead, need to Ctrl+Alt+Tab to panel and navigate to the
>> icon and activate it.
>
> That does seem awkward.  There should be a nicer way to launch the
> dialog via a keyboard shortcut, I think.  This sounds like something
> that we should file a bug about.

Thanks!  https://bugzilla.gnome.org/show_bug.cgi?id=599093

>> - There are no shortcuts to launch any assistive technology.  We
>> probably need a community discussion about these if the same gestures
>> are to be available at the login screen and the user session.
>
> I think these issues would really best be fixed by addressing the
> problems in gnome-control-center and gnome-settings-daemon so that
> these sorts of features work in the user session as well as the GDM
> login session.  See here:
>
>   https://bugzilla.gnome.org/show_bug.cgi?id=531595
>   https://bugzilla.gnome.org/show_bug.cgi?id=531596

Mattias also wrote "We do have the framework in place for these now. If
you open the keybinding capplet, there is a section for 'Accessibility'
shortcuts, with 'Toggle magnifier', 'Toggle screen reader' and 'Toggle
on-screen keyboard'.  We just need to set suitable values for these and
enable them in the gdm session."

Would these be for the gdm session only, or would they have to apply to
the gdm session and user session?  The reason I ask is that the
requirements and behavior of the assistive technology can be different
between the login screen and the user session.  For example, GOK has a
"login" mode, and we also will launch Orca a bit differently so it won't
interfere with the login screen (i.e., we want to launch Orca without a
main window on the login screen).

>> - The magnifier launches the 'magnifier' application instead of Orca
>> (Orca's magnification is preferred because it follows keyboard focus).
>> The magnifier also comes up in split screen mode instead of full
>> screen mode.
>
> This should just involve modifying the file
> /usr/share/gdm/autostart/LoginWindow/gnome-mag.desktop to call the
> appropriate program instead of calling "magnifier -v -m".  If you
> want to propose a patch, I would think this would get accepted upstream
> without much issue.

I'll take a look.  Modifying this to launch Orca with "--enable
magnifier" should be pretty simple to do.

>> - The gdm screen is launched without accessibility enabled.  As a
>> result, GTK+ does not appear to load the a11y modules and the
>> at-spi-registryd is not launched.  This yields the login screen
>> inaccessible.  a11y probably should be enabled by default for the gdm
>> screen, and this would hopefully fix the issues.
>
> If you want to enable a11y in GDM by default, you just need to set the
> GConf key to turn it on for the "gdm" user.  The same key that gets
> set when you run Preferences->Assistive Technologies and click the
> checkbox next to "Enable assistive technologies".

Does this mean the gdm user now has a specific gconf area for itself?
If so, where is the suggested place to set the default values for gdm
(vs. the normal user session)?

>> - SlowKeys and BounceKeys features don't seem to work, but StickyKeys
>> does.
>
> Do they not work at all, or they just do not work via the a11y menu?
> Don't these features support Xserver hotkeys to launch them?  Do the
> hotkeys work?  Do they work once the user session starts?  In other
> words, are they only broken at the GDM login screen?

They work once the user session starts, but not at the GDM login screen.
  I'm not sure, but I wonder if those dialogs that warn you about a
feature being turned on or off have a side effect?  These dialogs appear
on the user session, but not the gdm login screen.

>> - When any of the AccessX keys are enabled, the "Keyboard
>> Accessibility Status" applet should appear in the panel (it currently
>> does not).  This applet provides the user with AccessX feedback, such
>> as which modifiers are latched/locked.
>
> That seems a reasonable enhancement request, and something that would be
> good to file a bug about.

What if we just had the applet always installed (as we would do with
MouseTweaks)?

>> - Ctrl+Alt+Backspace doesn't seem to work any more (maybe an X Server
>> configuration issue?).
>
> This is not really a GDM issue.  This is managed by the Xserver
> configuration.

Mattias also wrote: "This got converted from a server configuration
thing to a regular xkb action."  Was that a change caused by something
actively done somewhere in GNOME or somewhere else (e.g., the X Server
folks made a modification in some X server revision)?

>> - Entering Ctrl, Alt, Tab in sequence when StickyKeys is enabled
>> doesn't seem to permit the selection of the bottom panel.  It should.
>
> Again, this sounds like an Xserver issue.

Odd.  It seems to work in the user session.

>> - The GOK keyboard does not reflect the physical keyboard layout (it
>> probably should -- if not possible, it probably should reflect a
>> PC-101/PC-102/etc. layout).  Instead, it's a minimal A-Z keyboard.  
>> This simplified keyboard does not include an "Alt" key.
>
> Is this an issue specific to launching GOK when GDM is running, or is
> this a problem in the user session as well?

This one does seem to be a general GOK/XKB interaction problem.  GOK
fails to pick up the keyboard layout for both the desktop and login screen.

>> - No audio cues seem to be given.  We should have a login screen sound
>> enabled by default.  This might be an audio permissions or
>> configuration problem on my machine.
>
> I am not sure, but I do not think this feature was ever ported to the
> new GDM.  If it has, you might be running into the audio permissions
> issue I mention below.
>
>> - Speech doesn't work.  It seems to launch, but no output is sent to
>> the speakers.  Running 'test-speech' as the gdm user from a shell
>> logged in via a different machine also seems to result in no speech.  
>> Note that the speech synthesis process runs, so this might be an audio
>> permissions or configuration issue.
>
> If you are testing on Solaris, it might be a permissions issue.  The old
> GDM used to call /usr/bin/setfacl to add the gdm user to the /dev/audio
> and /dev/audioctl device permissions.  I wonder if that needs to be
> ported to the new GDM also.

Yep - most likely a permissions issue:

wwalker@osol:~$ ls -lL /dev/audio*
crw------- 1 wwalker staff 238, 3 2009-10-16 09:06 /dev/audio
crw------- 1 wwalker staff 238, 4 2009-10-16 09:06 /dev/audioctl

Thanks!

Will

_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[Brian Cameron]

Willie:

> The rebuild/install of SUNWgnome-wm.spec fixed the problem.  Thanks!

Great.

>> We should have better hover support.  Is the right fix to make GDM just
>> work this way and respond to hover directly, or would it make more sense
>> to just integrate MouseTweaks so that it always runs with GDM?
>
> Integrating MouseTweaks in the panel is a great idea, and I think that
> would be a sufficient solution.  In addition, the MouseTweaks 'hover'
> area is probably the thing that we'd want to put in the lower left
> instead of the a11y icon.
>
> I can open an RFE for this if this seems reasonable to everyone.

Sounds like a good idea to me.  The RFE can highlight that there are a
few different ways to solve the problem (integrate MouseTweaks or make
GDM just support hover directly), and we can discuss how to best
implement this.

>>> - There are no shortcuts to launch any assistive technology.  We
>>> probably need a community discussion about these if the same gestures
>>> are to be available at the login screen and the user session.
>>
>> I think these issues would really best be fixed by addressing the
>> problems in gnome-control-center and gnome-settings-daemon so that
>> these sorts of features work in the user session as well as the GDM
>> login session.  See here:
>>
>>   https://bugzilla.gnome.org/show_bug.cgi?id=531595
>>   https://bugzilla.gnome.org/show_bug.cgi?id=531596
>
> Mattias also wrote "We do have the framework in place for these now. If
> you open the keybinding capplet, there is a section for 'Accessibility'
> shortcuts, with 'Toggle magnifier', 'Toggle screen reader' and 'Toggle
> on-screen keyboard'.  We just need to set suitable values for these and
> enable them in the gdm session."
>
> Would these be for the gdm session only, or would they have to apply to
> the gdm session and user session?  The reason I ask is that the
> requirements and behavior of the assistive technology can be different
> between the login screen and the user session.  For example, GOK has a
> "login" mode, and we also will launch Orca a bit differently so it won't
> interfere with the login screen (i.e., we want to launch Orca without a
> main window on the login screen).

Since the "gdm" user has its own GConf configuration settings in the
gdm $HOME directory, it should be possible for the gdm user to specify
the commands that are appropriate for the login screen separately from
the user session.  I believe the commands that are used to launch
various default AT programs are stored in GConf, so I would think this
should work.

>>> - The magnifier launches the 'magnifier' application instead of Orca
>>> (Orca's magnification is preferred because it follows keyboard
>>> focus). The magnifier also comes up in split screen mode instead of
>>> full screen mode.
>>
>> This should just involve modifying the file
>> /usr/share/gdm/autostart/LoginWindow/gnome-mag.desktop to call the
>> appropriate program instead of calling "magnifier -v -m".  If you
>> want to propose a patch, I would think this would get accepted upstream
>> without much issue.
>
> I'll take a look.  Modifying this to launch Orca with "--enable
> magnifier" should be pretty simple to do.

Yes, I'd imagine if you file a bug with a patch that it would get
upstream pretty easily.

>>> - The gdm screen is launched without accessibility enabled.  As a
>>> result, GTK+ does not appear to load the a11y modules and the
>>> at-spi-registryd is not launched.  This yields the login screen
>>> inaccessible.  a11y probably should be enabled by default for the gdm
>>> screen, and this would hopefully fix the issues.
>>
>> If you want to enable a11y in GDM by default, you just need to set the
>> GConf key to turn it on for the "gdm" user.  The same key that gets
>> set when you run Preferences->Assistive Technologies and click the
>> checkbox next to "Enable assistive technologies".
>
> Does this mean the gdm user now has a specific gconf area for itself? If
> so, where is the suggested place to set the default values for gdm (vs.
> the normal user session)?

The gdm user's $HOME directory is typically /var/lib/gdm (you can check
/etc/passwd to check on your system).  So, it should just be a matter of
setting the right GConf key values in the /var/lib/gdm/.gconf or
/var/lib/gdm/.gconf.mandatory directories.

>>> - SlowKeys and BounceKeys features don't seem to work, but StickyKeys
>>> does.
>>
>> Do they not work at all, or they just do not work via the a11y menu?
>> Don't these features support Xserver hotkeys to launch them?  Do the
>> hotkeys work?  Do they work once the user session starts?  In other
>> words, are they only broken at the GDM login screen?
>
> They work once the user session starts, but not at the GDM login screen.
>  I'm not sure, but I wonder if those dialogs that warn you about a
> feature being turned on or off have a side effect?  These dialogs appear
> on the user session, but not the gdm login screen.

That sounds like a bug, then.  That is odd since the same Xserver
process is used for both the login screen session and the user session.
I'd file a bug so we can look at this.

>>> - When any of the AccessX keys are enabled, the "Keyboard
>>> Accessibility Status" applet should appear in the panel (it currently
>>> does not).  This applet provides the user with AccessX feedback, such
>>> as which modifiers are latched/locked.
>>
>> That seems a reasonable enhancement request, and something that would be
>> good to file a bug about.
>
> What if we just had the applet always installed (as we would do with
> MouseTweaks)?

That would seem reasonable to me.  Though we would need to review the
applet to make sure that it doesn't expose anything inappropriate for
the login screen.

>>> - Ctrl+Alt+Backspace doesn't seem to work any more (maybe an X Server
>>> configuration issue?).
>>
>> This is not really a GDM issue.  This is managed by the Xserver
>> configuration.
>
> Mattias also wrote: "This got converted from a server configuration
> thing to a regular xkb action."  Was that a change caused by something
> actively done somewhere in GNOME or somewhere else (e.g., the X Server
> folks made a modification in some X server revision)?

I don't know, hopefully someone else can answer.  Might be a better
question for someone more familiar with the Xserver.

>>> - Entering Ctrl, Alt, Tab in sequence when StickyKeys is enabled
>>> doesn't seem to permit the selection of the bottom panel.  It should.
>>
>> Again, this sounds like an Xserver issue.
>
> Odd.  It seems to work in the user session.

We should file a bug about the SlowKeys/BounceKeys issue mentioned above
and I would include this issue in the same report.  I'd bet these are
all related problems.

>>> - The GOK keyboard does not reflect the physical keyboard layout (it
>>> probably should -- if not possible, it probably should reflect a
>>> PC-101/PC-102/etc. layout).  Instead, it's a minimal A-Z keyboard.  
>>> This simplified keyboard does not include an "Alt" key.
>>
>> Is this an issue specific to launching GOK when GDM is running, or is
>> this a problem in the user session as well?
>
> This one does seem to be a general GOK/XKB interaction problem.  GOK
> fails to pick up the keyboard layout for both the desktop and login screen.

Sounds like a GOK bug, and probably not something that is productive to
discuss in this forum then.

>> If you are testing on Solaris, it might be a permissions issue.  The old
>> GDM used to call /usr/bin/setfacl to add the gdm user to the /dev/audio
>> and /dev/audioctl device permissions.  I wonder if that needs to be
>> ported to the new GDM also.
>
> Yep - most likely a permissions issue:
>
> wwalker@osol:~$ ls -lL /dev/audio*
> crw------- 1 wwalker staff 238, 3 2009-10-16 09:06 /dev/audio
> crw------- 1 wwalker staff 238, 4 2009-10-16 09:06 /dev/audioctl

It will probably take me a week or so, but I will work on getting this
fixed in the new GDM and will let you know when there are updated
packages for you to test.  It shouldn't be a problem to get this
fixed quickly.  It would help if you could file a bug at
defect.opensolaris.org to help track it.  I believe this is really a
Solaris specific issue, though.  So it is probably better to continue
discussing this issue at defect.opensolaris.org instead of here.

Brian
_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[Willie Walker]

Brian Cameron wrote:

>> Integrating MouseTweaks in the panel is a great idea, and I think that
>> would be a sufficient solution.  In addition, the MouseTweaks 'hover'
>> area is probably the thing that we'd want to put in the lower left
>> instead of the a11y icon.
>>
>> I can open an RFE for this if this seems reasonable to everyone.
>
> Sounds like a good idea to me.  The RFE can highlight that there are a
> few different ways to solve the problem (integrate MouseTweaks or make
> GDM just support hover directly), and we can discuss how to best
> implement this.

https://bugzilla.gnome.org/show_bug.cgi?id=599113, with my bias towards
just putting MouseTweaks in the panel shown. ;-)

> Since the "gdm" user has its own GConf configuration settings in the
> gdm $HOME directory, it should be possible for the gdm user to specify
> the commands that are appropriate for the login screen separately from
> the user session.  I believe the commands that are used to launch
> various default AT programs are stored in GConf, so I would think this
> should work.

Where in the gdm git sources are the default settings held?  Is this the
data/session-setup.entries file?

>> They work once the user session starts, but not at the GDM login
>> screen.  I'm not sure, but I wonder if those dialogs that warn you
>> about a feature being turned on or off have a side effect?  These
>> dialogs appear on the user session, but not the gdm login screen.
>
> That sounds like a bug, then.  That is odd since the same Xserver
> process is used for both the login screen session and the user session.
> I'd file a bug so we can look at this.

For additional info - I can in fact enable StickyKeys, SlowKeys, and
MouseKeys using the X server hot keys.  I can only enable StickyKeys
from the a11y dialog on the login screen, but I can enable StickyKeys,
SlowKeys, and BounceKeys from the dialog in the normal user session.

Here's some related bugs I just opened:

https://bugzilla.gnome.org/show_bug.cgi?id=599115
https://bugzilla.gnome.org/show_bug.cgi?id=599117

>>>> - When any of the AccessX keys are enabled, the "Keyboard
>>>> Accessibility Status" applet should appear in the panel (it
>>>> currently does not).  This applet provides the user with AccessX
>>>> feedback, such as which modifiers are latched/locked.
>>>
>>> That seems a reasonable enhancement request, and something that would be
>>> good to file a bug about.

https://bugzilla.gnome.org/show_bug.cgi?id=599114

>>>> - Ctrl+Alt+Backspace doesn't seem to work any more (maybe an X
>>>> Server configuration issue?).

http://who-t.blogspot.com/2009/04/zapping-server.html

>>>> - Entering Ctrl, Alt, Tab in sequence when StickyKeys is enabled
>>>> doesn't seem to permit the selection of the bottom panel.  It should.
>>>
>>> Again, this sounds like an Xserver issue.
>>
>> Odd.  It seems to work in the user session.

https://bugzilla.gnome.org/show_bug.cgi?id=599116

> fixed quickly.  It would help if you could file a bug at
> defect.opensolaris.org to help track it.  I believe this is really a
> Solaris specific issue, though.  So it is probably better to continue
> discussing this issue at defect.opensolaris.org instead of here.

http://defect.opensolaris.org/bz/show_bug.cgi?id=12125

Call me "Willie the Bug Man".

Thanks!

Will
_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[Brian Cameron]

Willie:

>> Since the "gdm" user has its own GConf configuration settings in the
>> gdm $HOME directory, it should be possible for the gdm user to specify
>> the commands that are appropriate for the login screen separately from
>> the user session.  I believe the commands that are used to launch
>> various default AT programs are stored in GConf, so I would think this
>> should work.
>
> Where in the gdm git sources are the default settings held?  Is this the
> data/session-setup.entries file?

Yes.

Brian
_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list