Project Number Date
test_Tails_ISO_devel 4637 26 Sep 2026, 11:27

Failures Overview

The following summary displays scenarios that failed.

5:24.364
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.002
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:24.364
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.029
After features/support/hooks.rb:339 5.032

SCENARIO FAILED: 'Installing, starting and uninstalling a Flatpak' (at time 00:13:19)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/00:13:19_Installing,_starting_and_uninstalling_a_Flatpak.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/00:13:19_Installing,_starting_and_uninstalling_a_Flatpak.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/00:13:19_Installing,_starting_and_uninstalling_a_Flatpak.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/00:13:19_Installing,_starting_and_uninstalling_a_Flatpak.journal

After features/support/hooks.rb:108 0.004
5:24.947
Scenario Changing locale after installing 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.003
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:24.947
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: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.047
After features/support/hooks.rb:339 4.917

SCENARIO FAILED: 'Changing locale after installing a Flatpak' (at time 00:18:49)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/00:18:49_Changing_locale_after_installing_a_Flatpak.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/00:18:49_Changing_locale_after_installing_a_Flatpak.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/00:18:49_Changing_locale_after_installing_a_Flatpak.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/00:18:49_Changing_locale_after_installing_a_Flatpak.journal

After features/support/hooks.rb:108 0.004
Tags: @product
5:10.575
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 9.708
Then I wait until Tor is ready 0.861
And tca.conf includes the configured bridges 0.004
And available upgrades have been checked 5:0.000
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.758

SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:33:18)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/00:33:18_Using_obfs4_pluggable_transports.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/00:33:18_Using_obfs4_pluggable_transports.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/00:33:18_Using_obfs4_pluggable_transports.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/00:33:18_Using_obfs4_pluggable_transports.journal

After features/support/hooks.rb:108 0.049
Tags: @product
5:11.851
Scenario Asking for mocked bridge settings with automatic region-detection in Tor Connection
Steps
Given the Moat distributor responds with the default bridges 0.135
When I configure Tor Connection to ask for bridge settings based on my location 5.731
And I wait until Tor is ready 5.983
And available upgrades have been checked 5:0.000
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.923

SCENARIO FAILED: 'Asking for mocked bridge settings with automatic region-detection in Tor Connection' (at time 00:44:06)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/00:44:06_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/4637/artifact/build-artifacts/00:44:06_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/00:44:06_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/00:44:06_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.journal

After features/support/hooks.rb:108 0.048
6:6.053
Scenario I am warned I can not use Additional Software when I start Tails from a DVD and 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.002
Steps
Given I have started Tails from DVD and logged in with an administration password and the network is connected 6:6.053
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/additional_software_packages.feature:15: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
When I install "popularity-contest" using apt 0.000
Then I am notified I can not use Additional Software for "popularity-contest" 0.000
And I can open the Additional Software documentation from the notification 0.000
After features/support/hooks.rb:535 0.059
After features/support/hooks.rb:339 5.053

SCENARIO FAILED: 'I am warned I can not use Additional Software when I start Tails from a DVD and install a package' (at time 01:13:48)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/01:13:48_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.file_content_var_log_boot.log

Content of /run/live-additional-software/log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/01:13:48_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_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_devel/4637/artifact/build-artifacts/01:13:48_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/01:13:48_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/01:13:48_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/01:13:48_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.cmd_output_mount

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/01:13:48_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/01:13:48_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/01:13:48_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.journal

After features/support/hooks.rb:108 0.000
6:6.198
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.070
And I start Tails from USB drive "__internal" and I login with an administration password 6:6.128
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.034
After features/support/hooks.rb:339 4.957

SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:23:03)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/01:23:03_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_devel/4637/artifact/build-artifacts/01:23:03_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_devel/4637/artifact/build-artifacts/01:23:03_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_devel/4637/artifact/build-artifacts/01:23:03_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_devel/4637/artifact/build-artifacts/01:23:03_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_devel/4637/artifact/build-artifacts/01:23:03_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_devel/4637/artifact/build-artifacts/01:23:03_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_devel/4637/artifact/build-artifacts/01:23:03_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_devel/4637/artifact/build-artifacts/01:23:03_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal

After features/support/hooks.rb:108 0.005
2:8.014
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.002
Before features/support/hooks.rb:527 0.005
Steps
Given a computer 0.077
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:13.677
And I configure APT to prefer an old version of cowsay 0.007
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 8.458
And I accept adding "cowsay" to Additional Software 4.186
And Additional Software is correctly configured for package "cowsay" 0.493
And I shutdown Tails and wait for the computer to power off 2.559
And I start Tails from USB drive "__internal" with network unplugged 38.555
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/additional_software_packages.feature:85:in `And I start Tails from USB drive "__internal" with network unplugged'
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.054
After features/support/hooks.rb:339 5.067

SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:28:10)

Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/01:28:10_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/01:28:10_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/4637/artifact/build-artifacts/01:28:10_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/4637/artifact/build-artifacts/01:28:10_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/4637/artifact/build-artifacts/01:28:10_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/4637/artifact/build-artifacts/01:28:10_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/4637/artifact/build-artifacts/01:28:10_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/4637/artifact/build-artifacts/01:28:10_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.010
3:30.147
Scenario The Tails documentation launcher works when online
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 and the network is connected 9.531
When I start "Tails Documentation" via GNOME Activities Overview 9.491
Then the Tor Browser has started 11.113
And "Tails - Documentation" has loaded in the Tor Browser 3:0.010
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/browser.rb:263:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:278:in `/^"([^"]+)" has loaded in the Tor Browser$/'
features/documentation.feature:14:in `And "Tails - Documentation" has loaded in the Tor Browser'
After features/support/hooks.rb:339 5.058

SCENARIO FAILED: 'The Tails documentation launcher works when online' (at time 01:55:04)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/01:55:04_The_Tails_documentation_launcher_works_when_online.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/01:55:04_The_Tails_documentation_launcher_works_when_online.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/01:55:04_The_Tails_documentation_launcher_works_when_online.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/01:55:04_The_Tails_documentation_launcher_works_when_online.journal

After features/support/hooks.rb:108 0.000
Tags: @product
1:22.536
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.002
And the network is plugged 0.026
And I successfully configure Tor 9.784
And available upgrades have been checked 9.378
And all notifications have disappeared 3.647
And there is a GNOME bookmark for the Persistent directory 14.826
When I start the Tor Browser 9.133
And I download some file in the Tor Browser to the Persistent directory 27.737
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:109:in `And I download some file in the Tor Browser to the Persistent directory'
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.942

SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 03:52:02)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/03:52: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/4637/artifact/build-artifacts/03:52:02_The_Persistent_directory_is_usable_in_Tor_Browser.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/03:52:02_The_Persistent_directory_is_usable_in_Tor_Browser.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4637/artifact/build-artifacts/03:52:02_The_Persistent_directory_is_usable_in_Tor_Browser.journal

After features/support/hooks.rb:108 0.000