Re: [orca-list] [Testers wanted before the official release] Slint64-4.2.1 release candidate is accessible.
- From: Peter Vágner <pvdeejay gmail com>
- To: Didier Spaier <didier slint fr>
- Cc: orca-list <orca-list gnome org>, Jude DaShiell <jdashiel panix com>
- Subject: Re: [orca-list] [Testers wanted before the official release] Slint64-4.2.1 release candidate is accessible.
- Date: Sun, 22 Oct 2017 17:34:45 +0200
Hello,
Some more experiments here.
In our xinit config we are roughly doing something like this - see some added comments to explain my thoughts:
if [ -f ~/.config/startorca ]; then
# init some ENV variables
/usr/bin/speech-dispatcher -d
/usr/bin/orca # Orca will start at-spi if it's not running which will launch dbus if it's not running.
fi
if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then # Here console kit would also try to run dbus however dbus is already running so I guess we might end up missing some bus addresses or something
ck-launch-session dbus-launch --exit-with-session startlxde
else
startlxde
fi
When orca starts up and there is no instance of at-spi and speech-dispatcher orca will try to spawn both of them.
In gnome, at-spi is started via
/etc/xdg/autostart/at-spi-dbus-bus.desktop
By looking to the at-spi2-core build configuration I can verify this is a part of at-spi2-core.
It's specific to gnome and it appears gnome is the only DE it has accessibility turned on by default.
It reads...
[Desktop Entry]
Type=Application
Name=AT-SPI D-Bus Bus
Exec=/usr/lib/at-spi2-core/at-spi-bus-launcher --launch-immediately
_OnlyShowIn_=GNOME;Unity;
NoDisplay=true
AutostartCondition=GSETTINGS org.gnome.desktop.interface toolkit-accessibility
X-GNOME-AutoRestart=true
X-GNOME-Autostart-Phase=Initialization
When converted to our setup it might look like
[Desktop Entry]
Type=Application
Name=AT-SPI D-Bus Bus
Exec=/usr/libexec/at-spi-bus-launcher --launch-immediately
NoDisplay=true
AutostartCondition=[ -f ~/.config/startorca ]
So based off of that I guess we need to seperate accessibility setup into two parts:
* Configure all the variables and settings within the xinit configuration before launching the actual session.
* Where possible configure session autostart features to start orca.
Only we need to decide if we are going to start at-spi as a part of our session startup or we can keep orca handling its launch as soon as it starts.
I originally assumed seperate at-spi startup might be usefull if we wish to have orca access to apps running as root because gnome is the only DE where I have this seen working consistently so far, however on this install of slint I can use su to gain root and then launch gparted for example and orca reads it all fine no mather how at-spi is started.
Here is orca desktop file I have put into my
~/.config/autostart
after I have commented out call to it and call to speech-dispatcher in the xinit config.
[Desktop Entry]
Type=Application
Version=1.0
Name=orca
Exec=/usr/bin/orca
AutostartCondition=[ -f ~/.config/startorca ]
With session autostart handling orca startup I do also have desktop icons and they are accessible. Sometimes after closing all the windows focus is not automagically placed to the desktop so flat review or random mouse clicks are needed but still it's a good move I feel.
Greetings
Peter
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]