Project Number Date
test_Tails_ISO_5501-plaintext-locale-greeter 35 24 Jun 2025, 17:01

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
53.165
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.002
Before features/support/hooks.rb:507 0.003
Steps
Given I have started Tails from DVD without network and logged in 20.767
When I bump the system time with "+8 hours +15 minutes" 0.230
And all notifications have disappeared 11.338
And I capture all network traffic 0.035
And I make sure time sync before Tor connects fails 0.744
And the network is plugged 0.148
And the Tor Connection Assistant autostarts 4.197
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 12.420
And I click "Connect to Tor" 3.282
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:71:in `And I click "Connect to Tor"'
And the Tor Connection Assistant fails to connect to Tor 0.000
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 0.000
Then the system clock is less than 20 minutes incorrect 0.000
When I click "Connect to Tor" 0.000
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.069
After features/support/hooks.rb:330 6.336 
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:34:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/00:34:35_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/00:34:35_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/00:34:35_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/00:34:35_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.056
Feature: Using Tor bridges and pluggable transports
Tags: @product
15.707
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 3.223
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 12.484
Expected 
Expected TCAConnectionFailure to be raised but got Timeout::Error: try_for() timeout expired (RuntimeError)
./features/step_definitions/tor.rb:760:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:755:in `/^I unsuccessfully configure (a direct connection|some .* bridges) in the Tor Connection Assistant$/'
features/tor_bridges.feature:104:in `When I unsuccessfully configure some default bridges in the Tor Connection Assistant'
Then the Tor Connection Assistant reports that it failed to connect 0.000
Given the Tor network and default bridges are unblocked 0.000
When I click "Connect to Tor" 0.000
Then I wait until Tor is ready 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 5.542 
SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 00:53:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/00:53:12_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/00:53:12_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/00:53:12_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/00:53:12_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal
After features/support/hooks.rb:100 0.055
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
1:12.782
Scenario Erasure of read and write disk caches on unmount: LUKS-encrypted ext4
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD without network and logged in 1:12.782
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/erase_memory.feature:48:in `Given I have started Tails from DVD without network and logged in'
And I prepare Tails for memory erasure tests 0.000
When I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 0.000
Then I find very few patterns in the guest's memory 0.000
# write cache
When I fill the USB drive with a known pattern 0.000
Then patterns cover at least 99% of the test FS size in the guest's memory 0.000
When I umount the USB drive 0.000
Then I find very few patterns in the guest's memory after 3 seconds 0.000
# read cache
When I mount the USB drive again 0.000
And I read the content of the test FS 0.000
Then patterns cover at least 99% of the test FS size in the guest's memory 0.000
When I umount the USB drive 0.000
Then I find very few patterns in the guest's memory after 3 seconds 0.000
After features/support/hooks.rb:330 6.018 
SCENARIO FAILED: 'Erasure of read and write disk caches on unmount: LUKS-encrypted ext4' (at time 00:59:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/00:59:51_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/00:59:51_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/00:59:51_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/00:59:51_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.000
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
12:23.653
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.113
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12:23.653
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb: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 6.579 
SCENARIO FAILED: 'Erasure of read and write disk caches of persistent data on shutdown' (at time 01:13:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:13:51_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:13:51_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:13:51_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:13:51_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal
After features/support/hooks.rb:100 0.007
Feature: Installing Tails to a USB drive
Tags: @product
13:11.639
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.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13:11.639
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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: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 11.623 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage' (at time 01:38:10)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:38:10_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:38:10_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:38:10_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.024
Feature: Installing Tails to a USB drive
Tags: @product
2:5.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.010
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:5.031
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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: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 14.781 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a pristine USB drive, without cloning the Persistent Storage' (at time 01:40:31)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:40:31_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:40:31_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:40:31_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.000
Feature: Installing Tails to a USB drive
Tags: @product
2:3.783
Scenario Re-installing Tails over an existing USB installation with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
# We reach this first checkpoint only to ensure that the ' __internal' disk has reached the state (Tails installed + persistent partition set up) we need before we clone it below.
# This first part is done without Tails Installer (install from Tails USB image)
# Note: the "__internal" disk will keep its state across scenarios
# and features until one of its snapshots is restored.
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:3.783
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_install.feature:70:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I have started Tails from DVD without network and logged in 0.000
And I clone USB drive "__internal" to a temporary USB drive "install" 0.000
And I plug USB drive "install" 0.000
# This second part is done with Tails Installer, that's what this scenario is about
When I reinstall Tails to USB drive "install" by cloning 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 12.882 
SCENARIO FAILED: 'Re-installing Tails over an existing USB installation with a persistent partition' (at time 01:42:50)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:42:50_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:42:50_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:42:50_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Additional software
Tags: @product @check_tor_leaks @slow
6:28.171
Scenario I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:507 0.004
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:22.754
And I update APT using apt 21.009
And I install "popularity-contest" using apt 33.061
Then I am proposed to add the "popularity-contest" package to my Additional Software 7.519
When I create a persistent storage and activate the Additional Software feature 39.655
Then Additional Software is correctly configured for package "popularity-contest" 5.732
When I shutdown Tails and wait for the computer to power off 16.521
And I start Tails from USB drive "__internal" with network unplugged 1:50.119
And I enable persistence 1:11.797
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704: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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
features/additional_software_packages.feature:36:in `And I enable persistence'
And I log in to a new session 0.000
And the Additional Software installation service has started 0.000
Then I am notified that the installation succeeded 0.000
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.060
After features/support/hooks.rb:330 8.493 
SCENARIO FAILED: 'I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails' (at time 01:58:25)
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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:58:25_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:58:25_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:58:25_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:58:25_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:58:25_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:58: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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:58: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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/01:58: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.062
Feature: Additional software
Tags: @product @check_tor_leaks @slow
4:34.566
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.010
Before features/support/hooks.rb:507 0.003
Steps
Given a computer 0.241
And I start Tails from USB drive "__internal" and I login with an administration password 4:34.325
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:566:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:522:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
./features/step_definitions/common_steps.rb:295:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/additional_software_packages.feature:46:in `And I start Tails from USB drive "__internal" and I login with an administration password'
And I update APT using apt 0.000
When I install "makepp" using apt 0.000
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.040
After features/support/hooks.rb:330 7.084 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 02:03:09)
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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:03:09_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:03:09_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:03:09_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:03:09_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:03:09_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:03:09_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:03:09_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:03:09_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.007
Feature: Additional software
Tags: @product @check_tor_leaks @slow
2:12.578
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.002
Before features/support/hooks.rb:507 0.002
Steps
Given a computer 0.177
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:12.401
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:291: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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:291:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/additional_software_packages.feature:55:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
When I uninstall "popularity-contest" using apt 0.000
And I accept removing "popularity-contest" from Additional Software 0.000
Then "popularity-contest" is not in the list of Additional Software 0.000
When I start Synaptic 0.000
And I update APT using Synaptic 0.000
And I install "cowsay" using Synaptic 0.000
And I accept adding "cowsay" to Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I uninstall "cowsay" using apt 0.000
And I refuse removing "cowsay" from Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I remove "cowsay" from the list of Additional Software using Additional Software GUI 0.000
Then "cowsay" is not in the list of Additional Software 0.000
When I install "cowsay" using apt 0.000
And I refuse adding "cowsay" to Additional Software 0.000
Then "cowsay" is not in the list of Additional Software 0.000
After features/support/hooks.rb:515 0.073
After features/support/hooks.rb:330 12.008 
SCENARIO FAILED: 'My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic' (at time 02:05:29)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:05:29_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:05:29_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:05:29_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.journal
After features/support/hooks.rb:100 0.006
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
2:20.407
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.002
Before features/support/hooks.rb:507 0.003
Steps
Given a computer 0.168
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:20.238
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:291: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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:291:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/additional_software_packages.feature:79:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
And I configure APT to prefer an old version of cowsay 0.000
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 0.000
And I accept adding "cowsay" to Additional Software 0.000
And Additional Software is correctly configured for package "cowsay" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.000
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
# We remove the newest package after it has been downloaded and before
# it is installed, so that the upgrade process fails
And I prepare the Additional Software upgrade process to fail 0.000
And the network is plugged 0.000
And Tor is ready 0.000
And available upgrades have been checked 0.000
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.000
And I can open the Additional Software configuration window from the notification 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
And the network is plugged 0.000
And Tor is ready 0.000
Then the Additional Software upgrade service has started 0.000
And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000
After features/support/hooks.rb:515 0.030
After features/support/hooks.rb:330 9.557 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 02:08:02)
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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:08:02_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:08:02_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:08:02_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:08:02_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:08:02_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:08:02_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:08:02_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:08:02_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.024
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
2:12.285
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.013
Before features/support/hooks.rb:507 0.009
Steps
Given a computer 0.311
And I start Tails from USB drive "__internal" with network unplugged 1:25.056
And I enable persistence 46.917
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704: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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
features/additional_software_packages.feature:123:in `And I enable persistence'
And I remove the "cowsay" deb files from the APT cache 0.000
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.000
And I log in to a new session 0.000
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 0.000
And I can open the Additional Software log file from the notification 0.000
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:515 0.053
After features/support/hooks.rb:330 10.968 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 02:10:24)
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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:10:24_I_am_notified_when_Additional_Software_fails_to_install_a_package.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:10:24_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:10:24_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:10:24_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:10:24_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:10:24_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:10:24_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:10:24_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.008
Feature: Upgrading an old Tails USB installation
Tags: @product
2:35.908
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:35.733
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:291: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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:291:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:330 10.220 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:19:29)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:19:29_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:19:29_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:19:29_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.024
Feature: Upgrading an old Tails USB installation
Tags: @product
2:14.546
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.298
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.248
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:291: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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:291:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:330 10.945 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:25:31)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:25:31_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:25:31_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:25:31_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
1:49.363
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:49.363
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_upgrade.feature:82:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And no SquashFS delta is installed 0.000
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.000
And the file system changes introduced in version 6.3~testoverlayfs are not present 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.2~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:330 5.803 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:27:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:27:31_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:27:31_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:27:31_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:27:31_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
1:43.986
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:43.986
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_upgrade.feature:127:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the signing key used by the Upgrader is outdated 0.000
But a current signing key is available on our website 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.2~testoverlayfs 0.000
After features/support/hooks.rb:330 11.336 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 02:29:24)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:29:24_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:29:24_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:29:24_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:29:24_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:26.563
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.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:26.563
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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: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 7.417 
SCENARIO FAILED: 'Tails erases memory and shuts down on USB boot medium removal: persistent data' (at time 02:36:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:36:00_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:36:00_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:36:00_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:36:00_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.journal
After features/support/hooks.rb:100 0.000
Feature: Backing up the persistent storage
Tags: @product
1:28.865
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.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:28.865
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/backup.feature:8:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
# 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 0.000
And I clone USB drive "__internal" to a temporary USB drive "backup" 0.000
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 0.000
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.000
When I start Tails' custom backup tool 0.000
Then the backup tool displays "Plug in your backup Tails USB stick" 0.000
When I plug USB drive "backup" 0.000
And I give the Persistent Storage on drive "backup" its own UUID 0.000
And I click "Retry" in the backup tool 0.000
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.000
When I click "Back Up" in the backup tool 0.000
And I enter my persistent storage passphrase into the polkit prompt 0.000
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 0.000
# The backup tool ejects the drive, so we have to replug it
When I unplug USB drive "backup" 0.000
And I plug USB drive "backup" 0.000
Then the USB drive "backup" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:330 5.861 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 02:38:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:38:49_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:38:49_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:38:49_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:38:49_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.000
Feature: Using Evince
Tags: @product
1:16.268
Scenario I can view and print a PDF file stored in persistent /home/amnesia/Persistent
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 1:16.268
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/evince.feature:45:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I copy "/usr/share/cups/data/default-testpage.pdf" to "/home/amnesia/Persistent" as user "amnesia" 0.000
Then the file "/home/amnesia/Persistent/default-testpage.pdf" exists 0.000
When I open "/home/amnesia/Persistent/default-testpage.pdf" with Evince 0.000
Then I see "CupsTestPage.png" after at most 40 seconds 0.000
And I can print the current document to "/home/amnesia/Persistent/output.pdf" 0.000
After features/support/hooks.rb:330 6.261 
SCENARIO FAILED: 'I can view and print a PDF file stored in persistent /home/amnesia/Persistent' (at time 02:44:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:44:58_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:44:58_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:44:58_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:44:58_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.journal
After features/support/hooks.rb:100 0.000
Feature: Using Evince
Tags: @product @not_release_blocker
1:14.696
Scenario I cannot view a PDF file stored in persistent /home/amnesia/.gnupg
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 1:14.696
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/evince.feature:54:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I copy "/usr/share/cups/data/default-testpage.pdf" to "/home/amnesia/.gnupg" as user "amnesia" 0.000
Then the file "/home/amnesia/.gnupg/default-testpage.pdf" exists 0.000
Given I start monitoring the AppArmor log of "/usr/bin/evince" 0.000
And I try to open "/home/amnesia/.gnupg/default-testpage.pdf" with Evince 0.000
Then Evince tells me it cannot open "/home/amnesia/.gnupg/default-testpage.pdf" 0.000
And AppArmor has denied "/usr/bin/evince" from opening "/home/amnesia/.gnupg/default-testpage.pdf" 0.000
After features/support/hooks.rb:330 6.050 
SCENARIO FAILED: 'I cannot view a PDF file stored in persistent /home/amnesia/.gnupg' (at time 02:46:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:46:19_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:46:19_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:46:19_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:46:19_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.journal
After features/support/hooks.rb:100 0.000
Feature: GNOME is well-integrated into Tails
Tags: @product
1:14.401
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.003
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 1:14.401
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/gnome.feature:22:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
# Some apps (Tor Browser) only start when the network is plugged.
And the network is plugged 0.000
And Tor is ready 0.000
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 "gnome-terminal-server" 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 "Persistent Storage Backup" 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.797 
SCENARIO FAILED: 'I can launch various apps via GNOME Activities Overview' (at time 02:48:13)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:48:13_I_can_launch_various_apps_via_GNOME_Activities_Overview.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:48:13_I_can_launch_various_apps_via_GNOME_Activities_Overview.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:48:13_I_can_launch_various_apps_via_GNOME_Activities_Overview.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
1:15.710
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.174
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:15.536
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/hardware_failure.feature:29:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
features/hardware_failure.feature:23:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When Tails detects disk read failures on the SquashFS 0.000
Then I see a disk failure message 0.000
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:330 8.654 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:51:53)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:51:53_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:51:53_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:51:53_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
1:15.283
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.202
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:15.081
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/hardware_failure.feature:30:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
features/hardware_failure.feature:23:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When Tails detects disk read failures on the boot device 0.000
Then I see a disk failure message 0.000
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:330 8.738 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:53:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:53:17_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:53:17_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:53:17_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:53:17_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
1:16.802
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given a computer 0.448
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:16.353
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/hardware_failure.feature:31:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
features/hardware_failure.feature:23:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When Tails detects disk read failures on the boot device with a target error 0.000
Then I see a disk failure message 0.000
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:330 9.772 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:54:43)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:54:43_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:54:43_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/02:54:43_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product
30.071
Scenario Tails stores localization preferences in cleartext
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 without a persistent partition and stopped at Tails Greeter's login screen 14.935
And I set the language to Italian (it) 5.126
Then the language has been saved in cleartext storage 10.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/common_steps.rb:1758:in `/^the language has been saved in cleartext storage$/'
features/localization.feature:62:in `Then the language has been saved in cleartext storage'
When I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
Then the Greeter's language is set to Italian 0.000
After features/support/hooks.rb:330 5.534 
SCENARIO FAILED: 'Tails stores localization preferences in cleartext' (at time 03:47:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/03:47:28_Tails_stores_localization_preferences_in_cleartext.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/03:47:28_Tails_stores_localization_preferences_in_cleartext.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/03:47:28_Tails_stores_localization_preferences_in_cleartext.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/03:47:28_Tails_stores_localization_preferences_in_cleartext.journal
After features/support/hooks.rb:100 0.000
Feature: Packages are up-to-date
Tags: @source
6.815
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:532 0.000
Steps
Given I have the build manifest for the image under test 0.000
Then all packages listed in the build manifest are up-to-date 6.815
Command 
Command failed (pid 45353 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_5501-plaintext-locale-greeter/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_5501-plaintext-locale-greeter/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_5501-plaintext-locale-greeter/tmp/tails-amd64-5501-plaintext-locale-greeter@c56229ca92+stable@9c8c625ee5-20250624T0904Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_5501-plaintext-locale-greeter/tmp/tails-amd64-5501-plaintext-locale-greeter@c56229ca92+stable@9c8c625ee5-20250624T0904Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - ublock-origin (1.62.0+dfsg-1) to Debian trixie (1.62.0+dfsg-2)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_5501-plaintext-locale-greeter/features/support/helpers/misc_helpers.rb:321:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_5501-plaintext-locale-greeter/features/support/helpers/misc_helpers.rb:314:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_5501-plaintext-locale-greeter/features/support/helpers/misc_helpers.rb:314:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_5501-plaintext-locale-greeter/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:539 0.000
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
4:21.442
Scenario Creating a Persistent Storage
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 without a persistent partition and logged in 20.321
Then Tails is running from USB drive "__internal" 0.869
When I create a file in the Persistent directory 0.309
And I create a persistent partition with the default settings 38.941
Then the file I created was copied to the Persistent Storage 4.144
When I shutdown Tails and wait for the computer to power off 15.874
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:0.982
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:291: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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:291:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/persistence.feature:26:in `And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then persistence for "Persistent" is active 0.000
And the file I created in the Persistent directory exists 0.000
After features/support/hooks.rb:330 10.934 
SCENARIO FAILED: 'Creating a Persistent Storage' (at time 04:08:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:08:27_Creating_a_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:08:27_Creating_a_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:08:27_Creating_a_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:08:27_Creating_a_Persistent_Storage.journal
After features/support/hooks.rb:100 0.009
Feature: Tails persistence
Tags: @product
2:8.129
Scenario Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it
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 2:8.129
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:42:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then Tails is running from USB drive "__internal" 0.000
And all tps features are active 0.000
And all persistent directories have safe access rights 0.000
When I disable the first tps feature 0.000
Then all tps features but the first one are active 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then all tps features but the first one are active 0.000
After features/support/hooks.rb:330 8.738 
SCENARIO FAILED: 'Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it' (at time 04:12:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:12:23_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:12:23_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:12:23_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:12:23_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:36.764
Scenario Activating and deactivating Persistent Storage features
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:36.764
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:53:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then persistence for "Persistent" is active 0.000
And I create a file in the Persistent directory 0.000
Then the file I created was copied to the Persistent Storage 0.000
When I disable the first tps feature 0.000
Then persistence for "Persistent" is not active 0.000
And the Persistent directory does not exist 0.000
When I enable the first tps feature 0.000
Then persistence for "Persistent" is active 0.000
And the file I created in the Persistent directory exists 0.000
After features/support/hooks.rb:330 11.232 
SCENARIO FAILED: 'Activating and deactivating Persistent Storage features' (at time 04:14:08)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:14:08_Activating_and_deactivating_Persistent_Storage_features.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:14:08_Activating_and_deactivating_Persistent_Storage_features.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:14:08_Activating_and_deactivating_Persistent_Storage_features.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
2:14.249
Scenario Deleting data of a Persistent Storage feature
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:14.249
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:65:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then persistence for "Persistent" is active 0.000
When I create a file in the Persistent directory 0.000
And I disable the first tps feature 0.000
And I delete the data of the Persistent Folder feature 0.000
Then the file I created does not exist on the Persistent Storage 0.000
After features/support/hooks.rb:330 12.746 
SCENARIO FAILED: 'Deleting data of a Persistent Storage feature' (at time 04:16:34)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:16:34_Deleting_data_of_a_Persistent_Storage_feature.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:16:34_Deleting_data_of_a_Persistent_Storage_feature.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:16:34_Deleting_data_of_a_Persistent_Storage_feature.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:42.338
Scenario Writing files to a read/write-enabled persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.107
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:42.338
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:73:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And the network is plugged 0.000
And Tor is ready 0.000
And I take note of which tps features are available 0.000
When I write some files expected to persist 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: The next step succeeds (and the --debug output confirms that it's actually looking for the files) but will fail in a subsequent scenario restoring the same snapshot. This exactly what we want, but why does it work? What is guestfs's behaviour when qcow2 internal snapshots are involved?
Then only the expected files are present on the persistence partition on USB drive "__internal" 0.000
After features/support/hooks.rb:330 9.191 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition' (at time 04:18:30)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:18:30_Writing_files_to_a_read_write-enabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:18:30_Writing_files_to_a_read_write-enabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:18:30_Writing_files_to_a_read_write-enabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:51.990
Scenario Creating and using a persistent NetworkManager connection
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:51.990
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:83:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And the network is plugged 0.000
And Tor is ready 0.000
And I add a wired DHCP NetworkManager connection called "persistent-con-current" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
And I capture all network traffic 0.000
And the network is plugged 0.000
And Tor is ready 0.000
And I switch to the "persistent-con-current" NetworkManager connection 0.000
And the 1st network device has a spoofed MAC address configured 0.000
And no network device leaked the real MAC address 0.000
After features/support/hooks.rb:330 9.037 
SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 04:20:31)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:20:31_Creating_and_using_a_persistent_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:20:31_Creating_and_using_a_persistent_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:20:31_Creating_and_using_a_persistent_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:51.947
Scenario Persistent Greeter options
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 18.430
When I enable persistence 1:33.517
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704: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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
features/persistence.feature:104:in `When I enable persistence'
Then no persistent Greeter options were restored 0.000
When I set all Greeter options to non-default values 0.000
And I log in to a new session in German (de) after having activated the Persistent Storage 0.000
Then all Greeter options are set to non-default values 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
Given I enable persistence 0.000
Then persistent Greeter options were restored 0.000
When I log in to a new session after having activated the Persistent Storage 0.000
Then all Greeter options are set to non-default values 0.000
After features/support/hooks.rb:330 11.274 
SCENARIO FAILED: 'Persistent Greeter options' (at time 04:24:35)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:24:35_Persistent_Greeter_options.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:24:35_Persistent_Greeter_options.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:24:35_Persistent_Greeter_options.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:52.326
Scenario Changing the Persistent Storage passphrase
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.041
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:52.326
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:117:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
# 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 0.000
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 11.233 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 04:26:39)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:26:39_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:26:39_Changing_the_Persistent_Storage_passphrase.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:26:39_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:48.905
Scenario Dotfiles persistence
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:48.905
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:136:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When I write some dotfile expected to persist 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then the expected persistent dotfile is present in the filesystem 0.000
After features/support/hooks.rb:330 8.338 
SCENARIO FAILED: 'Dotfiles persistence' (at time 04:30:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:30:12_Dotfiles_persistence.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:30:12_Dotfiles_persistence.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:30:12_Dotfiles_persistence.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:30:12_Dotfiles_persistence.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:18.412
Scenario Feature activation fails
Before features/support/hooks.rb:266 0.011
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 18.036
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.090
When I try to enable persistence 0.284
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 1:0.001
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1724:in `/^the Welcome Screen tells me that the Persistent Folder feature couldn't be activated$/'
features/persistence.feature:146:in `Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated'
When I log in to a new session after having activated the Persistent Storage 0.000
And all notifications have disappeared 0.000
Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 0.000
And all tps features are enabled 0.000
And all tps features but the first one are active 0.000
After features/support/hooks.rb:330 13.567 
SCENARIO FAILED: 'Feature activation fails' (at time 04:31:39)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:31:39_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:31:39_Feature_activation_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:31:39_Feature_activation_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
7:53.709
Scenario LUKS header is automatically upgraded when unlocking the Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.025
Steps
Given I have started Tails without network from a USB drive with a LUKS 1 persistent partition and stopped at Tails Greeter's login screen 5:54.955
And I enable persistence 1:58.753
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704: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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
features/persistence.feature:155:in `And I enable persistence'
And I log in to a new session after having activated the Persistent Storage 0.000
Then a Tails persistence partition with LUKS version 2 and argon2id exists on USB drive "__internal" 0.000
And persistence is enabled 0.000
After features/support/hooks.rb:330 13.247 
SCENARIO FAILED: 'LUKS header is automatically upgraded when unlocking the Persistent Storage' (at time 04:39:48)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:39:48_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:39:48_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:39:48_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
2:11.404
Scenario LUKS backup header is restored if something goes wrong during upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Steps
Given I have started Tails without network from a USB drive with a LUKS 1 persistent partition and stopped at Tails Greeter's login screen 1:8.054
And I enable persistence but something goes wrong during the LUKS header upgrade 1:3.349
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:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:714:in `/^I enable persistence but something goes wrong during the LUKS header upgrade$/'
features/persistence.feature:162:in `And I enable persistence but something goes wrong during the LUKS header upgrade'
Then the Tails persistence partition on USB drive "__internal" still has LUKS version 1 0.000
After features/support/hooks.rb:330 5.669 
SCENARIO FAILED: 'LUKS backup header is restored if something goes wrong during upgrade' (at time 04:42:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:42:12_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:42:12_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:42:12_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:42:12_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
3:9.857
Scenario Automatic filesystem repair
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 1:9.536
And I corrupt the Persistent Storage filesystem on USB drive "__internal" 12.841
When I enable persistence 1:47.479
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704: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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
features/persistence.feature:168:in `When I enable persistence'
Then the filesystem of the Persistent Storage was repaired 0.000
And persistence is successfully enabled 0.000
After features/support/hooks.rb:330 14.746 
SCENARIO FAILED: 'Automatic filesystem repair' (at time 04:45:31)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:45:31_Automatic_filesystem_repair.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:45:31_Automatic_filesystem_repair.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:45:31_Automatic_filesystem_repair.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:39.252
Scenario Manual filesystem repair is successful
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 21.166
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 17.559
When I try to enable persistence 0.518
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.008
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 15.593 
SCENARIO FAILED: 'Manual filesystem repair is successful' (at time 04:47:27)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:47:27_Manual_filesystem_repair_is_successful.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:47:27_Manual_filesystem_repair_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:47:27_Manual_filesystem_repair_is_successful.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:36.320
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 34.457
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.330
When I try to enable persistence 1.519
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.012
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.044 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 04:49:15)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:49:15_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:49:15_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:49:15_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:35.096
Scenario Filesystem and I/O errors
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 17.227
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 15.605
And Tails detects disk read failures on the boot device 1.820
When I try to enable persistence 0.438
Then the Welcome Screen tells me that my hardware is probably failing 1:0.003
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:1835:in `/^the Welcome Screen tells me that my hardware is probably failing$/'
features/persistence.feature:210:in `Then the Welcome Screen tells me that my hardware is probably failing'
When I log in to a new session 0.000
And all notifications have disappeared 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 14.330 
SCENARIO FAILED: 'Filesystem and I/O errors' (at time 04:51:06)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:51:06_Filesystem_and_I_O_errors.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:51:06_Filesystem_and_I_O_errors.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:51:06_Filesystem_and_I_O_errors.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
2:11.401
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 48.571
And I create a persistent partition with the default settings 52.792
Then the "TorConfiguration" tps feature is not enabled 3.790
When the network is plugged 0.091
And the Tor Connection Assistant autostarts 15.353
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 10.800
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:628:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/persistent_tor_bridges.feature:13:in `And I configure some persistent obfs4 bridges in the Tor Connection Assistant'
And I wait until Tor is ready 0.000
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Using Persistent 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 click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 6.908 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 04:53:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:53:30_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:53:30_Using_Persistent_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:53:30_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:53:30_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
1:50.288
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 31.132
And I create a persistent partition with the default settings 50.942
Then the "TorConfiguration" tps feature is not enabled 3.923
When the network is plugged 0.096
And the Tor Connection Assistant autostarts 14.807
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 9.385
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:628:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/persistent_tor_bridges.feature:13:in `And I configure some persistent obfs4 bridges in the Tor Connection Assistant'
And I wait until Tor is ready 0.000
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 7.959 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 04:55:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:55:32_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:55:32_Disabling_persistence_of_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:55:32_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/04:55:32_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product @not_release_blocker
1:14.023
Scenario No unexpected network services
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:14.023
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/sane_defaults.feature:12:in `Given I have started Tails from DVD and logged in and the network is connected'
Then no unexpected services are listening for network connections 0.000
After features/support/hooks.rb:330 7.713 
SCENARIO FAILED: 'No unexpected network services' (at time 05:03:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:03:32_No_unexpected_network_services.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:03:32_No_unexpected_network_services.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:03:32_No_unexpected_network_services.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:03:32_No_unexpected_network_services.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
1:13.930
Scenario No unexpected error messages in the journal after booting from DVD
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD without network and logged in 1:13.930
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/sane_defaults.feature:20:in `Given I have started Tails from DVD without network and logged in'
Then there are no unexpected messages of priority "err" or higher in the journal 0.000
After features/support/hooks.rb:330 6.326 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from DVD' (at time 05:06:11)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:06:11_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:06:11_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:06:11_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:06:11_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
2:30.164
Scenario No unexpected error messages in the journal after booting from USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:30.164
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/sane_defaults.feature:24:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then there are no unexpected messages of priority "err" or higher in the journal 0.000
After features/support/hooks.rb:330 15.168 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 05:08:51)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:08:51_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:08:51_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:08:51_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal
After features/support/hooks.rb:100 0.000
Feature: The Tor enforcement is effective
Tags: @product
1:18.619
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.016
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:18.619
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/tor_enforcement.feature:16:in `Given I have started Tails from DVD and logged in and the network is connected'
And I capture all network traffic 0.000
When I successfully start the Unsafe Browser 0.000
And I open the Tails homepage in the Unsafe Browser 0.000
And the Tails homepage loads in the Unsafe Browser 0.000
Then the firewall leak detector has detected leaks 0.000
After features/support/hooks.rb:330 5.773 
SCENARIO FAILED: 'Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector' (at time 05:28:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:28:14_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:28:14_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:28:14_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:28:14_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:100 0.000
Feature: The Tor enforcement is effective
Tags: @product
1:11.543
Scenario Anti test: Detecting UDP leaks of DNS lookups with the firewall leak detector
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:11.543
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/tor_enforcement.feature:31:in `Given I have started Tails from DVD and logged in and the network is connected'
And I capture all network traffic 0.000
And I disable Tails' firewall 0.000
When I do a UDP DNS lookup of "torproject.org" 0.000
Then the firewall leak detector has detected leaks 0.000
After features/support/hooks.rb:330 5.787 
SCENARIO FAILED: 'Anti test: Detecting UDP leaks of DNS lookups with the firewall leak detector' (at time 05:30:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:30:12_Anti_test:_Detecting_UDP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:30:12_Anti_test:_Detecting_UDP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:30:12_Anti_test:_Detecting_UDP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:30:12_Anti_test:_Detecting_UDP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:5.818
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.197
Steps
Given I have started Tails from DVD and logged in and the network is connected 22.396
And a web server is running on the LAN 3.272
And I capture all network traffic 0.009
When I start the Tor Browser 40.139
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:11:in `When I start the Tor Browser'
And the Tor Browser loads the startup page 0.000
And I open a page on the LAN web server in the Tor Browser 0.000
Then the Tor Browser shows the "Unable to connect" error 0.000
And no traffic was sent to the web server on the LAN 0.000
After features/support/hooks.rb:330 6.163 
SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 05:40:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:40:16_The_Tor_Browser_cannot_access_the_LAN.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:40:16_The_Tor_Browser_cannot_access_the_LAN.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:40:16_The_Tor_Browser_cannot_access_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:40:16_The_Tor_Browser_cannot_access_the_LAN.journal
After features/support/hooks.rb:100 0.033
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
1:14.403
Scenario The Downloads directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:507 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 27.456
Then the live user's Downloads directory exists 0.445
And there is a GNOME bookmark for the Downloads directory 5.783
When I start the Tor Browser 40.717
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:22:in `When I start the Tor Browser'
And the Tor Browser loads the startup page 0.000
Then I can save the current page as "index.html" to the Downloads directory 0.000
And I can print the current page as "output.pdf" to the Downloads directory 0.000
After features/support/hooks.rb:515 0.039
After features/support/hooks.rb:330 8.305 
SCENARIO FAILED: 'The Downloads directory is usable in Tor Browser' (at time 05:41:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:41:37_The_Downloads_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:41:37_The_Downloads_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:41:37_The_Downloads_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:41:37_The_Downloads_directory_is_usable_in_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:50.753
Scenario I can view a file stored in "~/Downloads" but not in ~/.gnupg
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given I have started Tails from DVD and logged in and the network is connected 27.234
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/Downloads/synaptic.html" as user "amnesia" 0.316
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/.gnupg/synaptic.html" as user "amnesia" 0.155
And I copy "/usr/share/synaptic/html/index.html" to "/tmp/synaptic.html" as user "amnesia" 0.182
Then the file "/home/amnesia/.gnupg/synaptic.html" exists 0.172
And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.263
And the file "/live/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.408
And the file "/tmp/synaptic.html" exists 0.246
Given I start monitoring the AppArmor log of "torbrowser_firefox" 0.567
When I start the Tor Browser 44.970
And the Tor Browser loads the startup page 1.232
And I open the address "file:///home/amnesia/Downloads/synaptic.html" in the Tor Browser 26.930
Then I see "TorBrowserSynapticManual.png" after at most 5 seconds 8.071
cannot 
cannot find TorBrowserSynapticManual.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:759:in `/^I (do not )?see "([^"]*)" after at most (\d+) seconds$/'
features/torified_browsing.feature:62:in `Then I see "TorBrowserSynapticManual.png" after at most 5 seconds'
And AppArmor has not denied "torbrowser_firefox" from opening "/home/amnesia/Downloads/synaptic.html" 0.000
When I open the address "file:///home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
When I open the address "file:///lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
When I open the address "file:///live/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
When I open the address "file:///tmp/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
After features/support/hooks.rb:330 11.314 
SCENARIO FAILED: 'I can view a file stored in "~/Downloads" but not in ~/.gnupg' (at time 05:51:13)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:51:13_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:51:13_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:51:13_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:10.855
Scenario The Tor Browser uses TBB's shared libraries
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.208
Steps
Given I have started Tails from DVD and logged in and the network is connected 26.647
When I start the Tor Browser 44.207
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:75:in `When I start the Tor Browser'
Then the Tor Browser uses all expected TBB shared libraries 0.000
After features/support/hooks.rb:330 6.797 
SCENARIO FAILED: 'The Tor Browser uses TBB's shared libraries' (at time 05:52:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:52:36_The_Tor_Browser_uses_TBB_s_shared_libraries.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:52:36_The_Tor_Browser_uses_TBB_s_shared_libraries.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:52:36_The_Tor_Browser_uses_TBB_s_shared_libraries.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:52:36_The_Tor_Browser_uses_TBB_s_shared_libraries.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:3.572
Scenario The Tor Browser's circuit view feature works as expected
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.102
Steps
Given I have started Tails from DVD and logged in and the network is connected 23.821
When I start the Tor Browser 39.751
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:92:in `When I start the Tor Browser'
And the Tor Browser loads the startup page 0.000
Then Tor Browser's circuit view is working 0.000
After features/support/hooks.rb:330 6.368 
SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 05:55:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:55:56_The_Tor_Browser_s_circuit_view_feature_works_as_expected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:55:56_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:55:56_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:55:56_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:18.602
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:18.602
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:139: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/torified_browsing.feature:106:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And the network is plugged 0.000
And I successfully configure Tor 0.000
And available upgrades have been checked 0.000
And all notifications have disappeared 0.000
And there is a GNOME bookmark for the Persistent directory 0.000
When I start the Tor Browser 0.000
And I download some file in the Tor Browser to the Persistent directory 0.000
Then the file is saved to the Persistent directory 0.000
When I open the address "https://tails.net/about" in the Tor Browser 0.000
Then "Tails - How Tails works" has loaded in the Tor Browser 0.000
And I can print the current page as "output.pdf" to the Persistent directory 0.000
After features/support/hooks.rb:330 5.794 
SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 05:59:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:59:35_The_Persistent_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:59:35_The_Persistent_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:59:35_The_Persistent_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/05:59:35_The_Persistent_directory_is_usable_in_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
2:8.139
Scenario Persistent browser bookmarks
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:8.139
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:696: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/usb.rb:694:in `block in <top (required)>'
./features/step_definitions/usb.rb:704:in `block in <top (required)>'
./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:173:in `block (2 levels) 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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/torified_browsing.feature:134:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And all tps features are active 0.000
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories have safe access rights 0.000
When I start the Tor Browser in offline mode 0.000
And I add a bookmark to eff.org in the Tor Browser 0.000
And I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I log in to a new session 0.000
And all notifications have disappeared 0.000
And I start the Tor Browser in offline mode 0.000
Then the Tor Browser has a bookmark to eff.org 0.000
After features/support/hooks.rb:330 6.552 
SCENARIO FAILED: 'Persistent browser bookmarks' (at time 06:10:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:10:51_Persistent_browser_bookmarks.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:10:51_Persistent_browser_bookmarks.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:10:51_Persistent_browser_bookmarks.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:10:51_Persistent_browser_bookmarks.journal
After features/support/hooks.rb:100 0.000
Feature: Using Totem
Tags: @product
1:14.592
Scenario Watching a MP4 video stored on the non-persistent filesystem
Steps
Given I have started Tails from DVD without network and logged in 1:14.592
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/totem.feature:12:in `Given I have started Tails from DVD without network and logged in'
And I plug and mount a USB drive containing sample videos 0.000
And I copy the sample videos to "/home/amnesia" as user "amnesia" 0.000
And the file "/home/amnesia/video.mp4" exists 0.000
Given I start monitoring the AppArmor log of "/usr/bin/totem" 0.000
When I open "/home/amnesia/video.mp4" with Totem 0.000
Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 0.000
And AppArmor has not denied "/usr/bin/totem" from opening "/home/amnesia/video.mp4" 0.000
Given I close Totem 0.000
And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.000
And the file "/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 "/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 "/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 5.653 
SCENARIO FAILED: 'Watching a MP4 video stored on the non-persistent filesystem' (at time 06:15:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:15:12_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:15:12_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:15:12_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:15:12_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.journal
After features/support/hooks.rb:100 0.000
Feature: Using Totem
Tags: @product
2:8.859
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 2:8.859
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:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./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:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/totem.feature:55:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I plug and mount a USB drive containing sample videos 0.000
And I copy the sample videos to "/home/amnesia/Persistent" as user "amnesia" 0.000
When I open "/home/amnesia/Persistent/video.mp4" with Totem 0.000
Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 0.000
Given I close Totem 0.000
And I start monitoring the AppArmor log of "/usr/bin/totem" 0.000
And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.000
When I try to open "/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 "/home/amnesia/.gnupg/video.mp4" 0.000
After features/support/hooks.rb:330 9.146 
SCENARIO FAILED: 'Watching MP4 videos stored on the persistent volume should work as expected given our AppArmor confinement' (at time 06:19:11)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:19:11_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:19:11_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:19:11_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:19:11_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 @doc
1:14.312
Scenario Starting the Unsafe Browser works as it should
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:14.312
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/unsafe_browser.feature:25:in `Given I have started Tails from DVD and logged in and the network is connected'
When I successfully start the Unsafe Browser 0.000
Then the Unsafe Browser runs as the expected user 0.000
And the Unsafe Browser has a red theme 0.000
And the Unsafe Browser shows a warning as its start page 0.000
And the Unsafe Browser has no add-ons installed 0.000
And the Unsafe Browser has no bookmarks 0.000
And the Unsafe Browser uses all expected TBB shared libraries 0.000
After features/support/hooks.rb:330 6.153 
SCENARIO FAILED: 'Starting the Unsafe Browser works as it should' (at time 06:23:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:23:51_Starting_the_Unsafe_Browser_works_as_it_should.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:23:51_Starting_the_Unsafe_Browser_works_as_it_should.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:23:51_Starting_the_Unsafe_Browser_works_as_it_should.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:23:51_Starting_the_Unsafe_Browser_works_as_it_should.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product @not_release_blocker
1:9.177
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.025
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:9.177
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/unsafe_browser.feature:51:in `Given I have started Tails from DVD and logged in and the network is connected'
When I successfully start the Unsafe Browser 0.000
# 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 0.000
And I try to start the Unsafe Browser 0.000
Then I see a warning about another instance already running 0.000
After features/support/hooks.rb:330 6.784 
SCENARIO FAILED: 'Starting a second instance of the Unsafe Browser results in an error message being shown' (at time 06:28:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:28:10_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:28:10_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:28:10_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:28:10_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
1:19.830
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.037
Steps
Given I have started Tails from DVD without network and logged in 1:19.830
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/veracrypt.feature:8:in `Given I have started Tails from DVD without network and logged in'
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
0.000
Scenario Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume
Steps
When I plug a USB drive containing a basic VeraCrypt volume 0.000
And I cancel the GNOME authentication prompt 0.000
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 0.000
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt volume 0.000
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 6.802 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume' (at time 06:35:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:35:31_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:35:31_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:35:31_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:35:31_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
1:0.984
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 48.084
And I unlock and mount this VeraCrypt file container with GNOME Disks 12.899
The 
The Dogtail init script raised: ActionNotSupported: Cannot do 'activate' action on [DEAD]
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:346:in `call_tree_node_method'
./features/support/helpers/dogtail.rb:350:in `doActionNamed'
./features/support/helpers/dogtail.rb:364:in `activate'
./features/step_definitions/veracrypt.rb:240:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:68:in `And I unlock and mount this VeraCrypt file container with GNOME Disks'
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 12.613 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 06:45:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:45:31_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:45:31_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:45:31_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_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:45:31_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.015
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
1:28.992
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 34.775
And I unlock and mount this VeraCrypt file container with GNOME Disks 40.480
And I open this VeraCrypt volume in GNOME Files 13.736
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: "org.gnome.Nautilus" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/veracrypt.rb:313:in `new'
./features/step_definitions/veracrypt.rb:313:in `nautilus_with_open_veracrypt_volume'
./features/step_definitions/veracrypt.rb:320:in `/^I open this VeraCrypt volume in GNOME Files$/'
features/veracrypt.feature:85:in `And I open this VeraCrypt volume in GNOME Files'
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 6.965 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM' (at time 06:49:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:49:55_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:49:55_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:49:55_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:49:55_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000
Feature: I can report a bug with WhisperBack
Tags: @product
23.233
Scenario WhisperBack has access to debugging information
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Steps
Given I have started Tails from DVD without network and logged in 12.493
When I start "WhisperBack" via GNOME Activities Overview 10.740
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:1141:in `/^I start "([^"]+)" via GNOME Activities Overview$/'
features/whisperback.feature:18:in `When I start "WhisperBack" via GNOME Activities Overview'
Then WhisperBack has debugging information 0.000
After features/support/hooks.rb:330 5.544 
SCENARIO FAILED: 'WhisperBack has access to debugging information' (at time 06:51:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:51:15_WhisperBack_has_access_to_debugging_information.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:51:15_WhisperBack_has_access_to_debugging_information.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:51:15_WhisperBack_has_access_to_debugging_information.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/35/artifact/build-artifacts/06:51:15_WhisperBack_has_access_to_debugging_information.journal
After features/support/hooks.rb:100 0.000