Project Number Date
test_Tails_ISO_stable-flatpak 26 24 Sep 2026, 20:13

Failures Overview

The following summary displays scenarios that failed.

Feature: Installing and running Flatpak apps in Tails
Tags: @product @check_tor_leaks
5:23.180
Scenario Installing, starting and uninstalling a Flatpak
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.001
Steps
Given I have started Tails with the Flatpak feature from a USB drive with a persistent partition enabled and logged in and the network is connected 5:23.180
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:764:in `/^available upgrades have been checked$/'
./features/step_definitions/snapshots.rb:206:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:203:in `each'
./features/step_definitions/snapshots.rb:203:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:226:in `/^I\ have\ started\ Tails\ with\ the\ Flatpak\ feature\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/flatpak.feature:25:in `Given I have started Tails with the Flatpak feature from a USB drive with a persistent partition enabled and logged in and the network is connected'
When I start GNOME Software 0.000
And I install Signal Desktop using GNOME Software 0.000
Then the org.signal.Signal Flatpak is installed after at most 600 seconds 0.000
When I start the org.signal.Signal Flatpak 0.000
Then the org.signal.Signal Flatpak is running 0.000
Given I kill the org.signal.Signal Flatpak 0.000
And I go to the main screen of GNOME Software 0.000
When I uninstall Signal Desktop using GNOME Software 0.000
Then the org.signal.Signal Flatpak is uninstalled after at most 60 seconds 0.000
After features/support/hooks.rb:535 0.031
After features/support/hooks.rb:339 4.647 
SCENARIO FAILED: 'Installing, starting and uninstalling a Flatpak' (at time 00:12:47)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/00:12:47_Installing,_starting_and_uninstalling_a_Flatpak.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/00:12:47_Installing,_starting_and_uninstalling_a_Flatpak.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/00:12:47_Installing,_starting_and_uninstalling_a_Flatpak.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/00:12:47_Installing,_starting_and_uninstalling_a_Flatpak.journal
After features/support/hooks.rb:108 0.004
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:11.441
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 9.045
Then I wait until Tor is ready 2.389
And tca.conf includes the configured bridges 0.004
And available upgrades have been checked 5:0.001
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:764:in `/^available upgrades have been checked$/'
features/tor_bridges.feature:17:in `And available upgrades have been checked'
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:339 4.681 
SCENARIO FAILED: 'Using normal bridges' (at time 00:32:50)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/00:32:50_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/00:32:50_Using_normal_bridges.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/00:32:50_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/00:32:50_Using_normal_bridges.journal
After features/support/hooks.rb:108 0.047
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:30.345
Scenario Using obfs4 pluggable transports from a QR code
Steps
When I configure some obfs4 bridges from a QR code in the Tor Connection Assistant in hide mode 29.536
Then I wait until Tor is ready 0.803
And tca.conf includes the configured bridges 0.005
And available upgrades have been checked 5:0.000
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:764:in `/^available upgrades have been checked$/'
features/tor_bridges.feature:31:in `And available upgrades have been checked'
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:339 4.883 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:38:56)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/00:38:56_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/00:38:56_Using_obfs4_pluggable_transports_from_a_QR_code.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/00:38:56_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/00:38:56_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:108 0.069
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:37.006
Scenario TCA can reconnect after a connection failure
Steps
Given the Tor network and default bridges are blocked 0.986
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 28.818
Then the Tor Connection Assistant reports that it failed to connect 0.079
And tca.conf is empty 0.248
Given the Tor network and default bridges are unblocked 0.784
When I retry connecting to Tor 1.096
Then I wait until Tor is ready 4.984
And tca.conf includes no bridge 0.007
And available upgrades have been checked 5:0.000
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:764:in `/^available upgrades have been checked$/'
features/tor_bridges.feature:62:in `And available upgrades have been checked'
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:339 4.690 
SCENARIO FAILED: 'TCA can reconnect after a connection failure' (at time 00:45:45)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/00:45:45_TCA_can_reconnect_after_a_connection_failure.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/00:45:45_TCA_can_reconnect_after_a_connection_failure.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/00:45:45_TCA_can_reconnect_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/00:45:45_TCA_can_reconnect_after_a_connection_failure.journal
After features/support/hooks.rb:108 0.057
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
6:13.486
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.001
Steps
Given a computer 0.080
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 6:13.405
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:764:in `/^available upgrades have been checked$/'
./features/step_definitions/common_steps.rb:259:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/additional_software_packages.feature:79:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
And I configure APT to prefer an old version of cowsay 0.000
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 0.000
And I accept adding "cowsay" to Additional Software 0.000
And Additional Software is correctly configured for package "cowsay" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.000
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been installed 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
# We remove the newest package after it has been downloaded and before
# it is installed, so that the upgrade process fails
And I prepare the Additional Software upgrade process to fail 0.000
And the network is plugged 0.000
And Tor is ready 0.000
And available upgrades have been checked 0.000
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.000
And I can open the Additional Software configuration window from the notification 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been installed 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
And the network is plugged 0.000
And Tor is ready 0.000
Then the Additional Software upgrade service has started 0.000
And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000
After features/support/hooks.rb:535 0.040
After features/support/hooks.rb:339 5.075 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:26:30)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:26:30_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:26:30_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:26:30_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:26:30_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:26:30_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:26:30_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_mount
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:26:30_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:26:30_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:26:30_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal
After features/support/hooks.rb:108 0.011
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
5:51.877
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.001
Steps
Given a computer 0.076
And I start Tails from USB drive "__internal" with network unplugged 32.957
And I enable persistence 10.617
And I remove the "cowsay" deb files from the APT cache 0.034
And I log in to a new session 6.626
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 5:1.563
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:650:in `wait_notification'
./features/step_definitions/common_steps.rb:637:in `/^I (don't )?see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
features/additional_software_packages.feature:126:in `Then I see the "The installation of your additional software failed" notification after at most 300 seconds'
And I can open the Additional Software log file from the notification 0.000
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:535 0.054
After features/support/hooks.rb:339 8.244 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:32:27)
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:32:27_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:32:27_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:32:27_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:108 0.023
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
7:22.797
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.166
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.197
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.263
When the network is plugged 0.023
And Tor is ready 13.496
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2:2.893
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.028
Given I shutdown Tails and wait for the computer to power off 5.250
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.216
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.299
And the file system changes introduced in version 6.2~testoverlayfs are present 0.181
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.091
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.189
When the network is plugged 0.033
And Tor is ready 10.269
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.466
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.395
Given I shutdown Tails and wait for the computer to power off 2.555
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.197
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 7.615
And the file system changes introduced in version 6.3~testoverlayfs are present 0.303
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.095
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.154
When the network is plugged 0.034
And Tor is ready 11.911
Then the Upgrader considers the system as up-to-date 2:0.000
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1421:in `/^the Upgrader considers the system as up-to-date$/'
features/usb_upgrade.feature:120:in `Then the Upgrader considers the system as up-to-date'
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:339 4.690 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:47:02)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:47:02_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:47:02_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:47:02_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/01:47:02_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.009
Feature: Getting a DHCP lease without leaking too much information
5:21.995
Background
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given I have started Tails from DVD without network and logged in 6.121
And I capture all network traffic 0.004
And the network is plugged 0.050
And Tor is ready 9.349
And all notifications have disappeared 6.469
And available upgrades have been checked 5:0.000
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:764:in `/^available upgrades have been checked$/'
features/dhcp.feature:14:in `And available upgrades have been checked'
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
0.000
Scenario Getting a DHCP lease with a manually configured NetworkManager connection
Steps
When I add a wired DHCP NetworkManager connection called "manually-added-con" 0.000
And I switch to the "manually-added-con" NetworkManager connection 0.000
Then the hostname should not have been leaked on the network 0.000
After features/support/hooks.rb:339 4.886 
SCENARIO FAILED: 'Getting a DHCP lease with a manually configured NetworkManager connection' (at time 02:01:20)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/02:01:20_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/02:01:20_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/02:01:20_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/02:01:20_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.journal
After features/support/hooks.rb:108 0.048
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
5:17.034
Scenario Using a persistent Pidgin configuration
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Before features/support/hooks.rb:527 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.278
And the network is plugged 0.032
And Tor is ready 8.723
And available upgrades have been checked 5:0.000
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:764:in `/^available upgrades have been checked$/'
features/pidgin.feature:33:in `And available upgrades have been checked'
And all notifications have disappeared 0.000
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 0.000
Then I see Pidgin's account manager window 0.000
When I create my XMPP account 0.000
And I close Pidgin's account manager window 0.000
Then Pidgin automatically enables my XMPP account 0.000
When I close Pidgin 0.000
And I take note of the configured Pidgin accounts 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Given a computer 0.000
And I start Tails from USB drive "__internal" and I login with persistence enabled 0.000
And Pidgin has the expected persistent accounts configured 0.000
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 0.000
Then Pidgin automatically enables my XMPP account 0.000
After features/support/hooks.rb:535 0.030
After features/support/hooks.rb:339 4.827 
SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 03:30:19)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/03:30:19_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/03:30:19_Using_a_persistent_Pidgin_configuration.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/03:30:19_Using_a_persistent_Pidgin_configuration.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/03:30:19_Using_a_persistent_Pidgin_configuration.journal
After features/support/hooks.rb:108 0.005
Feature: Thunderbird email client
Tags: @product @check_tor_leaks
1:59.321
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 7.957
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.136
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.118
When I accept the autoconfiguration wizard's configuration 1:51.109
The 
The Dogtail init script raised: SearchError: descendant of [frame | Account Setup - Mozilla Thunderbird]: 'Get Messages' button
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:272:in `button'
./features/step_definitions/thunderbird.rb:128:in `/^I fetch my email$/'
./features/step_definitions/thunderbird.rb:160:in `/^I accept the (?:autoconfiguration wizard's|manual) configuration$/'
features/thunderbird.feature:24:in `When I accept the autoconfiguration wizard's configuration'
And I send an email to myself 0.000
And I fetch my email 0.000
Then I can find the email I sent to myself in my inbox 0.000
And the system only established connections with my email server 0.000
After features/support/hooks.rb:535 0.048
After features/support/hooks.rb:339 5.136 
SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 03:40:28)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/03:40:28_I_can_send_emails,_and_receive_emails_over_IMAP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/03:40:28_I_can_send_emails,_and_receive_emails_over_IMAP.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/03:40:28_I_can_send_emails,_and_receive_emails_over_IMAP.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/03:40:28_I_can_send_emails,_and_receive_emails_over_IMAP.journal
After features/support/hooks.rb:108 0.009
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
32.536
Scenario Downloading files with the Tor Browser
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Before features/support/hooks.rb:527 0.002
Steps
Given I have started Tails from DVD and logged in and the network is connected 8.233
When I start the Tor Browser 5.637
When I download some file in the Tor Browser to the Downloads directory 18.665
The 
The Dogtail init script raised: SearchError: descendant of [application | Firefox]: child with name='Opening tails-signing.key'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/browser.rb:356:in `/^I download some file in the Tor Browser to the (.*) directory$/'
features/torified_browsing.feature:29:in `When I download some file in the Tor Browser to the Downloads directory'
Then the file is saved to the Downloads directory 0.000
After features/support/hooks.rb:535 0.076
After features/support/hooks.rb:339 5.065 
SCENARIO FAILED: 'Downloading files with the Tor Browser' (at time 03:59:26)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/03:59:26_Downloading_files_with_the_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/03:59:26_Downloading_files_with_the_Tor_Browser.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/03:59:26_Downloading_files_with_the_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/03:59:26_Downloading_files_with_the_Tor_Browser.journal
After features/support/hooks.rb:108 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
5:16.043
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.824
And the network is plugged 0.026
And I successfully configure Tor 8.190
And available upgrades have been checked 5:0.001
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:764:in `/^available upgrades have been checked$/'
features/torified_browsing.feature:105:in `And available upgrades have been checked'
And all notifications have disappeared 0.000
And there is a GNOME bookmark for the Persistent directory 0.000
When I start the Tor Browser 0.000
And I download some file in the Tor Browser to the Persistent directory 0.000
Then the file is saved to the Persistent directory 0.000
When I open the address "https://tails.net/about" in the Tor Browser 0.000
Then "Tails - How Tails works" has loaded in the Tor Browser 0.000
And I can print the current page as "output.pdf" to the Persistent directory 0.000
After features/support/hooks.rb:339 4.826 
SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 04:08:32)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/04:08:32_The_Persistent_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/04:08:32_The_Persistent_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/04:08:32_The_Persistent_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/26/artifact/build-artifacts/04:08:32_The_Persistent_directory_is_usable_in_Tor_Browser.journal
After features/support/hooks.rb:108 0.000