Project Number Date
test_Tails_ISO_test-suite-options 1 17 Jun 2025, 01:12

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:30.033
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 9.120
And I wait until Tor is ready 3.681
When I disconnect the network through GNOME 3.894
And I connect the network through GNOME 4.186
Then the Tor Connection Assistant autostarts 2.397
And the Tor Connection Assistant connects to Tor 6.428
And I wait until Tor is ready 5:0.323
Time 
Time syncing failed (HtpdateError)
./features/step_definitions/common_steps.rb:711:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:709:in `/^the time has synced$/'
./features/step_definitions/common_steps.rb:662:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:89:in `And I wait until Tor is ready'
And Tor is using the same configuration as before 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 6.102 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:35:23)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/00:35:23_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/00:35:23_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log
Htpdate logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/00:35:23_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/00:35:23_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/00:35:23_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/00:35:23_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/00:35:23_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.059
Feature: Backing up the persistent storage
Tags: @product
1:54.951
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.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 26.755
# 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 15.038
And I clone USB drive "__internal" to a temporary USB drive "backup" 2.381
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.696
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.029
When I start Tails' custom backup tool 6.868
Then the backup tool displays "Plug in your backup Tails USB stick" 2.180
When I plug USB drive "backup" 5.429
And I give the Persistent Storage on drive "backup" its own UUID 0.198
And I click "Retry" in the backup tool 1.185
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.389
When I click "Back Up" in the backup tool 1.179
And I enter my persistent storage passphrase into the polkit prompt 4.617
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 30.001
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/backup.rb:6:in `/^the backup tool displays "([^"]+)"$/'
features/backup.feature:22:in `Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!"'
# The backup tool ejects the drive, so we have to replug it
When I unplug USB drive "backup" 0.000
And I plug USB drive "backup" 0.000
Then the USB drive "backup" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:330 7.231 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 02:30:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/02:30:52_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_test-suite-options/1/artifact/build-artifacts/02:30:52_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/02:30:52_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/02:30:52_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.167
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:33.468
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.028
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 41.752
When I log in to a new session in Italian (it) 57.410
Then the keyboard layout is set to "it" 0.296
When the network is plugged 0.104
And Tor is ready 31.257
Then I successfully start the Unsafe Browser 37.853
And I kill the Unsafe Browser 8.341
When I enable the screen keyboard 0.175
Then the screen keyboard works in Tor Browser 36.276
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/step_definitions/browser.rb:411:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:52:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 13.027 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#6)' (at time 03:49:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/03:49:18_Tails_is_localized_for_every_tier-1_language,_Examples___6_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/03:49:18_Tails_is_localized_for_every_tier-1_language,_Examples___6_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/03:49:18_Tails_is_localized_for_every_tier-1_language,_Examples___6_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/03:49:18_Tails_is_localized_for_every_tier-1_language,_Examples___6_.journal
After features/support/hooks.rb:100 0.004
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
4:53.081
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 19.374
When I log in to a new session in Spanish (es) 59.724
Then the keyboard layout is set to "es" 0.223
When the network is plugged 0.145
And Tor is ready 34.821
Then I successfully start the Unsafe Browser 24.846
And I kill the Unsafe Browser 6.864
When I enable the screen keyboard 1.255
Then the screen keyboard works in Tor Browser 1:6.796
And DuckDuckGo is the default search engine 40.791
And I kill the Tor Browser 6.682
And the screen keyboard works in Thunderbird 31.552
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: "Thunderbird" application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:1047:in `new'
./features/step_definitions/common_steps.rb:1047:in `block in launch_app'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:1046:in `launch_app'
./features/step_definitions/common_steps.rb:1093:in `launch_thunderbird'
./features/step_definitions/thunderbird.rb:33:in `block in <top (required)>'
./features/step_definitions/thunderbird.rb:212:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:1046:in `launch_app'
./features/step_definitions/common_steps.rb:1093:in `launch_thunderbird'
./features/step_definitions/thunderbird.rb:33:in `/^I start Thunderbird$/'
./features/step_definitions/thunderbird.rb:212:in `/^the screen keyboard works in Thunderbird$/'
features/localization.feature:56:in `And the screen keyboard works in Thunderbird'
features/localization.feature:33:in `And the screen keyboard works in Thunderbird'
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 6.563 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#10)' (at time 04:08:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:08:36_Tails_is_localized_for_every_tier-1_language,_Examples___10_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:08:36_Tails_is_localized_for_every_tier-1_language,_Examples___10_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:08:36_Tails_is_localized_for_every_tier-1_language,_Examples___10_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:08:36_Tails_is_localized_for_every_tier-1_language,_Examples___10_.journal
After features/support/hooks.rb:100 0.000
Feature: Networking
Tags: @product
1:26.195
Scenario No initial network
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.162
Steps
Given I have started Tails from DVD without network and logged in 14.054
And I wait between 30 and 60 seconds 1:0.059 
Slept for 60 seconds
Then the Tor Status icon tells me that Tor is not usable 12.081
cannot 
cannot find TorStatusNotUsable.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/checks.rb:319:in `/^the Tor Status icon tells me that Tor is( not)? usable$/'
features/networking.feature:7:in `Then the Tor Status icon tells me that Tor is not usable'
When the network is plugged 0.000
Then I successfully configure Tor 0.000
And the Tor Status icon tells me that Tor is usable 0.000
And all notifications have disappeared 0.000
And the time has synced 0.000
After features/support/hooks.rb:330 5.875 
SCENARIO FAILED: 'No initial network' (at time 04:27:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:27:15_No_initial_network.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:27:15_No_initial_network.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:27:15_No_initial_network.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:27:15_No_initial_network.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
58.630
Scenario Booting Tails from a USB drive with a disabled persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 47.222
When I log in to a new session without activating the Persistent Storage 11.408
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/common_steps.rb:519:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/persistence.feature:14:in `When I log in to a new session without activating the Persistent Storage'
Then Tails is running from USB drive "__internal" 0.000
And persistence is disabled 0.000
But a Tails persistence partition exists on USB drive "__internal" 0.000
After features/support/hooks.rb:330 5.473 
SCENARIO FAILED: 'Booting Tails from a USB drive with a disabled persistent partition' (at time 04:37:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:37:34_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:37:34_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:37:34_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:37:34_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:39.463
Scenario Creating a Persistent Storage when system is low on memory
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 1:39.463
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ without\ a\ persistent\ partition\ and\ logged\ in$/'
features/persistence.feature:31:in `Given I have started Tails without network from a USB drive without a persistent partition and logged in'
And the system is very low on memory 0.000
When I create a file in the Persistent directory 0.000
When I try to create a persistent partition 0.000
Then The Persistent Storage app shows the error message "Not enough memory to create Persistent Storage" 0.000
When I close the Persistent Storage app 0.000
And I free up some memory 0.000
And I create a persistent partition with the default settings 0.000
Then the file I created was copied to the Persistent Storage 0.000
After features/support/hooks.rb:330 5.881 
SCENARIO FAILED: 'Creating a Persistent Storage when system is low on memory' (at time 04:45:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:45:35_Creating_a_Persistent_Storage_when_system_is_low_on_memory.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:45:35_Creating_a_Persistent_Storage_when_system_is_low_on_memory.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:45:35_Creating_a_Persistent_Storage_when_system_is_low_on_memory.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:45:35_Creating_a_Persistent_Storage_when_system_is_low_on_memory.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:32.502
Scenario Activating and deactivating Persistent Storage features
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:32.502
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/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 6.698 
SCENARIO FAILED: 'Activating and deactivating Persistent Storage features' (at time 04:52:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:52:56_Activating_and_deactivating_Persistent_Storage_features.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:52:56_Activating_and_deactivating_Persistent_Storage_features.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:52:56_Activating_and_deactivating_Persistent_Storage_features.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:52:56_Activating_and_deactivating_Persistent_Storage_features.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:23.089
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.068
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:23.089
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/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 6.625 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition' (at time 04:55:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:55:15_Writing_files_to_a_read_write-enabled_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:55:15_Writing_files_to_a_read_write-enabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:55:15_Writing_files_to_a_read_write-enabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/04:55:15_Writing_files_to_a_read_write-enabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:25.915
Scenario Persistent Greeter options
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.202
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:25.915
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ and\ stopped\ at\ Tails\ Greeter's\ login\ screen$/'
features/persistence.feature:103:in `Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen'
When I enable persistence 0.000
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 5.481 
SCENARIO FAILED: 'Persistent Greeter options' (at time 05:05:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/05:05:13_Persistent_Greeter_options.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/05:05:13_Persistent_Greeter_options.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/05:05:13_Persistent_Greeter_options.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/05:05:13_Persistent_Greeter_options.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:39.278
Scenario Changing the Persistent Storage passphrase
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.821
# Note that if anything fails after the passphrase was changed and
# before it's changed back below, subsequent scenarios might fail
# because the Persistent Storage doesn't have the expected passphrase.
When I change the passphrase of the Persistent Storage 1:14.456
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:475:in `/^I change the passphrase of the Persistent Storage( back to the original)?$/'
features/persistence.feature:121:in `When I change the passphrase of the Persistent Storage'
And I shutdown Tails and wait for the computer to power off 0.000
Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 0.000
And I change the passphrase of the Persistent Storage back to the original 0.000
After features/support/hooks.rb:330 16.146 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 05:06:59)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/05:06:59_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/05:06:59_Changing_the_Persistent_Storage_passphrase.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/05:06:59_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:24.011
Scenario Feature activation fails
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 persistent partition and stopped at Tails Greeter's login screen 23.407
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.092
When I try to enable persistence 0.314
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 1:0.196
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 21.889 
SCENARIO FAILED: 'Feature activation fails' (at time 05:15:54)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/05:15:54_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/05:15:54_Feature_activation_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/05:15:54_Feature_activation_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
2:56.313
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.013
Steps
Given I have started Tails from DVD and logged in and the network is connected 35.388
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/Downloads/synaptic.html" as user "amnesia" 0.206
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/.gnupg/synaptic.html" as user "amnesia" 0.128
And I copy "/usr/share/synaptic/html/index.html" to "/tmp/synaptic.html" as user "amnesia" 0.124
Then the file "/home/amnesia/.gnupg/synaptic.html" exists 0.110
And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.129
And the file "/live/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.259
And the file "/tmp/synaptic.html" exists 0.168
Given I start monitoring the AppArmor log of "torbrowser_firefox" 0.345
When I start the Tor Browser 41.725
And the Tor Browser loads the startup page 1.368
And I open the address "file:///home/amnesia/Downloads/synaptic.html" in the Tor Browser 19.788
Then I see "TorBrowserSynapticManual.png" after at most 5 seconds 0.587
And AppArmor has not denied "torbrowser_firefox" from opening "/home/amnesia/Downloads/synaptic.html" 1.195
When I open the address "file:///home/amnesia/.gnupg/synaptic.html" in the Tor Browser 17.327
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.560
When I open the address "file:///lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 18.401
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.734
When I open the address "file:///live/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 15.562
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 3.147
When I open the address "file:///tmp/synaptic.html" in the Tor Browser 8.037
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 11.013
can 
can still find TorBrowserSynapticManual.png on the screen (FindFailed)
./features/support/helpers/screen.rb:207:in `rescue in wait_vanish'
./features/support/helpers/screen.rb:192:in `wait_vanish'
./features/step_definitions/common_steps.rb:757:in `/^I (do not )?see "([^"]*)" after at most (\d+) seconds$/'
features/torified_browsing.feature:71:in `Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds'
After features/support/hooks.rb:330 5.325 
SCENARIO FAILED: 'I can view a file stored in "~/Downloads" but not in ~/.gnupg' (at time 06:25:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/06:25:54_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/06:25:54_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/06:25:54_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/06:25:54_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 @check_tor_leaks
1:14.187
Scenario The Tor Browser's "New identity" feature works as expected
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Before features/support/hooks.rb:507 0.011
Steps
Given I have started Tails from DVD and logged in and the network is connected 31.605
When I start the Tor Browser 42.581
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:81:in `When I start the Tor Browser'
And the Tor Browser loads the startup page 0.000
When I open the address "https://example.com/" in the Tor Browser 0.000
Then Tor Browser displays a "Example Domain" heading on the "Example Domain" page 0.000
And the Tor Browser has 2 tabs open 0.000
When I request a new identity in Tor Browser 0.000
Then the Tor Browser loads the startup page 0.000
And the Tor Browser has 1 tab open 0.000
After features/support/hooks.rb:515 0.059
After features/support/hooks.rb:330 15.398 
SCENARIO FAILED: 'The Tor Browser's "New identity" feature works as expected' (at time 06:28:38)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/06:28:38_The_Tor_Browser_s__New_identity__feature_works_as_expected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/06:28:38_The_Tor_Browser_s__New_identity__feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/06:28:38_The_Tor_Browser_s__New_identity__feature_works_as_expected.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:14.358
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Steps
Given I have started Tails from DVD without network and logged in 1:14.358
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/torified_browsing.feature:128:in `Given I have started Tails from DVD without network and logged in'
features/torified_browsing.feature:120:in `Given I have started Tails from DVD without network and logged in'
Then the live user's Downloads directory exists 0.000
And there is a GNOME bookmark for the Downloads directory 0.000
Then I start the Tor Browser in offline mode 0.000
And I can save the current page as "index.html" to the Downloads GNOME bookmark 0.000
After features/support/hooks.rb:330 5.823 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#2)' (at time 06:39:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/06:39:32_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/06:39:32_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/06:39:32_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/06:39:32_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:12.743
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails from DVD without network and logged in 1:12.743
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/torified_browsing.feature:129:in `Given I have started Tails from DVD without network and logged in'
features/torified_browsing.feature:120:in `Given I have started Tails from DVD without network and logged in'
Then the live user's Music directory exists 0.000
And there is a GNOME bookmark for the Music directory 0.000
Then I start the Tor Browser in offline mode 0.000
And I can save the current page as "index.html" to the Music GNOME bookmark 0.000
After features/support/hooks.rb:330 6.643 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#3)' (at time 06:40:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/06:40:53_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/06:40:53_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/06:40:53_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/06:40:53_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
1:10.615
Scenario Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 46.293
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 11.335
And I open this VeraCrypt volume in GNOME Files 12.987
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:41: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 7.539 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container' (at time 07:23:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/07:23:16_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/07:23:16_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/07:23:16_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/07:23:16_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.051
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
1:2.565
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.960
And I unlock and mount this VeraCrypt file container with GNOME Disks 13.605
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 8.093 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 07:27:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/07:27:51_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_test-suite-options/1/artifact/build-artifacts/07:27:51_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/07:27:51_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_test-suite-options/1/artifact/build-artifacts/07:27:51_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.021
Feature: Using VeraCrypt encrypted volumes
1:13.463
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails from DVD without network and logged in 1:13.463
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 GNOME Disks to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 0.000
And I unlock and mount this VeraCrypt file container with GNOME Disks 0.000
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.398 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 07:29:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/07:29:13_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/07:29:13_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/07:29:13_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/1/artifact/build-artifacts/07:29:13_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.000