Project Number Date
test_Tails_ISO_feature-trixie 35 22 Jun 2025, 07:06

Failures Overview

The following summary displays scenarios that failed.

Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
16.654
Scenario Erasure of memory freed by killed userspace processes
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Steps
Given I have started Tails from DVD without network and logged in 8.910
And I prepare Tails for memory erasure tests 0.938
When I start a process allocating 128 MiB of memory with a known pattern 3.456
Then patterns cover at least 128 MiB in the guest's memory 3.349
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.965 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:38:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/00:38:36_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/35/artifact/build-artifacts/00:38:36_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/00:38:36_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/00:38:36_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:51.862
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.005
Before features/support/hooks.rb:507 0.006
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:28.262
And I update APT using apt 14.267
And I install "popularity-contest" using apt 26.429
Then I am proposed to add the "popularity-contest" package to my Additional Software 12.976
When I create a persistent storage and activate the Additional Software feature 31.124
Then Additional Software is correctly configured for package "popularity-contest" 3.076
When I shutdown Tails and wait for the computer to power off 15.602
And I start Tails from USB drive "__internal" with network unplugged 1:46.435
And I enable persistence 24.394
And I log in to a new session 49.829
And the Additional Software installation service has started 36.527
Then I am notified that the installation succeeded 5:2.934
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.055
After features/support/hooks.rb:330 6.793 
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:29:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/01:29:54_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/35/artifact/build-artifacts/01:29:54_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/35/artifact/build-artifacts/01:29:54_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/35/artifact/build-artifacts/01:29:54_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/35/artifact/build-artifacts/01:29:54_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/35/artifact/build-artifacts/01:29:54_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/35/artifact/build-artifacts/01:29:54_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/35/artifact/build-artifacts/01:29:54_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/35/artifact/build-artifacts/01:29:54_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.012
Feature: Additional software
Tags: @product @check_tor_leaks @slow
25:15.363
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.296
And I start Tails from USB drive "__internal" and I login with an administration password 2:56.564
And I update APT using apt 13.759
When I install "makepp" using apt 22:4.743
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.030
After features/support/hooks.rb:330 5.480 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:55:17)
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/35/artifact/build-artifacts/01:55:17_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/35/artifact/build-artifacts/01:55:17_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/35/artifact/build-artifacts/01:55:17_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/35/artifact/build-artifacts/01:55:17_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/35/artifact/build-artifacts/01:55:17_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/35/artifact/build-artifacts/01:55:17_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/35/artifact/build-artifacts/01:55:17_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/35/artifact/build-artifacts/01:55:17_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.012
Feature: Additional software
Tags: @product @check_tor_leaks @slow
10:14.710
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.004
Steps
Given a computer 0.181
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 4:34.045
When I uninstall "popularity-contest" using apt 25.215
And I accept removing "popularity-contest" from Additional Software 2.730
Then "popularity-contest" is not in the list of Additional Software 0.778
When I start Synaptic 15.919
And I update APT using Synaptic 22.402
And I install "cowsay" using Synaptic 4:33.436
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.038
After features/support/hooks.rb:330 5.801 
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:05:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/02:05:37_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/35/artifact/build-artifacts/02:05:37_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/35/artifact/build-artifacts/02:05:37_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/35/artifact/build-artifacts/02:05:37_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/35/artifact/build-artifacts/02:05:37_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/35/artifact/build-artifacts/02:05:37_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/35/artifact/build-artifacts/02:05:37_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/35/artifact/build-artifacts/02:05:37_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/35/artifact/build-artifacts/02:05:37_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.009
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
3:46.344
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.217
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 3:46.126
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/usb.rb:686:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704: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/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.039
After features/support/hooks.rb:330 5.169 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 02:09:29)
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/35/artifact/build-artifacts/02:09:29_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_feature-trixie/35/artifact/build-artifacts/02:09:29_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_feature-trixie/35/artifact/build-artifacts/02:09:29_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_feature-trixie/35/artifact/build-artifacts/02:09:29_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_feature-trixie/35/artifact/build-artifacts/02:09:29_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_feature-trixie/35/artifact/build-artifacts/02:09:29_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_feature-trixie/35/artifact/build-artifacts/02:09:29_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_feature-trixie/35/artifact/build-artifacts/02:09:29_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.008
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
2:2.334
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.004
Before features/support/hooks.rb:507 0.005
Steps
Given a computer 0.182
And I start Tails from USB drive "__internal" with network unplugged 1:46.020
And I enable persistence 16.072
And I remove the "cowsay" deb files from the APT cache 0.060
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.032
After features/support/hooks.rb:330 6.558 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 02:11:37)
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/35/artifact/build-artifacts/02:11:37_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_feature-trixie/35/artifact/build-artifacts/02:11:37_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_feature-trixie/35/artifact/build-artifacts/02:11:37_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_feature-trixie/35/artifact/build-artifacts/02:11:37_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_feature-trixie/35/artifact/build-artifacts/02:11:37_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/02:11:37_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/02:11:37_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/02:11:37_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
23:17.865
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.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.792
And no SquashFS delta is installed 0.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.368
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.503
When the network is plugged 0.076
And Tor is ready 55.247
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:9.386
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.700 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:51:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/02:51:14_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/35/artifact/build-artifacts/02:51:14_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/02:51:14_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/02:51:14_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.124
Scenario Upgrading a Tails whose signing key is outdated
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.304
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 25.972
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:11.347
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.346 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:14:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/03:14:10_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/35/artifact/build-artifacts/03:14:10_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/03:14:10_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/03:14:10_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:24.259
Scenario Outline Tails is localized for every tier-1 language
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 stopped at Tails Greeter's login screen 8.092
When I log in to a new session in French (fr) 50.528
Then the keyboard layout is set to "fr" 0.229
When the network is plugged 0.090
And Tor is ready 22.180
Then I successfully start the Unsafe Browser 16.205
And I kill the Unsafe Browser 7.455
When I enable the screen keyboard 0.148
Then the screen keyboard works in Tor Browser 39.327
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/step_definitions/browser.rb:482:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:438:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:46:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "fr" 0.000
After features/support/hooks.rb:330 8.719 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#4)' (at time 04:18:01)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/04:18:01_Tails_is_localized_for_every_tier-1_language,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/04:18:01_Tails_is_localized_for_every_tier-1_language,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/04:18:01_Tails_is_localized_for_every_tier-1_language,_Examples___4_.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
5:34.235
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 13.967
When I enable persistence 52.268
Then no persistent Greeter options were restored 15.930
When I set all Greeter options to non-default values 48.598
And I log in to a new session in German (de) after having activated the Persistent Storage 3:23.470
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:107:in `And I log in to a new session in German (de) after having activated the Persistent Storage'
Then all Greeter options are set to non-default values 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
Given I enable persistence 0.000
Then persistent Greeter options were restored 0.000
When I log in to a new session after having activated the Persistent Storage 0.000
Then all Greeter options are set to non-default values 0.000
After features/support/hooks.rb:330 7.107 
SCENARIO FAILED: 'Persistent Greeter options' (at time 05:30:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/05:30:25_Persistent_Greeter_options.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/05:30:25_Persistent_Greeter_options.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/05:30:25_Persistent_Greeter_options.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/05:30:25_Persistent_Greeter_options.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
3:36.677
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.054
Before features/support/hooks.rb:507 0.034
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.439
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.125
Then I see Pidgin's account manager window 3.259
When I create my XMPP account 16.305
And I close Pidgin's account manager window 0.976
Then Pidgin automatically enables my XMPP account 17.712
When I join some empty multi-user chat 42.397
And I clear the multi-user chat's scrollback 17.493
And my XMPP friend goes online and joins the multi-user chat 18.685
Then I can see that my friend joined the multi-user chat 1:15.281
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.033
After features/support/hooks.rb:330 6.351 
SCENARIO FAILED: 'Chatting with some friend over XMPP in a multi-user chat' (at time 06:15:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/06:15:38_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/35/artifact/build-artifacts/06:15:38_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/06:15:38_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/35/artifact/build-artifacts/06:15:38_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.journal
After features/support/hooks.rb:100 0.002
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
1:6.446
Scenario Using a persistent Pidgin configuration
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Before features/support/hooks.rb:507 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.168
And the network is plugged 0.088
And Tor is ready 25.289
And available upgrades have been checked 2.412
And all notifications have disappeared 5.689
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 10.810
Then I see Pidgin's account manager window 5.079
When I create my XMPP account 3.907
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:68: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
When I close Pidgin 0.000
And I take note of the configured Pidgin accounts 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Given a computer 0.000
And I start Tails from USB drive "__internal" and I login with persistence enabled 0.000
And Pidgin has the expected persistent accounts configured 0.000
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 0.000
Then Pidgin automatically enables my XMPP account 0.000
And I join some empty multi-user chat 0.000
# Exercise Pidgin AppArmor profile with persistence enabled.
# This should really be in dedicated scenarios, but it would be
# too costly to set up the virtual USB drive with persistence more
# than once in this feature.
Given I start monitoring the AppArmor log of "/usr/bin/pidgin" 0.000
Then I cannot add a certificate from the "/home/amnesia/.gnupg" directory to Pidgin 0.000
And AppArmor has denied "/usr/bin/pidgin" from opening "/home/amnesia/.gnupg/test.crt" 0.000
When I close Pidgin's certificate import failure dialog 0.000
And I close Pidgin's certificate manager 0.000
Given I restart monitoring the AppArmor log of "/usr/bin/pidgin" 0.000
Then I cannot add a certificate from the "/live/persistence/TailsData_unlocked/gnupg" directory to Pidgin 0.000
And AppArmor has denied "/usr/bin/pidgin" from opening "/live/persistence/TailsData_unlocked/gnupg/test.crt" 0.000
When I close Pidgin's certificate import failure dialog 0.000
And I close Pidgin's certificate manager 0.000
Then I can add a certificate from the "/home/amnesia" directory to Pidgin 0.000
After features/support/hooks.rb:515 0.034
After features/support/hooks.rb:330 5.559 
SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 06:18:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/06:18:52_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/06:18:52_Using_a_persistent_Pidgin_configuration.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/06:18:52_Using_a_persistent_Pidgin_configuration.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/06:18:52_Using_a_persistent_Pidgin_configuration.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
58.521
Scenario Persistent browser bookmarks
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.726
And all tps features are active 3.389
And all persistent filesystems have safe access rights 0.270
And all persistence configuration files have safe access rights 0.503
And all persistent directories have safe access rights 3.581
When I start the Tor Browser in offline mode 40.050
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/step_definitions/browser.rb:482: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 6.433 
SCENARIO FAILED: 'Persistent browser bookmarks' (at time 07:19:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/07:19:47_Persistent_browser_bookmarks.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/07:19:47_Persistent_browser_bookmarks.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/07:19:47_Persistent_browser_bookmarks.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/07:19:47_Persistent_browser_bookmarks.journal
After features/support/hooks.rb:100 0.000
Feature: Using Totem
Tags: @product
54.204
Scenario Watching a MP4 video stored on the non-persistent filesystem
Steps
Given I have started Tails from DVD without network and logged in 8.698
And I plug and mount a USB drive containing sample videos 19.788
And I copy the sample videos to "/home/amnesia" as user "amnesia" 0.072
And the file "/home/amnesia/video.mp4" exists 0.061
Given I start monitoring the AppArmor log of "/usr/bin/totem" 0.136
When I open "/home/amnesia/video.mp4" with Totem 5.959
Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 4.565
And AppArmor has not denied "/usr/bin/totem" from opening "/home/amnesia/video.mp4" 1.247
Given I close Totem 0.213
And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.133
And the file "/home/amnesia/.gnupg/video.mp4" exists 0.054
And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.121
When I try to open "/home/amnesia/.gnupg/video.mp4" with Totem 2.255
Then Totem tells me it is not allowed to open this file 10.895
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 6.437 
SCENARIO FAILED: 'Watching a MP4 video stored on the non-persistent filesystem' (at time 07:22:04)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/07:22:04_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/35/artifact/build-artifacts/07:22:04_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/07:22:04_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/07:22:04_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.journal
After features/support/hooks.rb:100 0.000
Feature: Using Totem
Tags: @product
57.670
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 10.832
And I plug and mount a USB drive containing sample videos 16.599
And I copy the sample videos to "/home/amnesia/Persistent" as user "amnesia" 0.155
When I open "/home/amnesia/Persistent/video.mp4" with Totem 7.001
Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 7.376
Given I close Totem 1.594
And I start monitoring the AppArmor log of "/usr/bin/totem" 0.288
And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.363
When I try to open "/home/amnesia/.gnupg/video.mp4" with Totem 2.305
Then Totem tells me it is not allowed to open this file 11.153
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 7.047 
SCENARIO FAILED: 'Watching MP4 videos stored on the persistent volume should work as expected given our AppArmor confinement' (at time 07:23:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/07:23:32_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/35/artifact/build-artifacts/07:23:32_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/35/artifact/build-artifacts/07:23:32_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/35/artifact/build-artifacts/07:23:32_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
Tags: @product @not_release_blocker
38.408
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 27.954
And I unlock and mount this VeraCrypt file container with GNOME Disks 10.454
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 7.770 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 07:39:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/35/artifact/build-artifacts/07:39:43_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/35/artifact/build-artifacts/07:39:43_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/35/artifact/build-artifacts/07:39:43_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/35/artifact/build-artifacts/07:39:43_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.015