Bug #16969

"Electrum starts" test step is broken on Buster

Added by intrigeri 2019-08-10 17:49:57 . Updated 2019-10-05 07:07:30 .

Status:
In Progress
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Electrum
Deliverable for:

Description

I’ve been so used to see the “Using a persistent Electrum configuration” fail since months that I did not notice that it failed much earlier on Buster than on Stretch:

  • on Stretch, it fails to connect to the Electrum servers (known issue wrt. the version we’re shipping)
  • on Buster, it fails at the “Electrum starts” step: Dogtail finds no “electrum” application when the “Electrum - Install Wizard” dialog is displayed; I’ve quickly tried the obvious, i.e. asking Dogtail to look for “electrum” and “Electrum - Install Wizard” instead, but none of these work

Files

recommended-packages.txt (4775 B) segfault, 2019-10-04 11:33:01

Subtasks

Related issues

Related to Tails - Bug #16281: Update the test suite for Buster Resolved 2019-01-05
Related to Tails - Bug #9732: Orca cannot work with Electrum Confirmed 2015-07-13
Blocks Tails - Feature #16209: Core work: Foundations Team Confirmed
Blocked by Tails - Bug #16421: Electrum Phishing Attack - Upstream Fix Committed Resolved 2019-02-05

History

#1 Updated by intrigeri 2019-08-10 17:50:26

#2 Updated by intrigeri 2019-08-14 06:48:11

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

#3 Updated by intrigeri 2019-08-14 06:48:55

  • Assignee deleted (anonym)
  • Priority changed from Elevated to Normal
  • Target version deleted (Tails_4.0)

As per discussion on the CI list, let’s not bother until we have a working Electrum (Bug #16421). Meanwhile, the affected scenario will be removed.

#4 Updated by intrigeri 2019-08-14 06:49:11

#5 Updated by intrigeri 2019-08-14 06:49:25

  • related to Bug #16281: Update the test suite for Buster added

#6 Updated by intrigeri 2019-09-08 06:30:23

  • Target version set to Tails_4.0

As per Bug #16421#note-20.

#7 Updated by segfault 2019-09-20 14:26:08

  • Status changed from Confirmed to In Progress

Applied in changeset commit:tails|3bba768b940f498d66215a16c4c4c95f98d62be6.

#8 Updated by segfault 2019-09-20 14:26:32

  • Assignee set to segfault
  • Feature Branch set to bugfix/16421-fix-electrum

#9 Updated by segfault 2019-10-03 16:17:20

The “Electrum starts” step fails because Electrum is not visible to Dogtail. It doesn’t seem to register with the accessibility interface.

#10 Updated by segfault 2019-10-03 17:06:47

It seems like all qt applications are not registering with the accessibility interface. Affected are: electrum, keepassxc, onionshare.

I tried the same on a Debian sid and there I can see those applications in Dogtail - but the Electrum app is called “python3” and doesn’t contain any information about its widgets.

#11 Updated by segfault 2019-10-04 11:17:04

I built Tails with recommended packages [1], as suggested by intrigeri, and now I see the same as on Sid: The Electrum window is displayed in Dogtail’s sniff tool as “python3” with no child nodes. So the tests still won’t work.

[1] FTR, I had to delete those local-hooks to get Tails to build with --apt-recommends true in auto/config:

config/chroot_local-hooks/04-change-gids-and-uids
config/chroot_local-hooks/05-adduser_tails-persistence-setup
config/chroot_local-hooks/06-adduser_clearnet
config/chroot_local-hooks/06-adduser_htp
config/chroot_local-hooks/06-adduser_tails-iuk-get-target-file
config/chroot_local-hooks/06-adduser_tails-upgrade-frontend
config/chroot_local-hooks/06-adduser_tor-launcher
config/chroot_local-hooks/07-adduser_tails-install-iuk
config/chroot_local-hooks/99-zzz_check_uids_and_gids

#12 Updated by intrigeri 2019-10-04 11:32:22

> and now I see the same as on Sid: The Electrum window is displayed in Dogtail’s sniff tool as “python3” with no child nodes. So the tests still won’t work.

On my sid (GNOME 3.34 + Wayland session), ORCA can read the Electrum UI.
But indeed, with Dogtail’s sniff tool I see the as you.
So it seems that Electrum is accessible for users who need this, but somehow it’s incompatible with Dogtail?

#13 Updated by segfault 2019-10-04 11:33:27

> The Electrum window is displayed in Dogtail’s sniff tool as “python3” with no child nodes

Same for OnionShare. KeepassXC shows up as “keepassxc” but also without child nodes.

I didn’t find out yet which package resulted in at least something showing up for Qt apps in Dogtail - and I don’t want to spend a lot of time on this, since the result doesn’t seem to be useful. I don’t see any obvious candidates in the diff of the packages installed in my old build and the one with --apt-recommends true. I’m attaching this list.

#14 Updated by segfault 2019-10-04 11:38:31

segfault wrote:
> I didn’t find out yet which package resulted in at least something showing up for Qt apps in Dogtail

It’s qt5-gtk-platformtheme

#15 Updated by segfault 2019-10-04 18:53:07

  • Assignee deleted (segfault)

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

  • related to Bug #9732: Orca cannot work with Electrum added

#17 Updated by intrigeri 2019-10-05 07:04:36

  • Feature Branch deleted (bugfix/16421-fix-electrum)

#18 Updated by intrigeri 2019-10-05 07:07:30

  • Target version deleted (Tails_4.0)

This was added to 4.0 because we thought that it would be easier to fix once we upgraded Electrum on Bug #16421. Unfortunately, that’s not the case, and given the amount of other work left to do for 4.0, I don’t think we can reasonably treat this as a release blocker.