how to enable accessibility for Firefox in Debian ARM64

classic Classic list List threaded Threaded
23 messages Options
12
Reply | Threaded
Open this post in threaded view
|

how to enable accessibility for Firefox in Debian ARM64

Mgr. Janusz Chmiel-2
Dear specialists,
Because packagers of Debian distribution created many many ARM 64 bit
packages, I would like to know, if Firefox havebeen compiled with
accessibility support, or if this support must be enabled or Firefox
would had to be recompiled, so AT-spi and Orca could be usable with
Firefox on ARM64 bit architecture.
Firefox is working including hod keys support, but Orca is totallysilent
insidethis process Window.
.
Thank you very much for yours answer.

Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

Samuel Thibault-8
Mgr. Janusz Chmiel, le mar. 30 oct. 2018 13:40:37 +0100, a ecrit:
> Because packagers of Debian distribution created many many ARM 64 bit
> packages, I would like to know, if Firefox havebeen compiled with
> accessibility support,

There is no reason why accessibility would have been disabled.

> Firefox is working including hod keys support, but Orca is totallysilent
> insidethis process Window.

IIRC you are running this in a very particular environment. You could
check with

$ git clone https://salsa.debian.org/a11y-team/check-a11y.git
$ cd check-a11y
$ ./troubleshoot

whether your environment has proper configuration.

Samuel

Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

Mgr. Janusz Chmiel-2
Mr Tibault,
Thank you very much for yours advices. I will test The environment.
Maybe, that thanksto Android lack of shared memory file creation or pair
of sockets communication issue, that Firefox can not work with Orca
because of it. I even get AN segmentation fault from Firefox.
So may be, that there is really some sockets issue.
I Am working with Termux on Android, I Am testing available scripts
including Ubuntu, Debian and Arch Linux.


Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

Samuel Thibault-8
Mgr. Janusz Chmiel, le mar. 30 oct. 2018 13:59:10 +0100, a ecrit:
> Maybe, that thanksto Android lack of shared memory file creation or
> pair of sockets communication issue, that Firefox can not work with
> Orca because of it.

But do other applications show up on Orca?

Samuel

Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

Mgr. Janusz Chmiel-2
Here is The output.
Packages
PASS: at-spi2-core installed
PASS: libgail-common installed
PASS: libatk-adaptor installed
FAIL: qt-at-spi not installed, Qt4 applications will not be accessible
FAIL: libatk-wrapper-java not installed, Java Swing applications will
not be accessible

Running environment
FAIL: at-spi-bus-launcher is not running as user
FAIL: at-spi2-registryd is not running as user
FAIL: no session bus address in $DBUS_SESSION_BUS_ADDRESS
PASS: got accessibility bus
unix:abstract=/tmp/dbus-0aJpdw97dC,guid=6b503f50cdff388c5b7209b75bd
8570d from session dbus
PASS: got accessibility bus
unix:abstract=/tmp/dbus-0aJpdw97dC,guid=6b503f50cdff388c5b7209b75bd
8570d from root window
PASS: accessibility buses from session dbus and from root window match

Layer enabling
WARN: GTK_MODULES does not contain gail, GTK2 applications may not be
accessible
WARN: GTK_MODULES does not contain atk-bridge, GTK2 applications may not
be accessible
WARN: QT_ACCESSIBILITY is not set to 1, Qt4 applications may not be
accessible

Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

Michael A Ray
In reply to this post by Samuel Thibault-8
Hello,

You didn't specify which ARM 64-bit machine you are running this on.

If it is a Raspberry Pi 3, then you cannot get sound currently from
aarch64, as there is no 'userland' code, the stuff that usually lives in
/opt, for 64-bit kernels.

And as far as I know the Pi Foundation has no intention currently of
modifying it to provide 64-bit versions of this code, which drives the GPU.

I have no knowledge of any other 64-bit ARM machine.

I guess it would work with an external USB sound device though, as that
avoids the GPU stuff, I think.

Mike

On 30/10/2018 12:47, Samuel Thibault wrote:

> Mgr. Janusz Chmiel, le mar. 30 oct. 2018 13:40:37 +0100, a ecrit:
>> Because packagers of Debian distribution created many many ARM 64 bit
>> packages, I would like to know, if Firefox havebeen compiled with
>> accessibility support,
>
> There is no reason why accessibility would have been disabled.
>
>> Firefox is working including hod keys support, but Orca is totallysilent
>> insidethis process Window.
>
> IIRC you are running this in a very particular environment. You could
> check with
>
> $ git clone https://salsa.debian.org/a11y-team/check-a11y.git
> $ cd check-a11y
> $ ./troubleshoot
>
> whether your environment has proper configuration.
>
> Samuel
>
>


--
Michael A. Ray
Analyst/Programmer
Witley, Surrey, South-east UK

"Perfection is achieved, not when there is nothing more to add, but when
there is nothing left to take away." -- A. de Saint-Exupery

https://cromarty.github.io/
http://eyesfreelinux.ninja/
http://www.raspberryvi.org/


Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

Samuel Thibault-8
In reply to this post by Mgr. Janusz Chmiel-2
Mgr. Janusz Chmiel, le mar. 30 oct. 2018 14:07:54 +0100, a ecrit:
> Here is The output.

> Running environment
> FAIL: at-spi-bus-launcher is not running as user
> FAIL: at-spi2-registryd is not running as user

That's odd, you don't have these running?

> FAIL: no session bus address in $DBUS_SESSION_BUS_ADDRESS
> PASS: got accessibility bus
> unix:abstract=/tmp/dbus-0aJpdw97dC,guid=6b503f50cdff388c5b7209b75bd
> 8570d from session dbus

Mmm, so the well-known path is enough. Perhaps DBUS_SESSION_BUS_ADDRESS
is needed for firefox to work. Could you git pull within check-a11y to
get the modification I have just made, to know what you would need to
put in DBUS_SESSION_BUS_ADDRESS?

> Layer enabling
> WARN: GTK_MODULES does not contain gail, GTK2 applications may not be
> accessible
> WARN: GTK_MODULES does not contain atk-bridge, GTK2 applications may not be
> accessible

That might also be an issue, you could try

export GTK_MODULES=gail:atk-bridge

Samuel

Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

Samuel Thibault-8
In reply to this post by Samuel Thibault-8
Samuel Thibault, le mar. 30 oct. 2018 14:01:59 +0100, a ecrit:
> Mgr. Janusz Chmiel, le mar. 30 oct. 2018 13:59:10 +0100, a ecrit:
> > Maybe, that thanksto Android lack of shared memory file creation or
> > pair of sockets communication issue, that Firefox can not work with
> > Orca because of it.
>
> But do other applications show up on Orca?

Please answer this question too. Unanswered questions means I miss
information to be able to conclude anything.

Samuel

Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

Mgr. Janusz Chmiel-2
Other applications areworking with Orca without issues, sure I do not
have something setup for now such as QT accessibility support.
But gedit, Pluma, even synaptics package manager work without issues.
Sure, I can not use lxde4 with Orca, hodkeys do not work there and Orca
is silent.
So I want to run openbox &
orca &
And specific application such as
firefox &
Because this procedure gives good results. Thanks to build in Pulseaudio
for Termux, which reliablz cooperates withAndroid operating system,
delayis not big and no speechdistortion at all. And even no random
crashes even while typing fast onThe keyboard.

Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

mattias jonsson
in wich build are pulseaudio in termux?

På 30 oktober 2018 2:43:05 em "Mgr. Janusz Chmiel" <[hidden email]>
skrev:

> Other applications areworking with Orca without issues, sure I do not
> have something setup for now such as QT accessibility support.
> But gedit, Pluma, even synaptics package manager work without issues.
> Sure, I can not use lxde4 with Orca, hodkeys do not work there and Orca
> is silent.
> So I want to run openbox &
> orca &
> And specific application such as
> firefox &
> Because this procedure gives good results. Thanks to build in Pulseaudio
> for Termux, which reliablz cooperates withAndroid operating system,
> delayis not big and no speechdistortion at all. And even no random
> crashes even while typing fast onThe keyboard.



Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

Mgr. Janusz Chmiel-2
In reply to this post by Samuel Thibault-8
       well-known path
/root/.dbus/session-bus/6a68d6b78714411e945e0bfc6f29ea48-0 says unix:abst
ract=/tmp/dbus-trOMoamaIh,guid=5b37503569acf1466fbdb9145bd8570d
PASS: got accessibility bus
unix:abstract=/tmp/dbus-0aJpdw97dC,guid=6b503f50cdff388c5b7209b75bd
8570d from session dbus
PASS: got accessibility bus
unix:abstract=/tmp/dbus-0aJpdw97dC,guid=6b503f50cdff388c5b7209b75bd
8570d from root window
PASS: accessibility buses from session dbus and from root window match


But how to set those values and which? How to run at-spi2-registryd and
how to run
at-spi-bus-launcher
Can I put commands to ./profile Bash file?


Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

Mgr. Janusz Chmiel-2
In reply to this post by mattias jonsson
Pulseaudio is stable and is Thepart of Termux repository. Official
Termux available on Google Play store support this sound server.
After you will install Termux, when you will run it.
Type
pkg install pulseaudio
You must also type The following commands to run Pulseaudio sound server
in Termux.

pulseaudio --start --exit-idle-time=-1
pacmd load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1
auth-anonymous=1
You can edit ./profile to add those lines above The last line. In this
case, Termux will automatically irun Pulseaudio sound server.

When you will install yours Linux distribution to Termux, do not forget
to add The following line to ./bash so Espeak and Speech-dispatcher will
work there with no issues.
export PULSE_SERVER=\"127.0.0.1
There are several distributions for Termux, which run perfectly. I
recommend to test Debian, Arch Linux and Ubuntu.
I love Debian, since there is The most friendly community here and even
I do not run normal Debian operating system, I run it by using termux,
Proot and Qemu user mode variant, which executes 64 bit code on ARM 32
bit CPU, it is possible to cope with sockets and other issues including
starting services.
Mr Vagner have informed Me about The way, how to setup Pulseaudio sound
server on Termux. So he is professional.

Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

Mgr. Janusz Chmiel-2
I have made mistake.

When you will install yours Linux distribution to Termux, do not forget
to add The following line to ./profile so Espeak and Speech-dispatcher
will work there with no issues.
export PULSE_SERVER=\"127.0.0.1
Profile Bash scriptalways resides inside /etc
so
nano /etc/profile

Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

Samuel Thibault-8
In reply to this post by Mgr. Janusz Chmiel-2
Mgr. Janusz Chmiel, le mar. 30 oct. 2018 14:59:44 +0100, a ecrit:
>       well-known path
> /root/.dbus/session-bus/6a68d6b78714411e945e0bfc6f29ea48-0 says unix:abstract=/tmp/dbus-trOMoamaIh,guid=5b37503569acf1466fbdb9145bd8570d

So you'd try to do

export DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-trOMoamaIh,guid=5b37503569acf1466fbdb9145bd8570d

before running firefox.

> But how to set those values and which? How to run at-spi2-registryd and
> how to run at-spi-bus-launcher

Since you said other applications are showing up in Orca, it means that
they are really running, and it's just that the "ps -x -o cmd" command
is not finding them out. Perhaps you could have a look at how to
properly detect them in your environment so we can improve the
troubleshoot script to use it.

Samuel

Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

Mgr. Janusz Chmiel-2
I Am sad. Because Firefox still do not want to cooperate with Orca. I
have exported all variables according to yours suggestions.
But no results.
So I have other question.
XserverXSDL a implementation of Xserver for Android do not contain
Xinerama extension. Is this Xserver specific extension Xinerama
extensioncrucial for some of included AT-SPi accessibility modules?
And I have other question.
Does somebody of us know about GTk compatible window manager, which can
be configured with no need to change source code of it to disable 3D
graphics support? Since Xserver XSDL do not support those instructions
and I do not like to recompile Android Kernel to include special drivers
for this purposes. And I do not know about otherXserver Android app.
Second, which is available on The Play store do not contain XKBT
extension and this extension is really crucial for Orca to detect
keyboard related events.
But I Am afraid, that there will not be such GTK compatible Window manager.
I also must disable picture loading in Firefox, because I AM getting
crytical errors related to graphics and this is making Firefox slow.

Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

Mgr. Janusz Chmiel-2
I will discuss with my ISP how to get reliably my IP address so if
somebody would have A good will to debug this issue remotely, with Me,
somebody can connect to my Debian session on Android by using ssh. Sure
it would be require if you would generate public key and I will add it
tomy Debian session.

I have even Audacity running and my sighted mother have confirmed Me,
that Xserver XSDL is even able to draw The GUi table inside Audacity
preferences. Audacity do not display too much crashes related to memory
allocations, only some bugs related to key accelerators, some values
inside Audacity.xml files are very probably incompatible with XKBT
implementation inside Xserver XSDL for Android.
But Short cut to display preferences menu works.

I have one non advanced question.
I need to create regular user, not root user on my Debian session. Since
VLC media player and many other apps simply do not allow Me to run as
root user.
Which command do I have to use?
And The professionally made script to install Debian on Termux is here.
May be, that somebody of us will analyse it to determine, if there is
something to repair or add to include full AT-SPI support for Firefox.

https://codeload.github.com/sp4rkie/debian-on-termux/zip/master

Script uses debootstrap and according to various messages while install
packages, this system is configured by using The best possible
techniques. Since when Debconf do its best to configure The tridgers for
Libcbin, there is nobug connection refused above this line.
There is also no issues related to errors connection to D-BUS sockets.
I believe, that somebody of us will look at this with Me, since it bring
Debian universal operating system to its next higher level.
It do not require Kernel related complex programmers tasks, it require
deep knowledge of Debian packaging system and D_BUS, sockets
communication. In some cases, some C or C++ specific aps do not work on
Android, because Android Kernel do not support shared memory
allocations, shared memory file creation. Fortunately, it is not
problem, because I do not have to run whole Gnome-session or Mate.
Gnome-keyring daemon report insufficient process capabilities. While
running Mate.

Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

Mgr. Janusz Chmiel-2

I have made functioning solution.
I have decided to work according to The instructions which are published
here.

https://wiki.debian.org/accessibility-devel

I have installed packages which have been described in The article.

I have installed LXDE
And then I typed
Openbox &
orca &
startlxde &
firefox &
And viola. Firefox cooperates with Orca.
I Am fighting with one big problem. I do not know, how to disable 3D
graphics by using some of GTK window managers, which are compatible with
Orca.
Many crytical errors are making Firefox process slower and slower. But
Orca build in navigation keys are working like a charm. I will try to
analyse window managers configuration files /etc if I will have some
chances to disable various graphics decorations. And 3D graphics
instructions.
But I Am very very glad, that I Am not having problems with Android
build in memory management. No memory allocation issues, no not enough
memory messages.
So it is always necessary to have some complete desktop environment
started before running Firefox in The Android by using Termux or other
project based on Proot module.

Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

Mgr. Janusz Chmiel-2
In reply to this post by Mgr. Janusz Chmiel-2
The secret is to add The following lines to to /etc/profile
eval $(dbus-launch); export DBUS_SESSION_BUS_ADDRESS DBUS_SESSION_BUS_PID
GSETTINGS_BACKEND=dconf gsettings set
org.gnome.desktop.a11y.applications screen-reader-enabled true
GSETTINGS_BACKEND=dconf gsettings set org.mate.interface accessibility true
GSETTINGS_BACKEND=dconf gsettings set org.mate.applications-at-visual
startup true
You have to add it in other case, Orca and Firefox will never cooperate
together.

It causes The at-spi assertion, but Firefox work. Sure, there are plenty
of bugs related to graphics error.
But Firefox is usable with Orca. Please do not forget to change sound
device in/etc/speech-dispatcher/speechd.conf
to The libao. I think, that speech-dispatcher autodetect sound server as
Pulseaudio by default, if The line is commentedby #
But if you will let Speech-dispatcher to work with Espeak according to
its default decision, you will occur issues. Letter by letter navigation
will not be reliable and you can occasionally get sockets related crash.
If you will use libao, youwill never occur crash related to speech
stability.

Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

Samuel Thibault-8
Hello,

Mgr. Janusz Chmiel, le lun. 05 nov. 2018 21:43:06 +0100, a ecrit:
> The secret is to add The following lines to to /etc/profile
> eval $(dbus-launch); export DBUS_SESSION_BUS_ADDRESS DBUS_SESSION_BUS_PID
> GSETTINGS_BACKEND=dconf gsettings set org.gnome.desktop.a11y.applications
> screen-reader-enabled true
> GSETTINGS_BACKEND=dconf gsettings set org.mate.interface accessibility true
> GSETTINGS_BACKEND=dconf gsettings set org.mate.applications-at-visual
> startup true
> You have to add it in other case, Orca and Firefox will never cooperate
> together.

Are the three gsettings really needed? I would have thought only the
first (i.e. "screen-reader-enabled") would be read by firefox.

Samuel

Reply | Threaded
Open this post in threaded view
|

Re: how to enable accessibility for Firefox in Debian ARM64

Mgr. Janusz Chmiel-2
I do not know, if all three settings are needed  It would require some
time to try it out.
Samuel, you are C language expert.
If Proot makes something wrong, that I Am getting truncate failed
permission denied message, for example, when pressing down arrow key
while I have opended /etc/profile in pluma.
When I have pressed down arrow key I have got this error message and
Orca have been silent.

I know, that you are very busy man andyou areworking on many projects.
But may be, that you could look inside Proot C source code why there is
so much errors related to truncate failed permission ednied.
You will also getthis bug when typing
espeak sometext
May be, that it is causing by The fact, that converting ARM64 bit ARM
assembly instructions to ARM32 have some shadow effects on mathematical
instructions.
I do not know, where to report this bug related to Proot module.
Since it exists across all Linux distributions so it is notDebian
specific one.


12