FS#67271 - [firefox] Firefox is not letting me disable the accessibility service when not in use
Attached to Project:
Arch Linux
Opened by Doug (neo-alquimista) - Tuesday, 14 July 2020, 00:41 GMT
Last edited by Jan Alexander Steffens (heftig) - Saturday, 26 March 2022, 16:00 GMT
Opened by Doug (neo-alquimista) - Tuesday, 14 July 2020, 00:41 GMT
Last edited by Jan Alexander Steffens (heftig) - Saturday, 26 March 2022, 16:00 GMT
|
Details
Description:
It started after I installed the packages "orca" and "espeak-ng". The accessibility feature toggle on the SHIFT+F12 panel is greyed out, claiming it cannot turn it off because it is being used outside the developer tools. I could not, however, pinpoint what is supposedly using it. Things I've tried: - Reboot - Confirmed that Orca is not running, nor it is started on boot - Killed the dbus-daemon process and reran Firefox: "/usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3". This process is spawned again by Firefox in its startup. Additional info: * Firefox package version: 78.0.2-1 * Orca version: 3.36.3-1 * espeak-ng version: 1.50-2 * dbus version: 1.12.20-1 I have attached the journald log. If a more specific log file is needed, I'll promptly provide it. Steps to reproduce: 1. Install Firefox 2. Install packages "orca" and "espeak-ng". I had also installed the package "espeak", but later removed it. 3. (not sure if needed) Enable accessibility features in the SHIFT+F12 panel. Try doing this and restarting Firefox if it doesn't reproduce the problem straight away. |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Saturday, 26 March 2022, 16:00 GMT
Reason for closing: Fixed
Saturday, 26 March 2022, 16:00 GMT
Reason for closing: Fixed
Comment by Doug (neo-alquimista) -
Tuesday, 14 July 2020, 00:55 GMT
(ignore this duplicated comment)
Comment by Doug (neo-alquimista) -
Tuesday, 14 July 2020, 01:05 GMT
Journald log file:
https://gist.github.com/o-alquimista/2b768c0abc612d0e4693bac2b72cc0fc
Comment by mattia (nTia89) -
Saturday, 26 March 2022, 08:16 GMT
I cannot reproduce the issue. Is it still valid for you?
Comment by Doug (neo-alquimista) -
Saturday, 26 March 2022, 12:38 GMT
No, it doesn't affect me any more.