Project Number Date
test_Tails_ISO_feature-trixie 49 09 Jul 2025, 10:42

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
3:1.968
Scenario The clock is set to the source date when the hardware clock is way in the past
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.207
And the hardware clock is set to "01 Jan 2000 12:34:56" 0.025
And I start the computer 2.831
And the computer boots Tails 2:58.730
Then the system clock is just past Tails' source date 0.172
The 
The system time (2025-06-25 12:42:27 +0000) is before the Tails source date (2025-06-26 10:09:02 +0000).
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/time_syncing.rb:126:in `/^the system clock is just past Tails' source date$/'
features/time_syncing.feature:53:in `Then the system clock is just past Tails' source date'
After features/support/hooks.rb:515 0.033
After features/support/hooks.rb:330 7.229 
SCENARIO FAILED: 'The clock is set to the source date when the hardware clock is way in the past' (at time 00:41:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/00:41:09_The_clock_is_set_to_the_source_date_when_the_hardware_clock_is_way_in_the_past.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/00:41:09_The_clock_is_set_to_the_source_date_when_the_hardware_clock_is_way_in_the_past.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/00:41:09_The_clock_is_set_to_the_source_date_when_the_hardware_clock_is_way_in_the_past.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/00:41:09_The_clock_is_set_to_the_source_date_when_the_hardware_clock_is_way_in_the_past.journal
After features/support/hooks.rb:100 0.064
Feature: Time syncing
Tags: @product @check_tor_leaks
1:41.621
Scenario I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.052
Before features/support/hooks.rb:507 0.025
Steps
Given I have started Tails from DVD without network and logged in 15.010
When I bump the system time with "+8 hours +15 minutes" 2.176
And all notifications have disappeared 11.991
And I capture all network traffic 0.010
And I make sure time sync before Tor connects fails 0.977
And the network is plugged 0.157
And the Tor Connection Assistant autostarts 15.017
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 5.791
And I click "Connect to Tor" 1.936
And the Tor Connection Assistant fails to connect to Tor 17.709
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 25.764
Then the system clock is less than 20 minutes incorrect 1.882
When I click "Connect to Tor" 3.194
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:840:in `/^(?:I click "Connect to Tor"|I retry connecting to Tor)$/'
features/time_syncing.feature:76:in `When I click "Connect to Tor"'
Then I wait until Tor is ready 0.000
And all Internet traffic has only flowed through the default bridges or fake connectivity check service 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:515 0.046
After features/support/hooks.rb:330 5.175 
SCENARIO FAILED: 'I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC' (at time 00:44:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/00:44:02_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/00:44:02_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/00:44:02_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/00:44:02_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.journal
After features/support/hooks.rb:100 0.035
Feature: Using Tor bridges and pluggable transports
Tags: @product
14.009
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 14.009
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/tor_bridges.feature:21:in `When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode'
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:330 5.946 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:50:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/00:50:03_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/00:50:03_Using_obfs4_pluggable_transports.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/00:50:03_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/00:50:03_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:100 0.049
Feature: Using Tor bridges and pluggable transports
Tags: @product @supports_real_tor
8.745
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 8.745
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/tor_bridges.feature:48:in `When I configure the default bridges in the Tor Connection Assistant'
Then I wait until Tor is ready 0.000
And Tor is configured to use the default bridges 0.000
And tca.conf includes no bridge 0.000
And available upgrades have been checked 0.000
And Tor is configured to use the default bridges 0.000
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000
After features/support/hooks.rb:330 8.620 
SCENARIO FAILED: 'Default Tor bridges' (at time 00:55:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/00:55:39_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/00:55:39_Default_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/00:55:39_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/00:55:39_Default_Tor_bridges.journal
After features/support/hooks.rb:100 0.059
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
40.225
Scenario Erasure of memory freed by killed userspace processes
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 25.565
And I prepare Tails for memory erasure tests 3.361
When I start a process allocating 128 MiB of memory with a known pattern 6.054
Then patterns cover at least 128 MiB in the guest's memory 5.243
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 8.177 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 01:06:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/01:06:49_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/49/artifact/build-artifacts/01:06:49_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/01:06:49_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/01:06:49_Erasure_of_memory_freed_by_killed_userspace_processes.journal
After features/support/hooks.rb:100 0.000
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
1:28.820
Scenario Erasure of read and write disk caches of persistent data on shutdown
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.126
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:28.820
execution 
execution expired (RemoteShell::SocketReadTimeout)
./features/support/helpers/misc_helpers.rb:114:in `sleep'
./features/support/helpers/misc_helpers.rb:114: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/support/helpers/vm_helper.rb:548:in `wait_until_remote_shell_is_up'
./features/step_definitions/common_steps.rb:447:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137: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/erase_memory.feature:75:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I prepare Tails for memory erasure tests 0.000
When I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
When I trigger shutdown 0.000
Then I find very few patterns in the guest's memory after 20 seconds 0.000
After features/support/hooks.rb:330 14.897 
SCENARIO FAILED: 'Erasure of read and write disk caches of persistent data on shutdown' (at time 01:16:05)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/01:16:05_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/01:16:05_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/01:16:05_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal
After features/support/hooks.rb:100 0.060
Feature: Installing Tails to a USB drive
Tags: @product
15:45.880
Scenario Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.057
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15:45.880
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:139:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137: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/usb_install.feature:45:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I create a file in the Persistent directory 0.000
And I temporarily create a 7200 MiB disk named "install" 0.000
And I create a gpt partition with a vfat filesystem on disk "install" 0.000
And I plug USB drive "install" 0.000
And I install Tails with Persistent Storage 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
And there is a persistence partition on USB drive "install" 0.000
And the USB drive "install" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:330 6.795 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage' (at time 01:42:04)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/01:42:04_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/01:42:04_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/01:42:04_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/01:42:04_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.007
Feature: Installing Tails to a USB drive
Tags: @product
24:31.031
Scenario Installing Tails with Tails Installer to a pristine USB drive, without cloning the Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24:31.031
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_install.feature:57:in `Given I have started Tails without network from a USB drive with a persistent partition enabled 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
And there is no persistence partition on USB drive "install" 0.000
After features/support/hooks.rb:330 5.780 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a pristine USB drive, without cloning the Persistent Storage' (at time 02:06:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/02:06:42_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/02:06:42_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/02:06:42_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/02:06:42_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.009
Feature: Additional software
Tags: @product @check_tor_leaks @slow
17:14.272
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.011
Before features/support/hooks.rb:507 0.025
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 2:45.031
And I update APT using apt 16.408
And I install "popularity-contest" using apt 39.724
Then I am proposed to add the "popularity-contest" package to my Additional Software 24.542
When I create a persistent storage and activate the Additional Software feature 54.842
Then Additional Software is correctly configured for package "popularity-contest" 11.429
When I shutdown Tails and wait for the computer to power off 23.699
And I start Tails from USB drive "__internal" with network unplugged 3:5.119
And I enable persistence 1:11.568
And I log in to a new session 1:22.025
And the Additional Software installation service has started 53.084
Then I am notified that the installation succeeded 5:6.795
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.046
After features/support/hooks.rb:330 13.164 
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 02:55:25)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/02:55:25_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/49/artifact/build-artifacts/02:55:25_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/49/artifact/build-artifacts/02:55:25_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.192
Feature: Additional software
Tags: @product @check_tor_leaks @slow
27:36.225
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.212
Before features/support/hooks.rb:507 0.163
Steps
Given a computer 0.725
And I start Tails from USB drive "__internal" and I login with an administration password 5:5.715
And I update APT using apt 19.815
When I install "makepp" using apt 22:9.969
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.041
After features/support/hooks.rb:330 8.990 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 03:23:16)
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/49/artifact/build-artifacts/03:23:16_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/49/artifact/build-artifacts/03:23:16_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/49/artifact/build-artifacts/03:23:16_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/49/artifact/build-artifacts/03:23:16_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/49/artifact/build-artifacts/03:23:16_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/49/artifact/build-artifacts/03:23:16_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/49/artifact/build-artifacts/03:23:16_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/49/artifact/build-artifacts/03:23:16_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.052
Feature: Additional software
Tags: @product @check_tor_leaks @slow
15:54.696
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.022
Before features/support/hooks.rb:507 0.024
Steps
Given a computer 0.385
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 7:21.822
When I uninstall "popularity-contest" using apt 35.718
And I accept removing "popularity-contest" from Additional Software 6.315
Then "popularity-contest" is not in the list of Additional Software 0.965
When I start Synaptic 28.875
And I update APT using Synaptic 25.590
And I install "cowsay" using Synaptic 6:55.022
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.131
After features/support/hooks.rb:330 8.390 
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 03:39:21)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/03:39:21_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/49/artifact/build-artifacts/03:39:21_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/49/artifact/build-artifacts/03:39:21_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/49/artifact/build-artifacts/03:39:21_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/49/artifact/build-artifacts/03:39:21_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/49/artifact/build-artifacts/03:39:21_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/49/artifact/build-artifacts/03:39:21_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/49/artifact/build-artifacts/03:39:21_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/49/artifact/build-artifacts/03:39:21_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.015
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
18:44.474
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.018
Before features/support/hooks.rb:507 0.021
Steps
Given a computer 0.575
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 5:51.001
And I configure APT to prefer an old version of cowsay 0.123
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 41.040
And I accept adding "cowsay" to Additional Software 19.314
And Additional Software is correctly configured for package "cowsay" 6.193
And I shutdown Tails and wait for the computer to power off 20.388
And I start Tails from USB drive "__internal" with network unplugged 3:2.191
And I enable persistence 37.846
# 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.067
# 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.094
And I log in to a new session 1:5.009
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 46.616
And I revert the APT tweaks that made it prefer an old version of cowsay 0.092
# 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.077
And the network is plugged 0.128
And Tor is ready 27.355
And available upgrades have been checked 1.260
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 4.777
And I can open the Additional Software configuration window from the notification 6.664
And I shutdown Tails and wait for the computer to power off 23.442
And I start Tails from USB drive "__internal" with network unplugged 2:21.125
And I enable persistence 19.380
# 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.036
And I log in to a new session 1:13.839
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 36.845
And I revert the APT tweaks that made it prefer an old version of cowsay 0.480
And the network is plugged 1.100
And Tor is ready 17.404
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:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:688:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:642:in `/^Tor is ready$/'
features/additional_software_packages.feature:114:in `And Tor is ready'
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.093
After features/support/hooks.rb:330 10.659 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 03:58:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/03:58:16_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/03:58:16_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/03:58:16_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/49/artifact/build-artifacts/03:58:16_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/49/artifact/build-artifacts/03:58:16_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/49/artifact/build-artifacts/03:58:16_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/49/artifact/build-artifacts/03:58:16_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/49/artifact/build-artifacts/03:58:16_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/49/artifact/build-artifacts/03:58:16_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal
After features/support/hooks.rb:100 0.036
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
4:7.614
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.009
Before features/support/hooks.rb:507 0.009
Steps
Given a computer 0.236
And I start Tails from USB drive "__internal" with network unplugged 2:18.726
And I enable persistence 20.725
And I remove the "cowsay" deb files from the APT cache 0.062
# 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.101
And I log in to a new session 1:10.447
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 5.990
And I can open the Additional Software log file from the notification 11.323
The 
The Dogtail init script raised: SearchError: descendant of [notification | ]: child with name='Show Log' roleName='button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/additional_software_packages.rb:39:in `click_gnome_shell_notification_button'
./features/step_definitions/additional_software_packages.rb:166:in `/^I can open the Additional Software log file from the notification$/'
features/additional_software_packages.feature:130:in `And I can open the Additional Software log file from the notification'
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:515 0.048
After features/support/hooks.rb:330 9.760 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 04:02:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/04:02:33_I_am_notified_when_Additional_Software_fails_to_install_a_package.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/04:02:33_I_am_notified_when_Additional_Software_fails_to_install_a_package.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/49/artifact/build-artifacts/04:02:33_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/49/artifact/build-artifacts/04:02:33_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/49/artifact/build-artifacts/04:02:33_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/49/artifact/build-artifacts/04:02:33_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/49/artifact/build-artifacts/04:02:33_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/04:02:33_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/49/artifact/build-artifacts/04:02:33_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.027
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
23:17.743
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.015
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.876
And no SquashFS delta is installed 0.202
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.389
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.614
And the file system changes introduced in version 6.3~testoverlayfs are not present 3.968
When the network is plugged 1.174
And Tor is ready 28.947
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:22.490
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 9.320 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 04:48:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/04:48:29_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/49/artifact/build-artifacts/04:48:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/04:48:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/04:48:29_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
23:51.630
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.039
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 37.250
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 2.645
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.186
And the signing key used by the Upgrader is outdated 0.135
But a current signing key is available on our website 0.000
When the network is plugged 0.119
And Tor is ready 52.822
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:18.469
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 13.103 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 05:12:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:12:34_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:12:34_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:12:34_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:12:34_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000
Feature: Emergency shutdown
Tags: @product @not_release_blocker
1:59.938
Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Steps
Given I have started Tails from DVD without network and logged in 20.561
And I prepare Tails for memory erasure tests 1.556
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 1:37.820
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:825:in `deal_with_polkit_prompt'
./features/step_definitions/common_steps.rb:1533:in `/^I plug and mount a (\d+) MiB USB drive with an? (.*)$/'
features/emergency_shutdown.feature:39:in `And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf"'
And I fill the USB drive with a known pattern 0.000
And I read the content of the test FS 0.000
And patterns cover at least 99% of the test FS size in the guest's memory 0.000
When I eject the boot medium 0.000
And I wait for Tails to finish wiping the memory 0.000
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:330 13.982 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 05:20:56)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:20:56_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:20:56_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:20:56_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.005
Feature: Emergency shutdown
Tags: @product @not_release_blocker
1:19.100
Scenario Tails erases memory and shuts down on USB boot medium removal: persistent data
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:19.100
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/emergency_shutdown.feature:48:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I prepare Tails for memory erasure tests 0.000
And I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
And patterns cover at least 100 MiB in the guest's memory 0.000
When I eject the boot medium 0.000
And I wait for Tails to finish wiping the memory 0.000
Then I find very few patterns in the guest's memory 0.000
And Tails eventually shuts down 0.000
After features/support/hooks.rb:330 5.839 
SCENARIO FAILED: 'Tails erases memory and shuts down on USB boot medium removal: persistent data' (at time 05:22:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:22:25_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:22:25_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:22:25_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:22:25_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.journal
After features/support/hooks.rb:100 0.000
Feature: Backing up the persistent storage
Tags: @product
2:21.373
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.037
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.718
# 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 23.234
And I clone USB drive "__internal" to a temporary USB drive "backup" 2.936
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 25.506
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.394
When I start Tails' custom backup tool 12.591
Then the backup tool displays "Plug in your backup Tails USB stick" 0.564
When I plug USB drive "backup" 4.655
And I give the Persistent Storage on drive "backup" its own UUID 0.333
And I click "Retry" in the backup tool 1.332
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.322
When I click "Back Up" in the backup tool 1.260
And I enter my persistent storage passphrase into the polkit prompt 22.520
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 30.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/backup.rb:6:in `/^the backup tool displays "([^"]+)"$/'
features/backup.feature:22:in `Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!"'
# 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 18.398 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 05:28:06)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:28:06_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:28:06_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:28:06_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.118
Feature: Electrum Bitcoin client
Tags: @product @check_tor_leaks
22.627
Scenario I am warned if Electrum is not persistent
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.545
Before features/support/hooks.rb:507 0.503
Steps
Given I have started Tails from DVD without network and logged in 12.422
When I start Electrum through the GNOME menu 10.205
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:1177:in `/^I start "([^"]+)" via GNOME Activities Overview$/'
./features/step_definitions/electrum.rb:14:in `/^I start Electrum through the GNOME menu$/'
features/electrum.feature:9:in `When I start Electrum through the GNOME menu'
But the "electrum" tps feature is not enabled 0.000
And I see a warning that Electrum is not persistent 0.000
After features/support/hooks.rb:515 0.045
After features/support/hooks.rb:330 6.210 
SCENARIO FAILED: 'I am warned if Electrum is not persistent' (at time 05:35:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:35:23_I_am_warned_if_Electrum_is_not_persistent.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:35:23_I_am_warned_if_Electrum_is_not_persistent.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:35:23_I_am_warned_if_Electrum_is_not_persistent.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:35:23_I_am_warned_if_Electrum_is_not_persistent.journal
After features/support/hooks.rb:100 0.000
Feature: GNOME is well-integrated into Tails
Tags: @product
1:9.541
Scenario I can launch various apps via GNOME Activities Overview
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Steps
# Some apps (Electrum and Persistent Storage Backup) only start when
# a Persistent Storage is available.
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 56.074
# Some apps (Tor Browser) only start when the network is plugged.
And the network is plugged 1.879
And Tor is ready 11.587
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:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:688:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:642:in `/^Tor is ready$/'
features/gnome.feature:25:in `And Tor is ready'
And all notifications have disappeared 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I close the "tails-additional-software-config" window 0.000
When I start "Disks" via GNOME Activities Overview 0.000
# The close button of GNOME Disks is not accessible
And I close the "gnome-disks" window via Alt+F4 0.000
When I start "GNOME Terminal" via GNOME Activities Overview 0.000
And I close the "org.gnome.Terminal" window 0.000
When I start "Files" via GNOME Activities Overview 0.000
And I close the "org.gnome.Nautilus" window 0.000
When I start "Persistent Storage" via GNOME Activities Overview 0.000
And I close the "tps-frontend" window 0.000
When I start "Back Up Persistent Storage" via GNOME Activities Overview 0.000
And I close the "zenity" window 0.000
When I start "Pidgin" via GNOME Activities Overview 0.000
And I close the "Pidgin" window via Alt+F4 0.000
When I start "Thunderbird" via GNOME Activities Overview 0.000
And I close the "Thunderbird" window 0.000
When I start "Tor Browser" via GNOME Activities Overview 0.000
And I close the "Firefox" window 0.000
When I start "Unlock VeraCrypt Volumes" via GNOME Activities Overview 0.000
And I close the "unlock-veracrypt-volumes" window 0.000
When I start "Unsafe Browser" via GNOME Activities Overview 0.000
And I close the "Firefox" window 0.000
After features/support/hooks.rb:330 8.608 
SCENARIO FAILED: 'I can launch various apps via GNOME Activities Overview' (at time 05:43:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:43:02_I_can_launch_various_apps_via_GNOME_Activities_Overview.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:43:02_I_can_launch_various_apps_via_GNOME_Activities_Overview.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:43:02_I_can_launch_various_apps_via_GNOME_Activities_Overview.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:43:02_I_can_launch_various_apps_via_GNOME_Activities_Overview.journal
After features/support/hooks.rb:100 0.000
Feature: Spoofing MAC addresses
Tags: @product
3:16.048
Scenario MAC address spoofing fails and macchanger returns false
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.882
And I capture all network traffic 0.017
And the network is plugged 0.110
And macchanger will fail by not spoofing and always returns false 0.201
When I log in to a new session 3:6.836
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/mac_spoofing.feature:40:in `When I log in to a new session'
Then no network interfaces are enabled 0.000
And no network device leaked the real MAC address 0.000
And I see the "Wired Network Disabled" notification after at most 60 seconds 0.000
After features/support/hooks.rb:330 7.367 
SCENARIO FAILED: 'MAC address spoofing fails and macchanger returns false' (at time 07:23:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/07:23:17_MAC_address_spoofing_fails_and_macchanger_returns_false.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/07:23:17_MAC_address_spoofing_fails_and_macchanger_returns_false.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/07:23:17_MAC_address_spoofing_fails_and_macchanger_returns_false.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/07:23:17_MAC_address_spoofing_fails_and_macchanger_returns_false.journal
After features/support/hooks.rb:100 0.074
Feature: Tails persistence
Tags: @product
6:25.421
Scenario Persistent Greeter options
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
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.315
When I enable persistence 1:8.548
Then no persistent Greeter options were restored 16.501
When I set all Greeter options to non-default values 51.825
And I log in to a new session in German (de) after having activated the Persistent Storage 54.612
Then all Greeter options are set to non-default values 0.563
When I cold reboot the computer 13.328
And the computer reboots Tails 2:4.848
Given I enable persistence 24.002
Then persistent Greeter options were restored 0.666
When I log in to a new session after having activated the Persistent Storage 17.206
The 
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with name='Start Tails' roleName='button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/common_steps.rb:516:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/persistence.feature:113:in `When I log in to a new session after having activated the Persistent Storage'
Then all Greeter options are set to non-default values 0.000
After features/support/hooks.rb:330 7.191 
SCENARIO FAILED: 'Persistent Greeter options' (at time 08:03:01)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:03:01_Persistent_Greeter_options.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:03:01_Persistent_Greeter_options.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:03:01_Persistent_Greeter_options.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:03:01_Persistent_Greeter_options.journal
After features/support/hooks.rb:100 0.013
Feature: Tails persistence
Tags: @product
1:22.289
Scenario Changing the Persistent Storage passphrase
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.727
# 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.561
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 10.857 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 08:04:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:04:32_Changing_the_Persistent_Storage_passphrase.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:04:32_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:04:32_Changing_the_Persistent_Storage_passphrase.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:04:32_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:29.313
Scenario Manual filesystem repair is successful
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.033
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 12.722
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 15.428
When I try to enable persistence 1.157
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.004
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 10.595 
SCENARIO FAILED: 'Manual filesystem repair is successful' (at time 08:25:49)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:25:49_Manual_filesystem_repair_is_successful.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:25:49_Manual_filesystem_repair_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:25:49_Manual_filesystem_repair_is_successful.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:12.854
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 12.302
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.144
When I try to enable persistence 0.405
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 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: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 12.768 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 08:27:15)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:27:15_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:27:15_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:27:15_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
1:49.671
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 22.363
And I create a persistent partition with the default settings 55.539
Then the "TorConfiguration" tps feature is not enabled 3.927
When the network is plugged 0.148
And the Tor Connection Assistant autostarts 17.088
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 10.603
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:637:in `block (2 levels) in <top (required)>'
./features/step_definitions/tor.rb:499: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 6.943 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 08:40:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:40:59_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:40:59_Disabling_persistence_of_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:40:59_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:40:59_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
3:55.368
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.010
Before features/support/hooks.rb:507 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 21.668
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 10.429
Then I see Pidgin's account manager window 6.792
When I create my XMPP account 23.898
And I close Pidgin's account manager window 1.321
Then Pidgin automatically enables my XMPP account 18.920
When I join some empty multi-user chat 41.025
And I clear the multi-user chat's scrollback 17.716
And my XMPP friend goes online and joins the multi-user chat 17.653
Then I can see that my friend joined the multi-user chat 1:15.942
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.042
After features/support/hooks.rb:330 5.749 
SCENARIO FAILED: 'Chatting with some friend over XMPP in a multi-user chat' (at time 08:49:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:49:00_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/49/artifact/build-artifacts/08:49:00_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/08:49:00_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/49/artifact/build-artifacts/08:49:00_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.journal
After features/support/hooks.rb:100 0.001
Feature: The Tor enforcement is effective
Tags: @product
2:8.607
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.022
Steps
Given I have started Tails from DVD and logged in and the network is connected 15.088
And I capture all network traffic 0.031
When I successfully start the Unsafe Browser 31.453
And I open the Tails homepage in the Unsafe Browser 21.997
And the Tails homepage loads in the Unsafe Browser 1:0.037
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:345: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 9.718 
SCENARIO FAILED: 'Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector' (at time 09:39:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/09:39:46_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_feature-trixie/49/artifact/build-artifacts/09:39:46_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_feature-trixie/49/artifact/build-artifacts/09:39:46_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_feature-trixie/49/artifact/build-artifacts/09:39:46_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:100 0.050
Feature: Using Totem
Tags: @product
59.077
Scenario Watching a MP4 video stored on the non-persistent filesystem
Steps
Given I have started Tails from DVD without network and logged in 9.530
And I plug and mount a USB drive containing sample videos 26.564
And I copy the sample videos to "/home/amnesia" as user "amnesia" 0.245
And the file "/home/amnesia/video.mp4" exists 0.149
Given I start monitoring the AppArmor log of "/usr/bin/totem" 0.268
When I open "/home/amnesia/video.mp4" with Totem 4.462
Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 3.938
And AppArmor has not denied "/usr/bin/totem" from opening "/home/amnesia/video.mp4" 0.070
Given I close Totem 0.228
And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.116
And the file "/home/amnesia/.gnupg/video.mp4" exists 0.095
And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.190
When I try to open "/home/amnesia/.gnupg/video.mp4" with Totem 2.325
Then Totem tells me it is not allowed to open this file 10.891
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.268 
SCENARIO FAILED: 'Watching a MP4 video stored on the non-persistent filesystem' (at time 10:27:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/10:27:42_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/49/artifact/build-artifacts/10:27:42_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/10:27:42_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/10:27:42_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.journal
After features/support/hooks.rb:100 0.001
Feature: Using Totem
Tags: @product
1:6.763
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 13.078
And I plug and mount a USB drive containing sample videos 25.922
And I copy the sample videos to "/home/amnesia/Persistent" as user "amnesia" 0.369
When I open "/home/amnesia/Persistent/video.mp4" with Totem 5.646
Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 5.520
Given I close Totem 2.094
And I start monitoring the AppArmor log of "/usr/bin/totem" 0.195
And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.087
When I try to open "/home/amnesia/.gnupg/video.mp4" with Totem 2.309
Then Totem tells me it is not allowed to open this file 11.539
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 5.369 
SCENARIO FAILED: 'Watching MP4 videos stored on the persistent volume should work as expected given our AppArmor confinement' (at time 10:29:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/10:29:43_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/49/artifact/build-artifacts/10:29:43_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/49/artifact/build-artifacts/10:29:43_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/49/artifact/build-artifacts/10:29:43_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.journal
After features/support/hooks.rb:100 0.001
Feature: Browsing the web using the Unsafe Browser
Tags: @product
1:59.800
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.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.887
When I successfully start the Unsafe Browser 27.546
When I open the Tails homepage in the Unsafe Browser 19.332
Then the Tails homepage loads in the Unsafe Browser 1:0.033
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:345: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 6.529 
SCENARIO FAILED: 'The Unsafe Browser can load a web page from the Internet' (at time 10:36:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/10:36:02_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_feature-trixie/49/artifact/build-artifacts/10:36:02_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/10:36:02_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/10:36:02_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product @not_release_blocker
1:21.208
Scenario Starting a second instance of the Unsafe Browser results in an error message being shown
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.330
When I successfully start the Unsafe Browser 27.379
# Wait for whatever facility the GNOME Activities Overview uses to
# learn about which applications are running to "settle". Without
# this sleep, it is confused and it's impossible to start a new
# instance (it will just switch to the one we already started).
And I wait 10 seconds 10.010 
Slept for 10 seconds
And I try to start the Unsafe Browser 0.480
Then I see a warning about another instance already running 30.007
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'zenity' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/unsafe_browser.rb:76:in `new'
./features/step_definitions/unsafe_browser.rb:76:in `block (2 levels) in <top (required)>'
./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/unsafe_browser.rb:75: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/unsafe_browser.rb:75:in `/^I see a warning about another instance already running$/'
features/unsafe_browser.feature:59:in `Then I see a warning about another instance already running'
After features/support/hooks.rb:330 11.894 
SCENARIO FAILED: 'Starting a second instance of the Unsafe Browser results in an error message being shown' (at time 10:38:22)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/10:38:22_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/10:38:22_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/10:38:22_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
44.383
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 32.420
And I unlock and mount this VeraCrypt file container with GNOME Disks 11.963
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.552 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 10:49:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/10:49:37_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/49/artifact/build-artifacts/10:49:37_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/49/artifact/build-artifacts/10:49:37_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/49/artifact/build-artifacts/10:49:37_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.014