Re: [orca-list] Gdm on Arch linux

[Steve Holmes <steve holmes88 gmail com>]

This is an interesting find.  It seems like every time I turn around,
gconf is changing or getting restructured and consequently breaks gdm
and attempts to keep it accessible.  I personally haven't found
anything around that describes how gconf workss nor how to use it
properly.  Then while all this is going on, there's talk of migrating
to g-settings? I really wish some developers would slow down a bit and
let the dust settle on a current implementation before moving on to
something else! It's no wonder a11y gets stuck in the back seat and so
often overlooked!

I wonder if I need to add this to my Arch Linux instructions to get
gdm talking.  Funny, I never ran into this situation in the past.
Hopefully someone can step forward on the list and offer some wisdom
about this.  I could update the wiki with this bit and if we learn
something later, this can be updated accordingly.

Thanks for letting us know and wow you must have had to do sume real
digging to uncover this.

On Sun, Oct 17, 2010 at 12:53:21AM +0100, Michael Whapples wrote:
>  Hello,
> There is another issue for getting accessible login on a new
> install. Basically when you install now there is a file
> /var/lib/gdm/.gconf.path which gets gconf to load settings from a
> system wide but read only source using settings to the GDM user only
> if they are defined. The problem with this is that as the system
> wide settings define /desktop/gnome/interface/accessibility then
> when you try and set this it says it cannot set the key because the
> source is read only. temporarily removing this file from
> /var/lib/gdm/ will allow you to set the gconf keys needed for
> accessible login.
>
> My questions go:
> * Is this .gconf.path file  a standard file for gconf in GDM?
> * Is this really a gconf or gdm bug, where should I report it?
> * Is there a better way to tell gconf to set the value by using the
> user local settings files?
>
> Michael Whapples
> On -10/01/37 20:59, Steve Holmes wrote:
> > Yes; please read the other messages I pointed out on this list and the
> > speechd list concerning running speech-dispatcher as a system
> > service.  I also recently mentioned the package up on AUR called
> > speech-dispatcher-git which has all the speech-dispatcher configs in
> > place to support this function.
> >
> > In addition, there is one hack you have to do for now until I get a
> > resolution to this and that is with /usr/bin/orca.  You will have to
> > go into that script and just before orca gets started, insert a line
> > to source /etc/profile.d/speechd.sh. This will set the environment
> > variable, $SPEECHD_ADDRESS which is needed to connect to the
> > speech-dispatcher server.  Be sure speech-dispatcher is already
> > running and verify that spd-say speaks a test string before restarting
> > gdm and you should be good to go.
> >
> > On Sat, Oct 16, 2010 at 11:26:32PM +0200, Christian wrote:
> > > Hi all,
> > > Well, has anyone now found a solution to get the Gnome logon screen being accessible on Arch with the 
> > > latest gdm?
> > > Many thanks,
> > > Christian
> > >
> > > _______________________________________________
> > > orca-list mailing list
> > > orca-list gnome org
> > > http://mail.gnome.org/mailman/listinfo/orca-list
> > > Visit http://live.gnome.org/Orca for more information on Orca.
> > > The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> > > The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> > > Netiquette Guidelines are at http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines
> > > Log bugs and feature requests at http://bugzilla.gnome.org
> > > Find out how to help at http://live.gnome.org/Orca/HowCanIHelp