Project Number Date
test_Tails_ISO_test-suite-trixie-2 17 14 Jun 2025, 12:14

Failures Overview

The following summary displays scenarios that failed.

Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
15.755
Scenario Erasure of memory freed by killed userspace processes
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.506
And I prepare Tails for memory erasure tests 0.717
When I start a process allocating 128 MiB of memory with a known pattern 2.413
Then patterns cover at least 128 MiB in the guest's memory 4.118
99.610% 
99.610% of the expected size (128 MiB) has the pattern, but more than 100.000% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:186:in `/^patterns cover at least (\d+) MiB in the guest's memory$/'
features/erase_memory.feature:17:in `Then patterns cover at least 128 MiB in the guest's memory'
Output 1 
Pattern coverage: 99.610% (127 MiB out of 128 MiB reference memory)
When I kill the allocating process 0.000
Then I find very few patterns in the guest's memory after 5 seconds 0.000
After features/support/hooks.rb:330 5.194 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:39:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/00:39:30_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/00:39:30_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/00:39:30_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/00:39:30_Erasure_of_memory_freed_by_killed_userspace_processes.journal
After features/support/hooks.rb:100 0.000
Feature: Additional software
Tags: @product @check_tor_leaks @slow
11:49.451
Scenario I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:507 0.011
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:30.591
And I update APT using apt 12.737
And I install "popularity-contest" using apt 26.132
Then I am proposed to add the "popularity-contest" package to my Additional Software 11.672
When I create a persistent storage and activate the Additional Software feature 24.785
Then Additional Software is correctly configured for package "popularity-contest" 2.977
When I shutdown Tails and wait for the computer to power off 14.707
And I start Tails from USB drive "__internal" with network unplugged 1:50.836
And I enable persistence 31.111
And I log in to a new session 55.737
And the Additional Software installation service has started 24.648
Then I am notified that the installation succeeded 5:3.512
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:631:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
./features/step_definitions/additional_software_packages.rb:28:in `/^I am notified that the installation succeeded$/'
features/additional_software_packages.feature:39:in `Then I am notified that the installation succeeded'
And Additional Software is correctly configured for package "popularity-contest" 0.000
And the package "popularity-contest" is installed after Additional Software has been started 0.000
After features/support/hooks.rb:515 0.043
After features/support/hooks.rb:330 10.332 
SCENARIO FAILED: 'I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails' (at time 01:32:15)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/01:32:15_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/01:32:15_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/01:32:15_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.journal
After features/support/hooks.rb:100 0.009
Feature: Additional software
Tags: @product @check_tor_leaks @slow
25:23.749
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Before features/support/hooks.rb:507 0.002
Steps
Given a computer 0.159
And I start Tails from USB drive "__internal" and I login with an administration password 3:2.854
And I update APT using apt 14.372
When I install "makepp" using apt 22:6.363
Tor 
Tor operation failed (despite retrying 10 times) with
Timeout::Error: try_for() timeout expired
Last ignored exception was: ExecutionFailedInVM: Command failed: dpkg -s 'makepp' 2>/dev/null | grep -qs '^Status:.*installed$'
error code: 1
stdout: 
stderr: .
<false> is not true.
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/apt.rb:69:in `block in wait_for_package_installation'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/apt.rb:68:in `wait_for_package_installation'
./features/step_definitions/apt.rb:86:in `block (3 levels) in <top (required)>'
./features/step_definitions/apt.rb:82:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:211:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:81:in `block in <top (required)>' (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:81:in `/^I install "(.+)" using apt$/'
features/additional_software_packages.feature:48:in `When I install "makepp" using apt'
Then the Additional Software dpkg hook has been run for package "makepp" and notices the persistence is locked 0.000
And the package "makepp" is installed 0.000
After features/support/hooks.rb:515 0.055
After features/support/hooks.rb:330 5.268 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:57:49)
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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/01:57:49_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/01:57:49_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/01:57:49_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/01:57:49_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/01:57:49_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/01:57:49_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/01:57:49_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/01:57:49_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.011
Feature: Additional software
Tags: @product @check_tor_leaks @slow
10:13.517
Scenario My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:507 0.003
Steps
Given a computer 0.176
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 4:27.746
When I uninstall "popularity-contest" using apt 25.083
And I accept removing "popularity-contest" from Additional Software 2.777
Then "popularity-contest" is not in the list of Additional Software 0.811
When I start Synaptic 17.147
And I update APT using Synaptic 21.883
And I install "cowsay" using Synaptic 4:37.892
Tor 
Tor operation failed (despite retrying 10 times) with
Dogtail::Failure: The Dogtail init script raised: SearchError: child of [application | synaptic]: 'Find' dialog
STDOUT:

STDERR:

 (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:180:in `/^I install "(.+)" using Synaptic$/'
features/additional_software_packages.feature:61:in `And I install "cowsay" using Synaptic'
And I accept adding "cowsay" to Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I uninstall "cowsay" using apt 0.000
And I refuse removing "cowsay" from Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I remove "cowsay" from the list of Additional Software using Additional Software GUI 0.000
Then "cowsay" is not in the list of Additional Software 0.000
When I install "cowsay" using apt 0.000
And I refuse adding "cowsay" to Additional Software 0.000
Then "cowsay" is not in the list of Additional Software 0.000
After features/support/hooks.rb:515 0.035
After features/support/hooks.rb:330 5.873 
SCENARIO FAILED: 'My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic' (at time 02:08:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:08:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:08:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:08:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:08:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:08:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:08:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:08:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:08:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:08:08_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.journal
After features/support/hooks.rb:100 0.006
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
5:23.889
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:507 0.003
Steps
Given a computer 0.211
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 5:23.678
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:597:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:538:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
./features/step_definitions/common_steps.rb:287: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 started 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 started 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:515 0.037
After features/support/hooks.rb:330 6.737 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 02:13:38)
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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:13:38_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:13:38_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:13:38_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:13:38_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:13:38_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:13:38_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:13:38_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:13:38_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal
After features/support/hooks.rb:100 0.036
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
2:8.185
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Before features/support/hooks.rb:507 0.008
Steps
Given a computer 0.191
And I start Tails from USB drive "__internal" with network unplugged 1:51.141
And I enable persistence 16.805
And I remove the "cowsay" deb files from the APT cache 0.046
Command 
Command failed: rm /live/persistence/TailsData_unlocked/apt/cache/cowsay_*.deb
error code: 1
stdout: 
stderr: rm: cannot remove '/live/persistence/TailsData_unlocked/apt/cache/cowsay_*.deb': No such file or directory
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/additional_software_packages.rb:134:in `/^I remove the "([^"]*)" deb files from the APT cache$/'
features/additional_software_packages.feature:124:in `And I remove the "cowsay" deb files from the APT cache'
# 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
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 0.000
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:515 0.043
After features/support/hooks.rb:330 5.482 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 02:15:53)
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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:15:53_I_am_notified_when_Additional_Software_fails_to_install_a_package.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:15:53_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:15:53_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:15:53_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:15:53_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:15:53_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:15:53_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:15:53_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.006
Feature: Upgrading an old Tails USB installation
Tags: @product
3:32.537
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given a computer 0.159
And I create a 7200 MiB disk named "old" 0.068
And I plug USB drive "old" 1.154
And I write an old version of the Tails USB image to disk "old" 32.733
When I start Tails from USB drive "old" with network unplugged 2:58.421
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:427:in `wait_for_ponytail'
./features/step_definitions/common_steps.rb:481:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276: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/usb_upgrade.feature:25:in `When I start Tails from USB drive "old" with network unplugged'
Then the boot device has safe access rights 0.000
And Tails is running from USB drive "old" 0.000
And there is no persistence partition on USB drive "old" 0.000
And process "udev-watchdog" is running 0.000
And udev-watchdog is monitoring the correct device 0.000
And I unplug USB drive "old" 0.000
After features/support/hooks.rb:330 5.902 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:19:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:19:31_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:19:31_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:19:31_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:19:31_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.006
Feature: Upgrading an old Tails USB installation
Tags: @product
2:34.298
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 2:34.101
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:427:in `wait_for_ponytail'
./features/step_definitions/common_steps.rb:481:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276: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/usb_upgrade.feature:36:in `And I start Tails from USB drive "old" with network unplugged and I login'
Then Tails is running from USB drive "old" 0.000
And I create a persistent partition 0.000
And I take note of which tps features are available 0.000
Then a Tails persistence partition exists on USB drive "old" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
After features/support/hooks.rb:330 5.797 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:22:11)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:22:11_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:22:11_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:22:11_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:22:11_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product
2:30.322
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.155
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.166
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:427:in `wait_for_ponytail'
./features/step_definitions/common_steps.rb:481:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276: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/usb_upgrade.feature:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:330 5.714 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:24:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:24:47_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:24:47_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:24:47_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:24:47_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.005
Feature: Upgrading an old Tails USB installation
Tags: @product
2:13.718
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.526
The 
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with roleName='password text'
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/usb.rb:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:283: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/usb_upgrade.feature:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:330 5.894 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:30:01)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:30:01_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:30:01_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:30:01_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:30:01_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.006
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
23:0.864
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.318
And no SquashFS delta is installed 0.155
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.348
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.585
When the network is plugged 0.078
And Tor is ready 28.447
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:13.542
Tor 
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderUpgradeTo6.2~testoverlayfs.png", "TailsUpgraderFailure.png"] on the screen (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/usb.rb:1301:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:90:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# 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.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# 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:330 5.454 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:53:07)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:53:07_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:53:07_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:53:07_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/02:53:07_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
22:50.097
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.441
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.102
But a current signing key is available on our website 0.000
When the network is plugged 0.136
And Tor is ready 25.354
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:12.660
Tor 
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderUpgradeTo6.2~testoverlayfs.png", "TailsUpgraderFailure.png"] on the screen (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/usb.rb:1301:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:134:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
After features/support/hooks.rb:330 5.977 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:16:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/03:16:03_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/03:16:03_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/03:16:03_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/03:16:03_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000
Feature: Emergency shutdown
Tags: @product @not_release_blocker
36.528
Scenario Tails erases memory and shuts down on USB boot medium removal: persistent data
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.805
And I prepare Tails for memory erasure tests 0.606
And I fill a 128 MiB file with a known pattern on the persistent filesystem 20.162
And patterns cover at least 100 MiB in the guest's memory 4.954
95.012% 
95.012% of the expected size (100 MiB) has the pattern, but more than 100.000% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:186:in `/^patterns cover at least (\d+) MiB in the guest's memory$/'
features/emergency_shutdown.feature:51:in `And patterns cover at least 100 MiB in the guest's memory'
Output 1 
Pattern coverage: 95.012% (95 MiB out of 100 MiB reference memory)
When I eject the boot medium 0.000
And I wait for Tails to finish wiping the memory 0.000
Then I find very few patterns in the guest's memory 0.000
And Tails eventually shuts down 0.000
After features/support/hooks.rb:330 5.752 
SCENARIO FAILED: 'Tails erases memory and shuts down on USB boot medium removal: persistent data' (at time 03:21:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/03:21:18_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/03:21:18_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/03:21:18_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/03:21:18_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.journal
After features/support/hooks.rb:100 0.000
Feature: Tails documentation
Tags: @product @doc @not_release_blocker
1:1.103
Scenario The Tails documentation launcher works when offline
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD without network and logged in 11.804
When I start "Tails Documentation" via GNOME Activities Overview 10.746
Then the Tor Browser has started 38.552
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:495:in `/^the Tor Browser (?:has started|starts)$/'
features/documentation.feature:7:in `Then the Tor Browser has started'
Then "Tails - Documentation" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 12.029 
SCENARIO FAILED: 'The Tails documentation launcher works when offline' (at time 03:27:58)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/03:27:58_The_Tails_documentation_launcher_works_when_offline.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/03:27:58_The_Tails_documentation_launcher_works_when_offline.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/03:27:58_The_Tails_documentation_launcher_works_when_offline.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product
3:5.893
Scenario Outline Disk partitioning errors without a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.025
Steps
Given a computer 0.484
And I set Tails to boot with options "test_partitioning_errors=fs_resize" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.084
And I plug USB drive "temp" 1.051
And I write the Tails USB image to disk "temp" 37.636
When I start Tails from USB drive "temp" with network unplugged 2:26.637
cannot 
cannot find TailsGreeter.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:477:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276: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/hardware_failure.feature:82:in `When I start Tails from USB drive "temp" with network unplugged'
features/hardware_failure.feature:72:in `When I start Tails from USB drive "temp" with network unplugged'
Then Tails is running from USB drive "temp" 0.000
And the Greeter recommends reinstalling Tails due to partitioning errors 0.000
And the Greeter forbids starting Tails 0.000
And the Greeter forbids all settings but language 0.000
And Tails detected partitioning error fs-not-resized 0.000
After features/support/hooks.rb:330 8.253 
SCENARIO FAILED: 'Disk partitioning errors without a persistent partition, Examples (#3)' (at time 04:05:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/04:05:12_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/04:05:12_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/04:05:12_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/04:05:12_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.journal
After features/support/hooks.rb:100 0.522
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
14.705
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Steps
Given I have started Tails from DVD without network and logged in 9.067
Then the keys trusted by APT are valid for the next 3 months 5.637
The 
The following APT key(s) will not be valid in 3 months: D051FE3A848DCABD4625787A6FFA8EF91DB114E0, 4C7A8E5E9454FE3FAE1E78ADF1D53D8C4F368D5D, C20CA1D9499DECBBD8BDACF9E415B2B4B5F5BBED, 4E6CBA363A3A3708DC533C75B7A50B4134FC6FE5, 084750FC01A6D388A643D869010908312D230C5F, A99951DAF9BB569BDB50AD90A70DAF536070D3A1, 6039406A4EDCE124CF087B0AEC61E0B0BBE55AB3, 0F8A1F54CB8BF69B34DB847F0A3B614236CA98F3, 150C8614919D8446E01E83AF9AA38DCD55BE302B, 7F5A44454C724A65CBCD4FB14D270D06F42584E6, F6CFDE3061333CE2A43FDAF0DFD993306D849617, 0E4EDE2C7F3E1FC0D033800E64481591B98321F9, 9FED2BCBDCD29CDF762678CBAED4B06F473041FA, A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553, ED6D65271AACF0FF15D123036FB2A1C265FFB764, 75DDC3C4A499F1A18CB5F3C8CBF8D6FD518E17E1, 126C0D24BD8A2942CC7DF8AC7638D0442B90D010, D21169141CECD440F2EB8DDA9D6D8F6BC857C906, 067E3C456BAE240ACEE88F6FEF0F382A1A7B6500, E1CF20DDFFE4B89E802658F1E0B11894F66AEC98, 16E90B3FDF65EDE3AA7F323C04EE7237B7D453EC, 6ED6F5CB5FA6FB2F460AE88EEDA0D2388AE22BA9, 379483D8B60160B155B372DDAA8E81B4331F7F50.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:40:in `assert_all_keys_are_valid_for_n_months'
./features/step_definitions/checks.rb:8:in `/^the keys trusted by APT are valid for the next (\d+) months$/'
features/keys.feature:11:in `Then the keys trusted by APT are valid for the next 3 months'
After features/support/hooks.rb:330 5.205 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 04:07:22)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/04:07:22_The_included_APT_repository_keys_are_up-to-date.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/04:07:22_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/04:07:22_The_included_APT_repository_keys_are_up-to-date.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/04:07:22_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
7:22.003
Scenario Persistent Greeter options
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 38.720
When I enable persistence 1:14.672
Then no persistent Greeter options were restored 17.700
When I set all Greeter options to non-default values 53.070
And I log in to a new session in German (de) after having activated the Persistent Storage 1:3.796
Then all Greeter options are set to non-default values 0.315
When I cold reboot the computer 14.452
And the computer reboots Tails 2:15.805
Given I enable persistence 25.072
Then persistent Greeter options were restored 0.703
When I log in to a new session after having activated the Persistent Storage 17.693
The 
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with name='Start Tails' roleName='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:276:in `child'
./features/step_definitions/common_steps.rb:513:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/persistence.feature:113:in `When I log in to a new session after having activated the Persistent Storage'
Then all Greeter options are set to non-default values 0.000
After features/support/hooks.rb:330 7.234 
SCENARIO FAILED: 'Persistent Greeter options' (at time 05:49:11)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/05:49:11_Persistent_Greeter_options.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/05:49:11_Persistent_Greeter_options.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/05:49:11_Persistent_Greeter_options.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/05:49:11_Persistent_Greeter_options.journal
After features/support/hooks.rb:100 0.006
Feature: Tails persistence
Tags: @product @doc
4:5.648
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.880
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.112
When I try to enable persistence 0.290
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 46.259
When I repair the filesystem of the Persistent Storage 3.658
Then the Welcome Screen tells me that it failed to repair the Persistent Storage 0.076
When I log in to a new session 3:5.370
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:597:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:538:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/persistence.feature:191:in `When I log in to a new session'
And all notifications have disappeared 0.000
# Now both WhisperBack and Tor Browser has started at the same
# time, so we do not know which window is focused. The steps about
# Tor Browser care about that, but the ones about WhisperBack do
# not, so we first deal with WhisperBack and then kill it to
# ensure that Tor Browser is focused.
Then WhisperBack is prefilled for fsck with summary: "Failed to repair the file system of your Persistent Storage" 0.000
And the file "/var/lib/gdm3/post-greeter-whisperback.json" is empty 0.000
When I close the "whisperback" window 0.000
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 9.115 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 06:16:28)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/06:16:28_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/06:16:28_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/06:16:28_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
2:46.004
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.823
And the network is plugged 0.100
And I successfully configure Tor 29.861
And available upgrades have been checked 1.151
And all notifications have disappeared 5.461
And there is a GNOME bookmark for the Persistent directory 28.742
When I start the Tor Browser 27.978
And I download some file in the Tor Browser to the Persistent directory 59.884
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:8:in `new'
./features/step_definitions/browser.rb:8:in `block in desktop_portal_save_as'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/browser.rb:7:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:326:in `block in <top (required)>' (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:7:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:326:in `/^I download some file in the Tor Browser to the (.*) directory$/'
features/torified_browsing.feature:113: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:330 9.471 
SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 07:10:31)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/07:10:31_The_Persistent_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/07:10:31_The_Persistent_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/07:10:31_The_Persistent_directory_is_usable_in_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
30.716
Scenario Persistent browser bookmarks
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.027
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.172
And all tps features are active 3.270
And all persistent filesystems have safe access rights 0.423
And all persistence configuration files have safe access rights 0.570
And all persistent directories have safe access rights 4.221
When I start the Tor Browser in offline mode 11.056
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'zenity' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:475:in `new'
./features/step_definitions/browser.rb:475:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:139:in `When I start the Tor Browser in offline mode'
And I add a bookmark to eff.org in the Tor Browser 0.000
And I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I log in to a new session 0.000
And all notifications have disappeared 0.000
And I start the Tor Browser in offline mode 0.000
Then the Tor Browser has a bookmark to eff.org 0.000
After features/support/hooks.rb:330 7.154 
SCENARIO FAILED: 'Persistent browser bookmarks' (at time 07:20:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/07:20:17_Persistent_browser_bookmarks.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/07:20:17_Persistent_browser_bookmarks.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/07:20:17_Persistent_browser_bookmarks.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/17/artifact/build-artifacts/07:20:17_Persistent_browser_bookmarks.journal
After features/support/hooks.rb:100 0.000