"Electrum starts" test step is broken on Buster
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
Revert "Test suite: remove totally broken Electrum scenario" (refs: #16969)
This reverts commit f092b0d6f268a12550283e3a510f0455055ca1d9.
We have a working Electrum version again.
Revert "Revert "Test suite: remove totally broken Electrum scenario" (refs: #16969)"
This reverts commit 3bba768b940f498d66215a16c4c4c95f98d62be6.
Unfortunately, this test is still broken on Buster as Dogtail can't see
Electrum's widgets, and even ORCA can only read part of its interface.
#10 Updated by segfault about 1 month ago
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 about 1 month ago
I built Tails with recommended packages , 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.
 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 about 1 month ago
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 about 1 month ago
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.
#18 Updated by intrigeri about 1 month ago
- Target version deleted (
This was added to 4.0 because we thought that it would be easier to fix once we upgraded Electrum on #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.