Project Number Date
test_Tails_ISO_stable 5762 08 Jul 2025, 12:02

Failures Overview

The following summary displays scenarios that failed.

Feature: Installing Tails to a USB drive
Tags: @product
1:12.808
Scenario Installing Tails with Tails Installer to a pristine USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 1:12.808
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72: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/usb_install.feature:36:in `Given I have started Tails from DVD without network and logged in'
And I temporarily create a 7200 MiB disk named "install" 0.000
And I plug USB drive "install" 0.000
And I install Tails to USB drive "install" by cloning 0.000
Then the running Tails is installed on USB drive "install" 0.000
And there is a random seed on USB drive "install" 0.000
But there is no persistence partition on USB drive "install" 0.000
After features/support/hooks.rb:330 5.493 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a pristine USB drive' (at time 01:06:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/01:06:18_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/01:06:18_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/01:06:18_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/01:06:18_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.000
Feature: Installing Tails to a USB drive
Tags: @product
1:16.397
Scenario Re-installing Tails over an existing USB installation with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.042
Steps
# We reach this first checkpoint only to ensure that the ' __internal' disk has reached the state (Tails installed + persistent partition set up) we need before we clone it below.
# This first part is done without Tails Installer (install from Tails USB image)
# Note: the "__internal" disk will keep its state across scenarios
# and features until one of its snapshots is restored.
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 33.959
And I have started Tails from DVD without network and logged in 9.529
And I clone USB drive "__internal" to a temporary USB drive "install" 10.518
And I plug USB drive "install" 3.717
# This second part is done with Tails Installer, that's what this scenario is about
When I reinstall Tails to USB drive "install" by cloning 18.672
cannot 
cannot find TailsClonerWindow.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/usb.rb:156:in `/^I start Tails Installer$/'
./features/step_definitions/usb.rb:187:in `/^I (install|reinstall|upgrade) Tails( with Persistent Storage)? (?:to|on) USB drive "([^"]+)" by cloning$/'
features/usb_install.feature:75:in `When I reinstall Tails to USB drive "install" by cloning'
Then the running Tails is installed on USB drive "install" 0.000
And there is a random seed on USB drive "install" 0.000
And there is no persistence partition on USB drive "install" 0.000
After features/support/hooks.rb:330 5.804 
SCENARIO FAILED: 'Re-installing Tails over an existing USB installation with a persistent partition' (at time 01:17:22)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/01:17:22_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/01:17:22_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/01:17:22_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/01:17:22_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.journal
After features/support/hooks.rb:100 0.187
Feature: Additional software
Tags: @product @check_tor_leaks @slow
2:37.260
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.007
Before features/support/hooks.rb:507 0.006
Steps
Given a computer 0.253
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:37.007
cannot 
cannot find TailsGreeterAdminPasswordDialog.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:548:in `/^I set an administration password$/'
./features/step_definitions/common_steps.rb:294: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:55:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
When I uninstall "popularity-contest" using apt 0.000
And I accept removing "popularity-contest" from Additional Software 0.000
Then "popularity-contest" is not in the list of Additional Software 0.000
When I start Synaptic 0.000
And I update APT using Synaptic 0.000
And I install "cowsay" using Synaptic 0.000
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.050
After features/support/hooks.rb:330 11.151 
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 01:47:01)
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_stable/5762/artifact/build-artifacts/01:47:01_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
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/01:47:01_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_stable/5762/artifact/build-artifacts/01:47:01_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_stable/5762/artifact/build-artifacts/01:47:01_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_stable/5762/artifact/build-artifacts/01:47:01_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_stable/5762/artifact/build-artifacts/01:47:01_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_stable/5762/artifact/build-artifacts/01:47:01_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_stable/5762/artifact/build-artifacts/01:47:01_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.072
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
2:28.140
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.052
Before features/support/hooks.rb:507 0.021
Steps
Given a computer 1.002
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:27.138
cannot 
cannot find TailsGreeterAdminPasswordDialog.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:548:in `/^I set an administration password$/'
./features/step_definitions/common_steps.rb:294: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.030
After features/support/hooks.rb:330 7.618 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:49:41)
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_stable/5762/artifact/build-artifacts/01:49:41_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_stable/5762/artifact/build-artifacts/01:49:41_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_stable/5762/artifact/build-artifacts/01:49:41_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_stable/5762/artifact/build-artifacts/01:49:41_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_stable/5762/artifact/build-artifacts/01:49:41_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_stable/5762/artifact/build-artifacts/01:49:41_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_stable/5762/artifact/build-artifacts/01:49:41_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_stable/5762/artifact/build-artifacts/01:49:41_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.011
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
2:19.346
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.005
Before features/support/hooks.rb:507 0.005
Steps
Given a computer 0.235
And I start Tails from USB drive "__internal" with network unplugged 1:54.228
And I enable persistence 24.805
And I remove the "cowsay" deb files from the APT cache 0.077
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:137: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.036
After features/support/hooks.rb:330 13.880 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:52:11)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/01:52:11_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/01:52:11_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/01:52:11_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.008
Feature: Backing up the persistent storage
Tags: @product
1:21.244
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.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.555
# 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 9.358
And I clone USB drive "__internal" to a temporary USB drive "backup" 6.332
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.438
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.767
When I start Tails' custom backup tool 6.584
Then the backup tool displays "Plug in your backup Tails USB stick" 0.759
When I plug USB drive "backup" 2.826
And I give the Persistent Storage on drive "backup" its own UUID 0.128
And I click "Retry" in the backup tool 1.149
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.278
When I click "Back Up" in the backup tool 1.160
And I enter my persistent storage passphrase into the polkit prompt 20.904
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:791: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 11.184 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 02:30:05)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/02:30:05_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/02:30:05_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/02:30:05_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.242
Feature: Hardware failures
Tags: @product @broken_welcome_screen
1:49.374
Scenario Outline Alerting about disk read failures before reaching the Welcome Screen
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given a computer 0.243
And boot device is damaged in a way that some read operations fail 0.000
When I start the computer 1.066
Then the computer boots Tails 48.062
And I see a disk failure message on the splash screen 1:0.003
FindTextFailed 
FindTextFailed (FindTextFailed)
./features/support/helpers/screen.rb:274:in `rescue in wait_text'
./features/support/helpers/screen.rb:266:in `wait_text'
./features/step_definitions/hardware.rb:43:in `/^I see a disk failure message on the splash screen$/'
features/hardware_failure.feature:17:in `And I see a disk failure message on the splash screen'
features/hardware_failure.feature:13:in `And I see a disk failure message on the splash screen'
After features/support/hooks.rb:330 7.783 
SCENARIO FAILED: 'Alerting about disk read failures before reaching the Welcome Screen, Examples (#2)' (at time 02:46:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/02:46:51_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/02:46:51_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/02:46:51_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/02:46:51_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___2_.journal
After features/support/hooks.rb:100 0.021
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
5:14.726
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.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 15.581
When I log in to a new session in French (fr) 47.894
Then the keyboard layout is set to "fr" 0.652
When the network is plugged 0.155
And Tor is ready 36.141
Then I successfully start the Unsafe Browser 39.142
And I kill the Unsafe Browser 7.465
When I enable the screen keyboard 0.418
Then the screen keyboard works in Tor Browser 1:10.491
And DuckDuckGo is the default search engine 59.563
And I kill the Tor Browser 6.822
And the screen keyboard works in Thunderbird 30.395
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: "Thunderbird" application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:1047:in `new'
./features/step_definitions/common_steps.rb:1047:in `block in launch_app'
./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/common_steps.rb:1046:in `launch_app'
./features/step_definitions/common_steps.rb:1093:in `launch_thunderbird'
./features/step_definitions/thunderbird.rb:33:in `block in <top (required)>'
./features/step_definitions/thunderbird.rb:212:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:1046:in `launch_app'
./features/step_definitions/common_steps.rb:1093:in `launch_thunderbird'
./features/step_definitions/thunderbird.rb:33:in `/^I start Thunderbird$/'
./features/step_definitions/thunderbird.rb:212:in `/^the screen keyboard works in Thunderbird$/'
features/localization.feature:47:in `And the screen keyboard works in Thunderbird'
features/localization.feature:33:in `And the screen keyboard works in Thunderbird'
And the layout of the screen keyboard is set to "fr" 0.000
After features/support/hooks.rb:330 6.859 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#4)' (at time 03:34:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/03:34:19_Tails_is_localized_for_every_tier-1_language,_Examples___4_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/03:34:19_Tails_is_localized_for_every_tier-1_language,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/03:34:19_Tails_is_localized_for_every_tier-1_language,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/03:34:19_Tails_is_localized_for_every_tier-1_language,_Examples___4_.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:23.091
Scenario Changing the Persistent Storage passphrase
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.349
# 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 1:6.741
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:475:in `/^I change the passphrase of the Persistent Storage( back to the original)?$/'
features/persistence.feature:121:in `When I change the passphrase of the Persistent Storage'
And I shutdown Tails and wait for the computer to power off 0.000
Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 0.000
And I change the passphrase of the Persistent Storage back to the original 0.000
After features/support/hooks.rb:330 17.347 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 04:54:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/04:54:14_Changing_the_Persistent_Storage_passphrase.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/04:54:14_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/04:54:14_Changing_the_Persistent_Storage_passphrase.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/04:54:14_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:29.234
Scenario Feature activation fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 28.827
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.099
When I try to enable persistence 0.306
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 1:0.001
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:1724:in `/^the Welcome Screen tells me that the Persistent Folder feature couldn't be activated$/'
features/persistence.feature:146:in `Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated'
When I log in to a new session after having activated the Persistent Storage 0.000
And all notifications have disappeared 0.000
Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 0.000
And all tps features are enabled 0.000
And all tps features but the first one are active 0.000
After features/support/hooks.rb:330 11.969 
SCENARIO FAILED: 'Feature activation fails' (at time 05:01:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/05:01:51_Feature_activation_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/05:01:51_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/05:01:51_Feature_activation_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/05:01:51_Feature_activation_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:41.221
Scenario Manual filesystem repair is successful
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 and stopped at Tails Greeter's login screen 24.676
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 16.021
When I try to enable persistence 0.520
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.002
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:1732:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:176:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that the filesystem was repaired successfully 0.000
And the filesystem of the Persistent Storage was repaired 0.000
When I close the filesystem repair dialog 0.000
Then persistence is successfully enabled 0.000
After features/support/hooks.rb:330 17.891 
SCENARIO FAILED: 'Manual filesystem repair is successful' (at time 05:14:34)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/05:14:34_Manual_filesystem_repair_is_successful.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/05:14:34_Manual_filesystem_repair_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/05:14:34_Manual_filesystem_repair_is_successful.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:31.146
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 28.910
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.412
When I try to enable persistence 1.741
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.082
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:1732:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:188:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that it failed to repair the Persistent Storage 0.000
When I log in to a new session 0.000
And all notifications have disappeared 0.000
# Now both WhisperBack and Tor Browser has started at the same
# time, so we do not know which window is focused. The steps about
# Tor Browser care about that, but the ones about WhisperBack do
# not, so we first deal with WhisperBack and then kill it to
# ensure that Tor Browser is focused.
Then WhisperBack is prefilled for fsck with summary: "Failed to repair the file system of your Persistent Storage" 0.000
And the file "/var/lib/gdm3/post-greeter-whisperback.json" is empty 0.000
When I close the "whisperback" window 0.000
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 10.231 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 05:16:19)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/05:16:19_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/05:16:19_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/05:16:19_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
1:46.081
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 21.621
And I create a persistent partition with the default settings 55.896
Then the "TorConfiguration" tps feature is not enabled 3.871
When the network is plugged 0.108
And the Tor Connection Assistant autostarts 15.545
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 9.037
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/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:628:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/persistent_tor_bridges.feature:13:in `And I configure some persistent obfs4 bridges in the Tor Connection Assistant'
And I wait until Tor is ready 0.000
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 8.843 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 05:30:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/05:30:38_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/05:30:38_Disabling_persistence_of_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/05:30:38_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/05:30:38_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
1:18.440
Scenario No unexpected error messages in the journal after booting from USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:18.440
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72: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\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/sane_defaults.feature:24:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then there are no unexpected messages of priority "err" or higher in the journal 0.000
After features/support/hooks.rb:330 6.072 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 05:40:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/05:40:40_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/05:40:40_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/05:40:40_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/05:40:40_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal
After features/support/hooks.rb:100 0.000
Feature: Thunderbird email client
Tags: @product @check_tor_leaks
37:52.448
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 21.778
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 5.365
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 3.576
When I accept the autoconfiguration wizard's configuration 37:21.727
Tor 
Tor operation failed (despite retrying 10 times) with
Timeout::Error: try_for() timeout expired (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/thunderbird.rb:136:in `/^I accept the (?:autoconfiguration wizard's|manual) configuration$/'
features/thunderbird.feature:22:in `When I accept the autoconfiguration wizard's configuration'
And I send an email to myself 0.000
And I fetch my email 0.000
Then I can find the email I sent to myself in my inbox 0.000
After features/support/hooks.rb:515 0.042
After features/support/hooks.rb:330 12.440 
SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 06:27:43)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/06:27:43_I_can_send_emails,_and_receive_emails_over_IMAP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/06:27:43_I_can_send_emails,_and_receive_emails_over_IMAP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/06:27:43_I_can_send_emails,_and_receive_emails_over_IMAP.journal
After features/support/hooks.rb:100 0.001
Feature: The Tor enforcement is effective
Tags: @product
1:53.157
Scenario Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.055
Steps
Given I have started Tails from DVD and logged in and the network is connected 14.467
And I capture all network traffic 0.276
When I successfully start the Unsafe Browser 27.831
And I open the Tails homepage in the Unsafe Browser 10.277
And the Tails homepage loads in the Unsafe Browser 1:0.305
cannot 
cannot find TailsHomepage.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:316:in `/^the Tails homepage loads in the Unsafe Browser$/'
features/tor_enforcement.feature:20:in `And the Tails homepage loads in the Unsafe Browser'
Then the firewall leak detector has detected leaks 0.000
After features/support/hooks.rb:330 6.255 
SCENARIO FAILED: 'Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector' (at time 06:34:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/06:34:09_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/06:34:09_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/06:34:09_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/06:34:09_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:100 0.054
Feature: Browsing the web using the Unsafe Browser
Tags: @product
2:11.977
Scenario The Unsafe Browser can load a web page from the Internet
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.048
Steps
Given I have started Tails from DVD and logged in and the network is connected 30.925
When I successfully start the Unsafe Browser 26.280
When I open the Tails homepage in the Unsafe Browser 14.763
Then the Tails homepage loads in the Unsafe Browser 1:0.007
cannot 
cannot find TailsHomepage.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:316:in `/^the Tails homepage loads in the Unsafe Browser$/'
features/unsafe_browser.feature:38:in `Then the Tails homepage loads in the Unsafe Browser'
And the Unsafe Browser has sent packets out to the Internet 0.000
After features/support/hooks.rb:330 5.826 
SCENARIO FAILED: 'The Unsafe Browser can load a web page from the Internet' (at time 07:21:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/07:21:18_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/07:21:18_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/07:21:18_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/07:21:18_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
46.656
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 34.603
And I unlock and mount this VeraCrypt file container with GNOME Disks 12.053
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:350:in `doActionNamed'
./features/support/helpers/dogtail.rb:364:in `activate'
./features/step_definitions/veracrypt.rb:240: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 6.904 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 07:35:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/07:35:16_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_stable/5762/artifact/build-artifacts/07:35:16_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/07:35:16_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_stable/5762/artifact/build-artifacts/07:35:16_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.021
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
56.335
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 43.519
And I unlock and mount this VeraCrypt file container with GNOME Disks 12.815
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:350:in `doActionNamed'
./features/support/helpers/dogtail.rb:364:in `activate'
./features/step_definitions/veracrypt.rb:240:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:76: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.915 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 07:36:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/07:36:35_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_stable/5762/artifact/build-artifacts/07:36:35_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/07:36:35_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5762/artifact/build-artifacts/07:36:35_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.019