Project Number Date
test_Tails_ISO_feature-trixie 38 25 Jun 2025, 08:14

Failures Overview

The following summary displays scenarios that failed.

Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
18.199
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.398
And I prepare Tails for memory erasure tests 1.707
When I start a process allocating 128 MiB of memory with a known pattern 3.500
Then patterns cover at least 128 MiB in the guest's memory 4.593
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.277 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:41:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/00:41:25_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/00:41:25_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/00:41:25_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/00:41:25_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:57.819
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.004
Before features/support/hooks.rb:507 0.004
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:26.966
And I update APT using apt 13.528
And I install "popularity-contest" using apt 24.749
Then I am proposed to add the "popularity-contest" package to my Additional Software 15.094
When I create a persistent storage and activate the Additional Software feature 25.086
Then Additional Software is correctly configured for package "popularity-contest" 3.159
When I shutdown Tails and wait for the computer to power off 15.310
And I start Tails from USB drive "__internal" with network unplugged 1:51.904
And I enable persistence 31.465
And I log in to a new session 52.114
And the Additional Software installation service has started 34.928
Then I am notified that the installation succeeded 5:3.509
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:634: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.064
After features/support/hooks.rb:330 7.857 
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:35:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/01:35:43_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/01:35:43_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.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_feature-trixie/38/artifact/build-artifacts/01:35:43_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/01:35:43_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/01:35:43_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/01:35:43_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/01:35:43_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_feature-trixie/38/artifact/build-artifacts/01:35:43_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_feature-trixie/38/artifact/build-artifacts/01:35:43_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.013
Feature: Additional software
Tags: @product @check_tor_leaks @slow
25:20.097
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.005
Before features/support/hooks.rb:507 0.005
Steps
Given a computer 0.196
And I start Tails from USB drive "__internal" and I login with an administration password 3:3.820
And I update APT using apt 11.077
When I install "makepp" using apt 22:5.002
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.043
After features/support/hooks.rb:330 5.493 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 02:01:11)
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_feature-trixie/38/artifact/build-artifacts/02:01:11_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_feature-trixie/38/artifact/build-artifacts/02:01:11_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_feature-trixie/38/artifact/build-artifacts/02:01:11_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_feature-trixie/38/artifact/build-artifacts/02:01:11_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_feature-trixie/38/artifact/build-artifacts/02:01:11_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_feature-trixie/38/artifact/build-artifacts/02:01:11_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_feature-trixie/38/artifact/build-artifacts/02:01:11_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_feature-trixie/38/artifact/build-artifacts/02:01:11_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.013
Feature: Additional software
Tags: @product @check_tor_leaks @slow
10:34.332
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.005
Before features/support/hooks.rb:507 0.005
Steps
Given a computer 0.180
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 4:49.826
When I uninstall "popularity-contest" using apt 25.065
And I accept removing "popularity-contest" from Additional Software 2.715
Then "popularity-contest" is not in the list of Additional Software 0.703
When I start Synaptic 16.740
And I update APT using Synaptic 22.446
And I install "cowsay" using Synaptic 4:36.653
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.037
After features/support/hooks.rb:330 5.770 
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:11:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/02:11:51_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_feature-trixie/38/artifact/build-artifacts/02:11:51_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_feature-trixie/38/artifact/build-artifacts/02:11:51_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_feature-trixie/38/artifact/build-artifacts/02:11:51_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_feature-trixie/38/artifact/build-artifacts/02:11:51_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_feature-trixie/38/artifact/build-artifacts/02:11:51_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_feature-trixie/38/artifact/build-artifacts/02:11:51_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_feature-trixie/38/artifact/build-artifacts/02:11:51_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_feature-trixie/38/artifact/build-artifacts/02:11:51_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.010
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
22:53.061
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.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.762
And no SquashFS delta is installed 0.440
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.528
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.363
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.486
When the network is plugged 0.103
And Tor is ready 23.891
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:13.435
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.678 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:10:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/03:10:42_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_feature-trixie/38/artifact/build-artifacts/03:10:42_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/03:10:42_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/03:10:42_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:46.299
Scenario Upgrading a Tails whose signing key is outdated
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 enabled and logged in 10.982
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.582
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.285
And the signing key used by the Upgrader is outdated 0.161
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 21.143
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:13.048
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.596 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:33:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/03:33:34_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/03:33:34_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/03:33:34_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/03:33:34_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
35.995
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.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.501
And I prepare Tails for memory erasure tests 0.964
And I fill a 128 MiB file with a known pattern on the persistent filesystem 20.089
And patterns cover at least 100 MiB in the guest's memory 3.440
65.359% 
65.359% 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: 65.359% (65 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.745 
SCENARIO FAILED: 'Tails erases memory and shuts down on USB boot medium removal: persistent data' (at time 03:38:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/03:38:03_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_feature-trixie/38/artifact/build-artifacts/03:38:03_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/03:38:03_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_feature-trixie/38/artifact/build-artifacts/03:38:03_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.journal
After features/support/hooks.rb:100 0.000
Feature: Backing up the persistent storage
Tags: @product
1:10.052
Scenario Using Tails' custom backup tool to backup a newly added file
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.562
# The volume cannot be in use when GuestFs clones it, which we do below
And I shutdown Tails and wait for the computer to power off 10.507
And I clone USB drive "__internal" to a temporary USB drive "backup" 2.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.944
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.027
When I start Tails' custom backup tool 5.451
Then the backup tool displays "Plug in your backup Tails USB stick" 0.279
When I plug USB drive "backup" 4.220
And I give the Persistent Storage on drive "backup" its own UUID 0.186
And I click "Retry" in the backup tool 1.226
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.468
When I click "Back Up" in the backup tool 1.257
And I enter my persistent storage passphrase into the polkit prompt 20.916
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:825:in `deal_with_polkit_prompt'
./features/step_definitions/backup.rb:18:in `/^I enter my persistent storage passphrase into the polkit prompt$/'
features/backup.feature:21:in `And I enter my persistent storage passphrase into the polkit prompt'
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 0.000
# The backup tool ejects the drive, so we have to replug it
When I unplug USB drive "backup" 0.000
And I plug USB drive "backup" 0.000
Then the USB drive "backup" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:330 10.262 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 03:41:09)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/03:41:09_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/03:41:09_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/03:41:09_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.240
Feature: Tails persistence
Tags: @product
5:56.905
Scenario Persistent Greeter options
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 12.259
When I enable persistence 58.076
Then no persistent Greeter options were restored 15.492
When I set all Greeter options to non-default values 49.921
And I log in to a new session in German (de) after having activated the Persistent Storage 52.431
Then all Greeter options are set to non-default values 0.551
When I cold reboot the computer 11.044
And the computer reboots Tails 1:58.451
Given I enable persistence 22.134
Then persistent Greeter options were restored 0.605
When I log in to a new session after having activated the Persistent Storage 15.936
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:516: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.602 
SCENARIO FAILED: 'Persistent Greeter options' (at time 05:50:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/05:50:46_Persistent_Greeter_options.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/05:50:46_Persistent_Greeter_options.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/05:50:46_Persistent_Greeter_options.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/05:50:46_Persistent_Greeter_options.journal
After features/support/hooks.rb:100 0.007
Feature: Tails persistence
Tags: @product
6:53.390
Scenario Changing the Persistent Storage passphrase
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 enabled and logged in 12.396
# Note that if anything fails after the passphrase was changed and
# before it's changed back below, subsequent scenarios might fail
# because the Persistent Storage doesn't have the expected passphrase.
When I change the passphrase of the Persistent Storage 37.031
And I shutdown Tails and wait for the computer to power off 15.125
Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 5:48.837
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:600:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:541: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/persistence.feature:123:in `Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase'
And I change the passphrase of the Persistent Storage back to the original 0.000
After features/support/hooks.rb:330 6.357 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 05:57:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/05:57:47_Changing_the_Persistent_Storage_passphrase.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/05:57:47_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/05:57:47_Changing_the_Persistent_Storage_passphrase.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/05:57:47_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:100 0.009
Feature: Tails persistence
Tags: @product
3:15.397
Scenario Deleting a Tails persistent partition
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 and stopped at Tails Greeter's login screen 13.071
And I log in to a new session without activating the Persistent Storage 3:2.325
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:600:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:541: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:128:in `And I log in to a new session without activating the Persistent Storage'
Then persistence is disabled 0.000
But a Tails persistence partition exists on USB drive "__internal" 0.000
And all notifications have disappeared 0.000
When I delete the persistent partition 0.000
Then there is no persistence partition on USB drive "__internal" 0.000
After features/support/hooks.rb:330 9.254 
SCENARIO FAILED: 'Deleting a Tails persistent partition' (at time 06:01:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/06:01:09_Deleting_a_Tails_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/06:01:09_Deleting_a_Tails_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/06:01:09_Deleting_a_Tails_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/06:01:09_Deleting_a_Tails_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
36.179
Scenario Chatting with some friend over XMPP
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:507 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 16.676
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.107
Then I see Pidgin's account manager window 3.864
When I create my XMPP account 4.531
cannot 
cannot find PidginAddAccountProtocolXMPP.png on the screen (FindFailed)
./features/support/helpers/screen.rb:157:in `find'
./features/support/helpers/screen.rb:367:in `hover'
./features/support/helpers/screen.rb:394:in `click'
./features/step_definitions/pidgin.rb:126:in `/^I create my XMPP account$/'
features/pidgin.feature:21:in `When I create my XMPP account'
And I close Pidgin's account manager window 0.000
Then Pidgin automatically enables my XMPP account 0.000
Given my XMPP friend goes online 0.000
When I start a conversation with my friend 0.000
And I say something to my friend 0.000
Then I receive a response from my friend 0.000
After features/support/hooks.rb:515 0.031
After features/support/hooks.rb:330 5.779 
SCENARIO FAILED: 'Chatting with some friend over XMPP' (at time 06:36:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/06:36:06_Chatting_with_some_friend_over_XMPP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/06:36:06_Chatting_with_some_friend_over_XMPP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/06:36:06_Chatting_with_some_friend_over_XMPP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/06:36:06_Chatting_with_some_friend_over_XMPP.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
3:37.607
Scenario Chatting with some friend over XMPP in a multi-user chat
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:507 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 15.243
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 10.947
Then I see Pidgin's account manager window 3.466
When I create my XMPP account 16.283
And I close Pidgin's account manager window 0.729
Then Pidgin automatically enables my XMPP account 19.723
When I join some empty multi-user chat 41.653
And I clear the multi-user chat's scrollback 18.194
And my XMPP friend goes online and joins the multi-user chat 15.919
Then I can see that my friend joined the multi-user chat 1:15.447
cannot 
cannot find PidginChat2UsersInRoom.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/pidgin.rb:268:in `/^I can see that my friend joined the multi-user chat$/'
features/pidgin.feature:40:in `Then I can see that my friend joined the multi-user chat'
And I say something to my friend in the multi-user chat 0.000
Then I receive a response from my friend in the multi-user chat 0.000
When I say https://gitlab.tails.boum.org/tails to my friend in the multi-user chat 0.000
Then I see the Tails GitLab URL 0.000
When I wait 10 seconds 0.000
And I click on the Tails GitLab URL 0.000
Then the Tor Browser loads the Tails GitLab 0.000
After features/support/hooks.rb:515 0.067
After features/support/hooks.rb:330 5.844 
SCENARIO FAILED: 'Chatting with some friend over XMPP in a multi-user chat' (at time 06:39:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/06:39:50_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/06:39:50_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/06:39:50_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/06:39:50_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.journal
After features/support/hooks.rb:100 0.004
Feature: Using Totem
Tags: @product
1:35.817
Scenario Watching a MP4 video stored on the non-persistent filesystem
Steps
Given I have started Tails from DVD without network and logged in 29.264
And I plug and mount a USB drive containing sample videos 31.118
And I copy the sample videos to "/home/amnesia" as user "amnesia" 0.095
And the file "/home/amnesia/video.mp4" exists 0.086
Given I start monitoring the AppArmor log of "/usr/bin/totem" 0.217
When I open "/home/amnesia/video.mp4" with Totem 5.270
Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 14.128
And AppArmor has not denied "/usr/bin/totem" from opening "/home/amnesia/video.mp4" 1.370
Given I close Totem 0.321
And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.114
And the file "/home/amnesia/.gnupg/video.mp4" exists 0.099
And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.246
When I try to open "/home/amnesia/.gnupg/video.mp4" with Totem 2.611
Then Totem tells me it is not allowed to open this file 10.869
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'totem' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/totem.rb:59:in `new'
./features/step_definitions/totem.rb:59:in `/^Totem tells me it is not allowed to open this file$/'
features/totem.feature:25:in `Then Totem tells me it is not allowed to open this file'
And AppArmor has denied "/usr/bin/totem" from opening "/home/amnesia/.gnupg/video.mp4" 0.000
Given I close Totem 0.000
And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" exists 0.000
And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.000
When I try to open "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" with Totem 0.000
Then Totem tells me it is not allowed to open this file 0.000
And AppArmor has denied "/usr/bin/totem" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" 0.000
Given I close Totem 0.000
And the file "/live/overlay/rw/home/amnesia/.gnupg/video.mp4" exists 0.000
And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.000
When I try to open "/live/overlay/rw/home/amnesia/.gnupg/video.mp4" with Totem 0.000
Then Totem tells me it is not allowed to open this file 0.000
# Due to our AppArmor aliases, /live/overlay will be treated
# as /usr/lib/live/mount/overlay.
And AppArmor has denied "/usr/bin/totem" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" 0.000
Given I close Totem 0.000
And I copy "/home/amnesia/video.mp4" to "/home/amnesia/.purple/otr.private_key" as user "amnesia" 0.000
And the file "/home/amnesia/.purple/otr.private_key" exists 0.000
And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.000
When I try to open "/home/amnesia/.purple/otr.private_key" with Totem 0.000
Then Totem tells me it is not allowed to open this file 0.000
And AppArmor has denied "/usr/bin/totem" from opening "/home/amnesia/.purple/otr.private_key" 0.000
After features/support/hooks.rb:330 8.351 
SCENARIO FAILED: 'Watching a MP4 video stored on the non-persistent filesystem' (at time 08:08:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:08:44_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:08:44_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:08:44_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:08:44_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.journal
After features/support/hooks.rb:100 0.002
Feature: Using Totem
Tags: @product
1:34.713
Scenario Watching MP4 videos stored on the persistent volume should work as expected given our AppArmor confinement
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.428
And I plug and mount a USB drive containing sample videos 34.044
And I copy the sample videos to "/home/amnesia/Persistent" as user "amnesia" 0.284
When I open "/home/amnesia/Persistent/video.mp4" with Totem 8.074
Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 16.435
Given I close Totem 1.295
And I start monitoring the AppArmor log of "/usr/bin/totem" 0.192
And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.104
When I try to open "/home/amnesia/.gnupg/video.mp4" with Totem 2.358
Then Totem tells me it is not allowed to open this file 11.496
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'totem' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/totem.rb:59:in `new'
./features/step_definitions/totem.rb:59:in `/^Totem tells me it is not allowed to open this file$/'
features/totem.feature:64:in `Then Totem tells me it is not allowed to open this file'
And AppArmor has denied "/usr/bin/totem" from opening "/home/amnesia/.gnupg/video.mp4" 0.000
After features/support/hooks.rb:330 6.801 
SCENARIO FAILED: 'Watching MP4 videos stored on the persistent volume should work as expected given our AppArmor confinement' (at time 08:11:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:11:23_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:11:23_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:11:23_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:11:23_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
1:18.155
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD without network and logged in 1:18.155
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/veracrypt.feature:8:in `Given I have started Tails from DVD without network and logged in'
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
0.000
Scenario Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume
Steps
When I plug a USB drive containing a basic VeraCrypt volume 0.000
And I cancel the GNOME authentication prompt 0.000
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 0.000
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt volume 0.000
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 6.826 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume' (at time 08:30:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:30:28_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:30:28_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:30:28_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:30:28_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
1:15.664
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.028
Steps
Given I have started Tails from DVD without network and logged in 1:15.664
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/veracrypt.feature:8:in `Given I have started Tails from DVD without network and logged in'
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
0.000
Scenario Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 0.000
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 0.000
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 7.550 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM' (at time 08:33:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:33:08_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:33:08_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:33:08_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:33:08_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
1:31.637
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.167
Steps
Given I have started Tails from DVD without network and logged in 1:31.637
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/veracrypt.feature:8:in `Given I have started Tails from DVD without network and logged in'
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
0.000
Scenario Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 0.000
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 0.000
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 6.843 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container' (at time 08:34:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:34:47_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:34:47_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:34:47_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:34:47_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
1:8.769
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a keyfile 55.684
And I unlock and mount this VeraCrypt file container with GNOME Disks 13.084
The 
The Dogtail init script raised: ActionNotSupported: Cannot do 'activate' action on [DEAD]
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:346:in `call_tree_node_method'
./features/support/helpers/dogtail.rb:364:in `doActionNamed'
./features/support/helpers/dogtail.rb:378:in `activate'
./features/step_definitions/veracrypt.rb:238:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:68:in `And I unlock and mount this VeraCrypt file container with GNOME Disks'
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 8.818 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 08:39:04)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:39:04_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:39:04_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:39:04_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:39:04_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.046
Feature: Using VeraCrypt encrypted volumes
1:11.677
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.040
Steps
Given I have started Tails from DVD without network and logged in 1:11.677
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/veracrypt.feature:8:in `Given I have started Tails from DVD without network and logged in'
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
0.000
Scenario Use GNOME Disks to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 0.000
And I unlock and mount this VeraCrypt file container with GNOME Disks 0.000
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 6.937 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 08:40:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:40:25_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:40:25_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:40:25_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:40:25_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
1:16.026
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given I have started Tails from DVD without network and logged in 1:16.026
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/veracrypt.feature:8:in `Given I have started Tails from DVD without network and logged in'
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
0.000
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 0.000
And I unlock and mount this VeraCrypt file container with GNOME Disks 0.000
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 7.028 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM' (at time 08:41:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:41:48_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:41:48_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:41:48_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:41:48_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000
Feature: I can report a bug with WhisperBack
Tags: @product
1:19.072
Scenario All debugging information can be retrieved
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD without network and logged in 1:19.072
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/whisperback.feature:13:in `Given I have started Tails from DVD without network and logged in'
Then running "/usr/local/sbin/tails-debugging-info --strict" as user "root" succeeds 0.000
After features/support/hooks.rb:330 7.064 
SCENARIO FAILED: 'All debugging information can be retrieved' (at time 08:43:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:43:48_All_debugging_information_can_be_retrieved.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:43:48_All_debugging_information_can_be_retrieved.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:43:48_All_debugging_information_can_be_retrieved.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/08:43:48_All_debugging_information_can_be_retrieved.journal
After features/support/hooks.rb:100 0.000