Bug #9260

Orca reads neither Tor Browser nor Thunderbird if started after it

Added by sajolida 2015-04-18 20:33:31 . Updated 2017-11-15 11:49:35 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Accessibility
Target version:
Tails_3.3
Start date:
2015-04-18
Due date:
% Done:

100%

Feature Branch:
bugfix/14752-a11y-enabled-after-tor-browser-is-started
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Browser
Deliverable for:

Description

To reproduce on Tails 1.3.2:

1. Start Tails without networking.
2. Start Tor Browser.
3. Start Orca (Applications → Universal Access → Orca) and click Ok to enable default options.
4. Double-click on some text on the Tor Browser error page.
5. Nothing is read.

If you invert steps 2 and 3, the text in step 5 is read.

Subtasks

Related issues

Related to Tails - Bug #9051: Tor Launcher is not accessible Confirmed 2015-03-14
Related to Tails - Bug #14752: On-screen keyboard works neither in Tor Browser nor in Thunderbird if started after it Resolved 2017-09-30
Blocked by Tails - Bug #14735: stable branch FTBFS since the 3.2 release Resolved 2017-09-29

History

#1 Updated by sajolida 2015-04-18 20:33:56

  • related to Bug #7502: Unsafe Browser is not accessible added

#2 Updated by sajolida 2015-04-18 20:43:44

  • related to Bug #9261: Tor Browser crashes on key press when read by Orca added

#3 Updated by intrigeri 2015-04-19 12:01:46

I can reproduce this. I see no corresponding AppArmor log messages, so I think it’s unrelated. Now, I’m inclined to flag this as low priority, if not rejected: a user who needs Orca will have it started first… otherwise they’ll simply be unable to start Tor Browser.

#4 Updated by intrigeri 2015-04-19 12:04:38

  • Type of work changed from Code to Discuss

#5 Updated by intrigeri 2015-04-19 12:05:05

  • related to deleted (Bug #9261: Tor Browser crashes on key press when read by Orca)

#6 Updated by sajolida 2015-04-22 11:03:37

  • Assignee set to pzajda
  • Priority changed from Normal to Low
  • QA Check set to Info Needed

pzajda, can you confirm our analysis and otherwise bring this back to
“Normal” priority?

#7 Updated by intrigeri 2017-04-01 06:52:54

  • related to Bug #9051: Tor Launcher is not accessible added

#8 Updated by sajolida 2017-04-13 10:06:56

  • Subject changed from Orca doesn't read Tor Browser if started after Tor Browser to Orca doesn't read Tor Browser if Orca is started after Tor Browser

#9 Updated by Anonymous 2017-06-29 09:57:41

ping @pzajda, can you still reproduce this on current Tails?

#10 Updated by pzajda 2017-07-13 16:27:31

I’ve just checked and this issue still occurs with Tail 3.0.1.

#11 Updated by intrigeri 2017-07-13 18:26:40

  • Assignee deleted (pzajda)
  • Priority changed from Low to Normal
  • QA Check deleted (Info Needed)
  • Type of work changed from Discuss to Code

#12 Updated by intrigeri 2017-09-02 08:16:19

#13 Updated by intrigeri 2017-09-02 08:16:59

  • blocked by Bug #12384: Forward Greeter accessibility settings to the GNOME session added

#14 Updated by intrigeri 2017-09-02 08:17:31

I believe Bug #12384 will fix this, by ensuring Orca is started early after login whenever it was enabled in the Greeter.

#15 Updated by intrigeri 2017-09-02 08:18:17

  • blocks deleted (Bug #12384: Forward Greeter accessibility settings to the GNOME session)

#16 Updated by intrigeri 2017-09-02 08:18:41

  • blocked by Bug #12384: Forward Greeter accessibility settings to the GNOME session added

#17 Updated by intrigeri 2017-09-02 08:21:14

  • related to deleted (Bug #9051: Tor Launcher is not accessible)

#18 Updated by intrigeri 2017-09-02 08:21:43

  • related to Bug #9051: Tor Launcher is not accessible added

#19 Updated by intrigeri 2017-09-02 08:22:49

  • related to deleted (Bug #7502: Unsafe Browser is not accessible)

#20 Updated by intrigeri 2017-09-30 07:32:32

  • Subject changed from Orca doesn't read Tor Browser if Orca is started after Tor Browser to Orca doesn't read Tor Browser if started after it

#21 Updated by intrigeri 2017-09-30 07:32:41

  • related to Bug #14752: On-screen keyboard works neither in Tor Browser nor in Thunderbird if started after it added

#22 Updated by intrigeri 2017-09-30 08:58:05

  • blocked by Bug #14735: stable branch FTBFS since the 3.2 release added

#23 Updated by intrigeri 2017-09-30 08:58:56

  • Status changed from Confirmed to In Progress
  • Assignee set to intrigeri
  • Target version set to Tails_3.3
  • % Done changed from 0 to 10
  • Feature Branch set to bugfix/14752-a11y-enabled-after-tor-browser-is-started

#24 Updated by intrigeri 2017-10-01 07:46:12

  • Subject changed from Orca doesn't read Tor Browser if started after it to Orca reads neither Tor Browser nor Thunderbird if started after it

#25 Updated by intrigeri 2017-10-01 08:15:29

  • % Done changed from 10 to 30

Fixed for Thunderbird as well. Another full test suite run and I think it’ll be ready for QA :)

#26 Updated by intrigeri 2017-10-01 10:25:21

  • Assignee changed from intrigeri to anonym
  • % Done changed from 30 to 50
  • QA Check set to Ready for QA

Full test suite, including @fragile, passed.

#27 Updated by anonym 2017-10-04 16:23:12

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

#28 Updated by anonym 2017-11-15 11:44:34

  • blocks deleted (Bug #12384: Forward Greeter accessibility settings to the GNOME session)

#29 Updated by anonym 2017-11-15 11:49:35

  • Status changed from Fix committed to Resolved