Project Number Date
test_Tails_ISO_web-release-7.14 5 29 Sep 2026, 22:09

Failures Overview

The following summary displays scenarios that failed.

3:18.716
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.004
Steps
Given a computer 0.101
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:19.050
And I configure APT to prefer an old version of cowsay 0.021
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 5.516
And I accept adding "cowsay" to Additional Software 5.003
And Additional Software is correctly configured for package "cowsay" 0.621
And I shutdown Tails and wait for the computer to power off 2.604
And I start Tails from USB drive "__internal" with network unplugged 34.583
And I enable persistence 12.012
# 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.006
# 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.055
And I log in to a new session 8.141
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been installed 10.375
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.048
And the network is plugged 0.026
And Tor is ready 12.705
And available upgrades have been checked 0.037
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.293
And I can open the Additional Software configuration window from the notification 26.473
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.055
After features/support/hooks.rb:339 5.787

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

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_web-release-7.14/5/artifact/build-artifacts/01:05:42_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_web-release-7.14/5/artifact/build-artifacts/01:05:42_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_web-release-7.14/5/artifact/build-artifacts/01:05:42_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_web-release-7.14/5/artifact/build-artifacts/01:05:42_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_web-release-7.14/5/artifact/build-artifacts/01:05:42_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_web-release-7.14/5/artifact/build-artifacts/01:05:42_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_web-release-7.14/5/artifact/build-artifacts/01:05:42_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_web-release-7.14/5/artifact/build-artifacts/01:05:42_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_web-release-7.14/5/artifact/build-artifacts/01:05:42_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.030
Feature: Localization
Tags: @product
27.504
Scenario Tails stores localization preferences when it's asked to
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 stopped at Tails Greeter's login screen 8.051
When I set the language to Italian (it) 4.604
And I save the language and keyboard options in cleartext storage 14.847
The
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with name='Question' roleName='alert'
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/common_steps.rb:511:in `/^I save the language and keyboard options in cleartext storage$/'
features/localization.feature:71:in `And I save the language and keyboard options in cleartext storage'
Then the "it" language and keyboard have been saved in cleartext storage 0.000
When I set the language to French (fr) 0.000
Then the "fr" 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
And I start Tails from USB drive "__internal" with network unplugged 0.000
Then the "fr" language and keyboard have been saved in cleartext storage 0.000
And the Welcome Screen's language is set to French 0.000
When I log in to a new session 0.000
Then the language is set to French 0.000
After features/support/hooks.rb:339 4.977

SCENARIO FAILED: 'Tails stores localization preferences when it's asked to' (at time 02:12:34)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_web-release-7.14/5/artifact/build-artifacts/02:12:34_Tails_stores_localization_preferences_when_it_s_asked_to.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_web-release-7.14/5/artifact/build-artifacts/02:12:34_Tails_stores_localization_preferences_when_it_s_asked_to.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_web-release-7.14/5/artifact/build-artifacts/02:12:34_Tails_stores_localization_preferences_when_it_s_asked_to.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_web-release-7.14/5/artifact/build-artifacts/02:12:34_Tails_stores_localization_preferences_when_it_s_asked_to.journal

After features/support/hooks.rb:108 0.000
1:23.779
Scenario The Tor Browser's "New identity" feature works as expected
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Before features/support/hooks.rb:527 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 9.372
When I start the Tor Browser 7.602
When I open the address "https://example.com/" in the Tor Browser 6.804
Then Tor Browser displays a "Example Domain" heading on the "Example Domain" page 1: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/browser.rb:390:in `/^Tor Browser displays a "([^"]+)" heading on the "([^"]+)" page$/'
features/torified_browsing.feature:77:in `Then Tor Browser displays a "Example Domain" heading on the "Example Domain" page'
And the Tor Browser has 2 tabs open 0.000
When I request a new identity in Tor Browser 0.000
Then the Tor Browser loads about:tor 0.000
And the Tor Browser has 1 tab open 0.000
After features/support/hooks.rb:535 0.041
After features/support/hooks.rb:339 5.222

SCENARIO FAILED: 'The Tor Browser's "New identity" feature works as expected' (at time 03:08:12)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_web-release-7.14/5/artifact/build-artifacts/03:08:12_The_Tor_Browser_s__New_identity__feature_works_as_expected.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_web-release-7.14/5/artifact/build-artifacts/03:08:12_The_Tor_Browser_s__New_identity__feature_works_as_expected.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_web-release-7.14/5/artifact/build-artifacts/03:08:12_The_Tor_Browser_s__New_identity__feature_works_as_expected.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_web-release-7.14/5/artifact/build-artifacts/03:08:12_The_Tor_Browser_s__New_identity__feature_works_as_expected.journal

After features/support/hooks.rb:108 0.000