Project Number Date
test_Tails_ISO_devel 4635 24 Sep 2026, 15:11

Failures Overview

The following summary displays scenarios that failed.

Feature: Installing and running Flatpak apps in Tails
Tags: @product @check_tor_leaks
5:25.466
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:25.466
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.033
After features/support/hooks.rb:339 5.054 
SCENARIO FAILED: 'Installing, starting and uninstalling a Flatpak' (at time 00:13:26)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/00:13:26_Installing,_starting_and_uninstalling_a_Flatpak.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/00:13:26_Installing,_starting_and_uninstalling_a_Flatpak.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/00:13:26_Installing,_starting_and_uninstalling_a_Flatpak.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/00:13:26_Installing,_starting_and_uninstalling_a_Flatpak.journal
After features/support/hooks.rb:108 0.005
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:11.948
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 9.805
Then I wait until Tor is ready 2.136
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: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.647 
SCENARIO FAILED: 'Using normal bridges' (at time 00:33:59)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/00:33:59_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/00:33:59_Using_normal_bridges.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/00:33:59_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/00:33:59_Using_normal_bridges.journal
After features/support/hooks.rb:108 0.072
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:11.952
Scenario Asking for mocked bridge settings with automatic region-detection in Tor Connection
Steps
Given the Moat distributor responds with the default bridges 0.108
When I configure Tor Connection to ask for bridge settings based on my location 5.844
And I wait until Tor is ready 5.998
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:105:in `And available upgrades have been checked'
Then Tor is configured to use the default bridges 0.000
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000
After features/support/hooks.rb:339 4.825 
SCENARIO FAILED: 'Asking for mocked bridge settings with automatic region-detection in Tor Connection' (at time 00:44:38)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/00:44:38_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/00:44:38_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/00:44:38_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/00:44:38_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.journal
After features/support/hooks.rb:108 0.049
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
7:54.144
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.012
Before features/support/hooks.rb:527 0.003
Steps
Given a computer 0.100
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:20.594
And I configure APT to prefer an old version of cowsay 0.010
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 8.108
And I accept adding "cowsay" to Additional Software 5.444
And Additional Software is correctly configured for package "cowsay" 0.655
And I shutdown Tails and wait for the computer to power off 3.896
And I start Tails from USB drive "__internal" with network unplugged 33.311
And I enable persistence 11.823
# 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.050
And I log in to a new session 7.412
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been installed 10.162
And I revert the APT tweaks that made it prefer an old version of cowsay 0.037
# 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.035
And the network is plugged 0.034
And Tor is ready 12.456
And available upgrades have been checked 5:0.005
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/additional_software_packages.feature:101:in `And available upgrades have been checked'
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.041
After features/support/hooks.rb:339 5.263 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:25:46)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/01:25:46_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_devel/4635/artifact/build-artifacts/01:25:46_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_devel/4635/artifact/build-artifacts/01:25:46_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_devel/4635/artifact/build-artifacts/01:25:46_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_devel/4635/artifact/build-artifacts/01:25:46_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_devel/4635/artifact/build-artifacts/01:25:46_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_devel/4635/artifact/build-artifacts/01:25:46_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_devel/4635/artifact/build-artifacts/01:25:46_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_devel/4635/artifact/build-artifacts/01:25:46_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.014
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
7:47.368
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 9.029
And the network is plugged 0.069
And Tor is ready 11.817
And available upgrades have been checked 0.042
And all notifications have disappeared 8.294
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 10.174
Then I see Pidgin's account manager window 1.080
When I create my XMPP account 12.248
And I close Pidgin's account manager window 0.487
Then Pidgin automatically enables my XMPP account 18.001
When I close Pidgin 15.910
And I take note of the configured Pidgin accounts 0.008
And I shutdown Tails and wait for the computer to power off 5.196
Given a computer 0.107
And I start Tails from USB drive "__internal" and I login with persistence enabled 6:14.900
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/pidgin.feature:44:in `And I start Tails from USB drive "__internal" and I login with persistence enabled'
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.038
After features/support/hooks.rb:339 5.080 
SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 03:28:18)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/03:28:18_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/03:28:18_Using_a_persistent_Pidgin_configuration.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/03:28:18_Using_a_persistent_Pidgin_configuration.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/03:28:18_Using_a_persistent_Pidgin_configuration.journal
After features/support/hooks.rb:108 0.012
Feature: Thunderbird email client
6:10.553
Background
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Before features/support/hooks.rb:527 0.002
Steps
Given I have started Tails from DVD and logged in with an administration password and the network is connected 6:10.553
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.039
After features/support/hooks.rb:339 4.813 
SCENARIO FAILED: 'No add-ons are installed' (at time 03:40:43)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/03:40:43_No_add-ons_are_installed.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/03:40:43_No_add-ons_are_installed.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/03:40:43_No_add-ons_are_installed.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/03:40:43_No_add-ons_are_installed.journal
After features/support/hooks.rb:108 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
5:18.400
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.538
And the network is plugged 0.031
And I successfully configure Tor 9.830
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/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 5.081 
SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 04:11:02)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/04:11:02_The_Persistent_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/04:11:02_The_Persistent_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/04:11:02_The_Persistent_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4635/artifact/build-artifacts/04:11:02_The_Persistent_directory_is_usable_in_Tor_Browser.journal
After features/support/hooks.rb:108 0.000