Bug #9732

Orca cannot work with Electrum

Added by emmapeel 2015-07-13 07:32:34 . Updated 2020-05-01 16:53:08 .

Target version:
Start date:
Due date:
% Done:


Feature Branch:
Type of work:

Affected tool:
Deliverable for:


Reported by user:

steps to reproduce:

- Turn Orca on
- Open electrum

Orca cannot read it.


Related issues

Related to Tails - Bug #16969: "Electrum starts" test step is broken on Buster In Progress
Blocked by Tails - Bug #16421: Electrum Phishing Attack - Upstream Fix Committed Resolved 2019-02-05


#1 Updated by intrigeri 2015-07-15 09:15:02

  • Assignee set to anonym

#2 Updated by sajolida 2016-02-08 16:06:23

  • Assignee changed from anonym to emmapeel
  • Target version set to Tails_2.2
  • Type of work changed from Code to Test
  • Starter set to Yes

The next step I think is to test this on Debian Jessie and see if it’s specific to Tails. Assigning to emmapeel and next release as this should be part of the initial research for the ticket but you’re allowed to find other volunteers :)

#3 Updated by sajolida 2016-02-08 18:35:28

  • QA Check set to Info Needed

#4 Updated by sajolida 2016-02-13 17:08:30

  • Status changed from New to Confirmed
  • Assignee deleted (emmapeel)
  • Target version deleted (Tails_2.2)
  • QA Check deleted (Info Needed)
  • Type of work changed from Test to Wait

Actually this has already been reported in Debian, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734235. So this is “Confirmed” but “Wait”.

#5 Updated by Anonymous 2017-06-28 10:58:55

Upstream bug has been filed: https://github.com/spesmilo/electrum/issues/1036

#6 Updated by Anonymous 2017-06-28 11:00:16

  • Starter deleted (Yes)

#7 Updated by intrigeri 2017-12-08 07:53:53

  • Affected tool set to Electrum

#8 Updated by Anonymous 2018-01-15 14:34:07

#9 Updated by intrigeri 2018-01-15 15:07:59

(What I committed to do on Feature #14522 is about the “core Tails system”, which is currently ill-defined, but during the discussion we’re having about defining it better, it was made clear that Electrum is definitely not part of it. Let’s not turn Feature #14522 into a catch-all ticket about all possible issues for vision-impaired people, otherwise we won’t ever close it and it does not make sense to add it to our roadmap as we did. Also, I want Feature #14522 to be something I can realistically complete by the end of 2019; given Electrum upstream seems to be mostly uninterested, I don’t want to have to port Electrum to Qt5 myself in order to get Feature #14522 done.)

#10 Updated by Anonymous 2018-08-18 11:43:34

This bug was forwarded to Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734235

#11 Updated by Anonymous 2018-08-18 11:44:48

And Electrum was ported to Qt5 according to https://github.com/spesmilo/electrum/issues/1036 but nobody reported back if it actually improves the situation.

#12 Updated by Anonymous 2018-08-18 11:47:19

  • Priority changed from Normal to Low

#13 Updated by intrigeri 2018-08-18 14:49:42

  • Type of work changed from Wait to Test

So next step is to try it again :)

#14 Updated by intrigeri 2018-08-18 14:50:57

  • Assignee set to s7r
  • Priority changed from Low to Normal
  • Parent task set to Feature #14522

s7r, can you please test this? Thanks in advance!

#15 Updated by s7r 2018-08-31 14:52:48

  • Type of work changed from Test to Wait

Tested on 3.9-rc1 with Electrum 3.1.3 and it does not work. It reads the initial wizard but it states that desktop assistance is disabled for Electrum. There is some work upstream quire recently to fix this https://github.com/spesmilo/electrum/issues/4637 and nothing has been merged yet, so it’ll come.

Setting this ticket to wait since there’s nothing we can do about it for the moment, but leaving the bug open so we don’t forget to test again.

#16 Updated by intrigeri 2019-03-08 16:29:35

According to the upstream ticket, most of the issues are fixed in 3.2.2.

#17 Updated by intrigeri 2019-09-08 06:35:21

  • blocked by Bug #16421: Electrum Phishing Attack - Upstream Fix Committed added

#18 Updated by intrigeri 2019-09-08 06:36:32

  • Type of work changed from Wait to Test

In theory the upgrade planned in Bug #16421 should fix this for free ⇒ once that’s done, next step is to test & verify that the screen reader can read Electrum. Thanks in advance!

#19 Updated by s7r 2019-10-01 22:01:27

  • Type of work changed from Test to Code

Well yes, in theory. But I have tested with Electrum 3.3.8 in tails-amd64-bugfix_16421-fix-electrum-4.0-20190927T1734Z-3bba768b94+devel@fe2c7513ee.iso and ScreenReader still does not read Electrum. I am putting this out of test since my test does not pass unfortunately. If I’m wrong please correct me.

It “reads” it or at least it tries to read it. The top bar is read just fine (File, Wallet, View, etc.). The tabs (history / send / receive / addresses, etc.) are not read properly, more like "1, 2, 3, read only text, OK button, etc.) the notification messages pop-ups are also not read (only OK button is read). I am not sure if this is fixable.

#20 Updated by intrigeri 2019-10-05 06:51:35

  • related to Bug #16969: "Electrum starts" test step is broken on Buster added

#21 Updated by intrigeri 2019-10-05 07:05:21

segfault found out in Bug #16969 that installing qt5-gtk-platformtheme might help.

#22 Updated by zersiax 2020-05-01 16:53:08

Was that last idea ever tested?
Qt5 , although it does have accessibility support, doesn’t always immediately make things more accessible once it is implemented. It depends on a number of things, but those are mostly on Electrum’s side. Can anyone confirm if this works at present?
If not, I will both follow up with Electrum as well as look for possible GUI or CLI alternatives