Re: [orca-list] gdm Accessibility with 2.28

[Steve Holmes <steve holmes88 gmail com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

More on this subject, I poked around in some of my system logs and in
/var/log/messages.log, I found the following:
gnome-session[15729]: WARNING: Application 'at-spi-registryd.desktop'
failed to register before timeout
Any idea what this means or how to correct it?

Since my last post, I copied the orca-screen-reader.desktop into
/etc/xdg/autostart directory and the at-spi desktop file was already
there.  Dunno if this error was popping up before I copied in the orca
file but I am grasping at straws here some to try and get an
accessible login.

Before, I never had an accessible login from gdm but was able to add
some sound queues and pre-recorded wav files to prompt me but that all
died with the upgrade to gdm 2.28.

On Tue, Oct 13, 2009 at 10:35:28PM -0700, Steve Holmes wrote:
> There has apparently been some big changes to gdm's configuration
> setup.  I'm curious as to if any Arch-Linux users out there have run
> into this and how they went about getting gdm to talk before logging
> in?  I found a link to the gdm reference manual but I'm still missing
> something.  The manual talks about desktop files and there happens to
> be a screen reader desktop file in /usr/share/gdm/autostart but I
> don't think that is automatically being activated.  I wouldn't think
> it would be by default for most regular users out there.  I would
> think that file would have to go in another autostart direct to be in
> effect.
>
> I'm on an Arch-Linux system and I do believe the loss of the original
> /etc/gdm/custom.conf usability is not unique to Arch.
>
> Any ideas?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEAREDAAYFAkrVbVQACgkQWSjv55S0LfHz2gCdEKxaNKrUShwezrV75QC5tqt1
pXEAoOhtjeNgmGCj+qOn7foDbP3CNpXW
=eela
-----END PGP SIGNATURE-----