Project Number Date
test_Tails_ISO_21565-flatpak-safe 53 27 Sep 2026, 03:39

Failures Overview

The following summary displays scenarios that failed.

Feature: Installing and running Flatpak apps in Tails
Tags: @product @check_tor_leaks
2:37.521
Scenario GNOME Software does not start until Tor is ready
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Before features/support/hooks.rb:527 0.011
Steps
Given I have started Tails without network with the Flatpak feature from a USB drive with a persistent partition enabled and logged in 2:37.521
Feature 
Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:800:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:795:in `each'
./features/step_definitions/usb.rb:795:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./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\ without\ network\ with\ the\ Flatpak\ feature\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/flatpak.feature:13:in `Given I have started Tails without network with the Flatpak feature from a USB drive with a persistent partition enabled and logged in'
Then process "gnome-software" is not running 0.000
When I try to start GNOME Software 0.000
Then I see an error about GNOME Software requiring Tor to be ready 0.000
And I close the "zenity" window 0.000
And process "gnome-software" is not running 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then process "gnome-software" is running within 10 seconds 0.000
After features/support/hooks.rb:535 0.034
After features/support/hooks.rb:339 4.761 
SCENARIO FAILED: 'GNOME Software does not start until Tor is ready' (at time 00:06:47)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:06:47_GNOME_Software_does_not_start_until_Tor_is_ready.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:06:47_GNOME_Software_does_not_start_until_Tor_is_ready.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:06:47_GNOME_Software_does_not_start_until_Tor_is_ready.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:06:47_GNOME_Software_does_not_start_until_Tor_is_ready.journal
After features/support/hooks.rb:108 0.009
Feature: Installing and running Flatpak apps in Tails
Tags: @product @check_tor_leaks
2:36.777
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 2:36.777
Feature 
Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:800:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:795:in `each'
./features/step_definitions/usb.rb:795:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./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:190: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.989 
SCENARIO FAILED: 'Installing, starting and uninstalling a Flatpak' (at time 00:09:28)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:09:28_Installing,_starting_and_uninstalling_a_Flatpak.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:09:28_Installing,_starting_and_uninstalling_a_Flatpak.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:09:28_Installing,_starting_and_uninstalling_a_Flatpak.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:09:28_Installing,_starting_and_uninstalling_a_Flatpak.journal
After features/support/hooks.rb:108 0.008
Feature: Installing and running Flatpak apps in Tails
Tags: @product @check_tor_leaks
2:46.403
Scenario Changing locale after installing a Flatpak
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.000
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 2:46.403
Feature 
Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:800:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:795:in `each'
./features/step_definitions/usb.rb:795:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./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:190: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:38: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 Thunderbird using GNOME Software 0.000
Then the org.mozilla.thunderbird Flatpak is installed after at most 600 seconds 0.000
And the "de" locale is not present in the org.mozilla.thunderbird.Locale Flatpak extension 0.000
Given I set Tails to boot with options "flatpak" 0.000
When I cold reboot the computer 0.000
Then the computer boots Tails 0.000
When I enable persistence 0.000
And I log in to a new session in German (de) 0.000
Given it has been 3 days since GNOME Software checked for updates 0.000
And GNOME Software thinks it is after 06:00 but before 23:00 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the "de" locale is present in the org.mozilla.thunderbird.Locale Flatpak extension after at most 600 seconds 0.000
After features/support/hooks.rb:535 0.034
After features/support/hooks.rb:339 4.956 
SCENARIO FAILED: 'Changing locale after installing a Flatpak' (at time 00:12:20)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:12:20_Changing_locale_after_installing_a_Flatpak.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:12:20_Changing_locale_after_installing_a_Flatpak.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:12:20_Changing_locale_after_installing_a_Flatpak.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:12:20_Changing_locale_after_installing_a_Flatpak.journal
After features/support/hooks.rb:108 0.008
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:10.464
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 9.634
Then I wait until Tor is ready 0.824
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:24: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.691 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:26:33)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:26:33_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:26:33_Using_obfs4_pluggable_transports.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:26:33_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:26:33_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:108 0.042
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:29.888
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 28.112
Then I wait until Tor is ready 1.771
And tca.conf includes the configured bridges 0.004
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 5.033 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:32:16)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:32:16_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:32:16_Using_obfs4_pluggable_transports_from_a_QR_code.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:32:16_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:32:16_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:108 0.051
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:28.543
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 5.719
And I wait until Tor is ready 0.646
When I disconnect the network through GNOME 10.611
And I connect the network through GNOME 9.265
Then the Tor Connection Assistant autostarts 0.080
And the Tor Connection Assistant connects to Tor 1.370
And I wait until Tor is ready 0.849
And Tor is using the same configuration as before 0.000
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:80: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.838 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:40:00)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:40:00_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:40:00_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:40:00_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/00:40:00_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:108 0.073
Feature: Additional software
Tags: @product @check_tor_leaks @slow
6:1.919
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing 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.069
And I start Tails from USB drive "__internal" and I login with an administration password 6:1.850
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:46:in `And I start Tails from USB drive "__internal" and I login with an administration password'
And I update the APT lists using apt 0.000
When I install "ripgrep" using apt 0.000
Then the Additional Software dpkg hook has been run for package "ripgrep" and notices the persistence is locked 0.000
And the package "ripgrep" is installed 0.000
After features/support/hooks.rb:535 0.029
After features/support/hooks.rb:339 5.072 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:14:18)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/01:14:18_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/01:14:18_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.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_21565-flatpak-safe/53/artifact/build-artifacts/01:14:18_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/01:14:18_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/01:14:18_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/01:14:18_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/01:14:18_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/01:14:18_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/01:14:18_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:108 0.004
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
3:7.976
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.075
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:11.720
And I configure APT to prefer an old version of cowsay 0.006
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 5.036
And I accept adding "cowsay" to Additional Software 3.974
And Additional Software is correctly configured for package "cowsay" 0.433
And I shutdown Tails and wait for the computer to power off 3.954
And I start Tails from USB drive "__internal" with network unplugged 32.323
And I enable persistence 10.555
# 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.005
# 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.075
And I log in to a new session 7.239
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been installed 10.376
And I revert the APT tweaks that made it prefer an old version of cowsay 0.032
# 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.044
And the network is plugged 0.028
And Tor is ready 12.027
And available upgrades have been checked 3.158
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.470
And I can open the Additional Software configuration window from the notification 26.437
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with roleName='notification'
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/additional_software_packages.rb:33:in `click_gnome_shell_notification_button'
./features/step_definitions/additional_software_packages.rb:160:in `/^I can open the Additional Software configuration window from the notification$/'
features/additional_software_packages.feature:103:in `And I can open the Additional Software configuration window from the notification'
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.033
After features/support/hooks.rb:339 5.347 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:20:19)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/01:20:19_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_21565-flatpak-safe/53/artifact/build-artifacts/01:20:19_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_21565-flatpak-safe/53/artifact/build-artifacts/01:20:19_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_21565-flatpak-safe/53/artifact/build-artifacts/01:20:19_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_21565-flatpak-safe/53/artifact/build-artifacts/01:20:19_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_21565-flatpak-safe/53/artifact/build-artifacts/01:20:19_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_21565-flatpak-safe/53/artifact/build-artifacts/01:20:19_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_21565-flatpak-safe/53/artifact/build-artifacts/01:20:19_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_21565-flatpak-safe/53/artifact/build-artifacts/01:20:19_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.026
Feature: Localization
Tags: @product
1:21.089
Scenario Cleartext localization preferences have priority over Persistent Storage
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 without a persistent partition and logged in 8.449
# The first boot simulates a legacy Tails, where locale is only saved in Persistent Storage
Then Tails is running from USB drive "__internal" 0.306
And I create a persistent partition 29.062
And I manually store legacy localization settings in Persistent Storage 0.186
When I shutdown Tails and wait for the computer to power off 5.184
# The second boot verifies that the legacy setting still works
And I start Tails from USB drive "__internal" with network unplugged 37.899
Known 
Known issue #20282: Error starting GDM with your graphics card (RuntimeError)
./features/step_definitions/common_steps.rb:450:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:238: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/localization.feature:90:in `And I start Tails from USB drive "__internal" with network unplugged'
Then the Welcome Screen's language is set to English 0.000
And the Welcome Screen's formats is set to United States 0.000
When I enable persistence 0.000
Then the Welcome Screen's language is set to German 0.000
And the Welcome Screen's formats is set to France 0.000
When I set the language to Italian (it) 0.000
Then the language and keyboard have not been saved in cleartext storage 0.000
When I save the language and keyboard options in cleartext storage 0.000
Then the "it" language and keyboard have been saved in cleartext storage 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# The third boot verifies that cleartext has priority
And I start Tails from USB drive "__internal" with network unplugged 0.000
Then the Welcome Screen's language is set to Italian 0.000
And the Welcome Screen's formats is set to Italy 0.000
When I enable persistence 0.000
# Only formats are loaded from persistence
Then the Welcome Screen's formats is set to France 0.000
And the Welcome Screen's language is set to Italian 0.000
After features/support/hooks.rb:339 4.740 
SCENARIO FAILED: 'Cleartext localization preferences have priority over Persistent Storage' (at time 02:26:14)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/02:26:14_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/02:26:14_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/02:26:14_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/02:26:14_Cleartext_localization_preferences_have_priority_over_Persistent_Storage.journal
After features/support/hooks.rb:108 0.005
Feature: Tails persistence
Tags: @product
6:8.039
Scenario Tails Persistent Storage behave tests
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails from DVD and logged in with an administration password and the network is connected 6:8.039
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\ from\ DVD\ and\ logged\ in\ with\ an\ administration\ password\ and\ the\ network\ is\ connected$/'
features/persistence.feature:7:in `Given I have started Tails from DVD and logged in with an administration password and the network is connected'
And I update the APT lists using apt 0.000
And I install "python3-behave" using apt 0.000
Then the Tails Persistent Storage behave tests pass 0.000
After features/support/hooks.rb:339 4.805 
SCENARIO FAILED: 'Tails Persistent Storage behave tests' (at time 02:37:53)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/02:37:53_Tails_Persistent_Storage_behave_tests.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/02:37:53_Tails_Persistent_Storage_behave_tests.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/02:37:53_Tails_Persistent_Storage_behave_tests.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/02:37:53_Tails_Persistent_Storage_behave_tests.journal
After features/support/hooks.rb:108 0.000
Feature: Thunderbird email client
6:4.856
Background
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.005
Steps
Given I have started Tails from DVD and logged in with an administration password and the network is connected 6:4.856
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\ from\ DVD\ and\ logged\ in\ with\ an\ administration\ password\ and\ the\ network\ is\ connected$/'
features/thunderbird.feature:7:in `Given I have started Tails from DVD and logged in with an administration password and the network is connected'
And I have not configured an email account yet 0.000
And Thunderbird is installed 0.000
When I start Thunderbird 0.000
Then I am prompted to setup an email account 0.000
Feature: Thunderbird email client
Tags: @product @check_tor_leaks
0.000
Scenario No add-ons are installed
Steps
Given I cancel setting up an email account 0.000
When I open Thunderbird's Add-ons Manager 0.000
And I open the Extensions tab 0.000
Then I see that no add-ons are enabled in Thunderbird 0.000
And no unexpected connection has leaked from Thunderbird 0.000
After features/support/hooks.rb:535 0.043
After features/support/hooks.rb:339 4.974 
SCENARIO FAILED: 'No add-ons are installed' (at time 03:14:28)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/03:14:28_No_add-ons_are_installed.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/03:14:28_No_add-ons_are_installed.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/03:14:28_No_add-ons_are_installed.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/03:14:28_No_add-ons_are_installed.journal
After features/support/hooks.rb:108 0.000
Feature: Thunderbird email client
5:23.387
Background
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 from DVD and logged in with an administration password and the network is connected 5:23.387
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\ from\ DVD\ and\ logged\ in\ with\ an\ administration\ password\ and\ the\ network\ is\ connected$/'
features/thunderbird.feature:7:in `Given I have started Tails from DVD and logged in with an administration password and the network is connected'
And I have not configured an email account yet 0.000
And Thunderbird is installed 0.000
When I start Thunderbird 0.000
Then I am prompted to setup an email account 0.000
Feature: Thunderbird email client
Tags: @product @check_tor_leaks
0.000
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 0.000
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.000
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.000
When I accept the autoconfiguration wizard's configuration 0.000
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.028
After features/support/hooks.rb:339 4.960 
SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 03:19:57)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/03:19:57_I_can_send_emails,_and_receive_emails_over_IMAP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/03:19:57_I_can_send_emails,_and_receive_emails_over_IMAP.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/03:19:57_I_can_send_emails,_and_receive_emails_over_IMAP.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/53/artifact/build-artifacts/03:19:57_I_can_send_emails,_and_receive_emails_over_IMAP.journal
After features/support/hooks.rb:108 0.000