Project Number Date
test_Tails_ISO_test-snapshot-restore-improvements 4 21 Aug 2026, 22:02

Failures Overview

The following summary displays scenarios that failed.

Feature: Root access control enforcement
Tags: @product
1:33.728
Scenario I can perform administrative tasks if I have set up an administration password in the Welcome Screen
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given I have started Tails from DVD without network and logged in with an administration password 1:11.114
And running a command as root with pkexec requires PolicyKit administrator privileges 0.082
Then I can run a command as root with sudo 0.091
Then I can run a command as root with pkexec 22.441
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:1031:in `/^I run "([^"]+)" in Console$/'
./features/step_definitions/root_access_control.rb:49:in `/^I can run a command as root with pkexec$/'
features/root_access_control.feature:10:in `Then I can run a command as root with pkexec'
After features/support/hooks.rb:339 5.344 
SCENARIO FAILED: 'I can perform administrative tasks if I have set up an administration password in the Welcome Screen' (at time 00:13:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:13:41_I_can_perform_administrative_tasks_if_I_have_set_up_an_administration_password_in_the_Welcome_Screen.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:13:41_I_can_perform_administrative_tasks_if_I_have_set_up_an_administration_password_in_the_Welcome_Screen.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:13:41_I_can_perform_administrative_tasks_if_I_have_set_up_an_administration_password_in_the_Welcome_Screen.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:13:41_I_can_perform_administrative_tasks_if_I_have_set_up_an_administration_password_in_the_Welcome_Screen.journal
After features/support/hooks.rb:108 0.063
Feature: Time syncing
Tags: @product @check_tor_leaks
19.060
Scenario On a clock with host's time, Tor Connection works even if time sync fails
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.001
Steps
Given I have started Tails from DVD without network and logged in 3.595
And I make sure time sync before Tor connects times out 1.076
When the network is plugged 0.024
And I successfully configure Tor 14.365
The 
The Dogtail init script raised: SearchError: descendant of [application | Tor Connection]: child with name='Connect to Tor automatically' roleName='radio button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/tor.rb:533:in `tca_configure'
./features/step_definitions/tor.rb:553:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:718:in `/^I successfully configure Tor$/'
features/time_syncing.feature:59:in `And I successfully configure Tor'
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:535 0.034
After features/support/hooks.rb:339 4.861 
SCENARIO FAILED: 'On a clock with host's time, Tor Connection works even if time sync fails' (at time 00:19:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:19:03_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:19:03_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:19:03_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:19:03_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.journal
After features/support/hooks.rb:108 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
19.082
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:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.001
Steps
Given I have started Tails from DVD without network and logged in 3.444
When I bump the system time with "+8 hours +15 minutes" 0.167
And all notifications have disappeared 3.176
And I capture all network traffic 0.002
And I make sure time sync before Tor connects fails 0.059
And the network is plugged 0.075
And the Tor Connection Assistant autostarts 1.706
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 10.450
The 
The Dogtail init script raised: SearchError: descendant of [application | Tor Connection]: child with name='Connect to Tor automatically' roleName='radio button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/tor.rb:533:in `tca_configure'
./features/step_definitions/tor.rb:670:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/time_syncing.feature:70:in `When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting'
And I click "Connect to Tor" 0.000
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:535 0.034
After features/support/hooks.rb:339 4.888 
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:19:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:19:27_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_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:19:27_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_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:19:27_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_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:19:27_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:108 0.050
Feature: Using Tor bridges and pluggable transports
Tags: @product
10.577
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 10.577
The 
The Dogtail init script raised: SearchError: descendant of [application | Tor Connection]: child with name='Connect to Tor automatically' roleName='radio button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/tor.rb:533:in `tca_configure'
./features/step_definitions/tor.rb:553:in `/^I configure a direct connection in the Tor Connection Assistant$/'
features/tor_bridges.feature:72:in `Given I configure a direct connection in the Tor Connection Assistant'
And I wait until Tor is ready 0.000
When I disconnect the network through GNOME 0.000
And I connect the network through GNOME 0.000
Then the Tor Connection Assistant autostarts 0.000
And the Tor Connection Assistant connects to Tor 0.000
And I wait until Tor is ready 0.000
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:339 4.908 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:24:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:24:14_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:24:14_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:24:14_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:24:14_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:108 0.036
Feature: Using Tor bridges and pluggable transports
Tags: @product
10.568
Scenario Asking for bridge settings but receiving a mocked API error in Tor Connection
Steps
Given the Moat distributor responds with an API error 0.021
When I configure Tor Connection to ask for bridge settings based on my location 10.546
The 
The Dogtail init script raised: SearchError: descendant of [application | Tor Connection]: child with name='Connect to Tor automatically' roleName='radio button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/tor.rb:533:in `tca_configure'
./features/step_definitions/tor.rb:856:in `/^I configure Tor Connection to ask for bridge settings (?:based on my location|for "(.*)")$/'
features/tor_bridges.feature:111:in `When I configure Tor Connection to ask for bridge settings based on my location'
Then the Tor Connection Assistant reports that it failed to connect 0.000
And the Tor Connection Assistant reports the Moat API error 0.000
After features/support/hooks.rb:339 4.929 
SCENARIO FAILED: 'Asking for bridge settings but receiving a mocked API error in Tor Connection' (at time 00:26:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:26:41_Asking_for_bridge_settings_but_receiving_a_mocked_API_error_in_Tor_Connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:26:41_Asking_for_bridge_settings_but_receiving_a_mocked_API_error_in_Tor_Connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:26:41_Asking_for_bridge_settings_but_receiving_a_mocked_API_error_in_Tor_Connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:26:41_Asking_for_bridge_settings_but_receiving_a_mocked_API_error_in_Tor_Connection.journal
After features/support/hooks.rb:108 0.063
Feature: Installing Tails to a USB drive
Tags: @product
32.663
Scenario Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 5.197
And I create a file in the Persistent directory 0.084
And I temporarily create a 7200 MiB disk named "install" 0.025
And I create a gpt partition with a vfat filesystem on disk "install" 2.811
And I plug USB drive "install" 2.177
And I install Tails with Persistent Storage to USB drive "install" by cloning 22.366
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:1031:in `/^I run "([^"]+)" in Console$/'
./features/step_definitions/usb.rb:155:in `/^I start Tails Installer$/'
./features/step_definitions/usb.rb:195:in `/^I (install|reinstall|upgrade) Tails( with Persistent Storage)? (?:to|on) USB drive "([^"]+)" by cloning$/'
features/usb_install.feature:50:in `And I install Tails with Persistent Storage to USB drive "install" by cloning'
Then the running Tails is installed on USB drive "install" 0.000
And there is a random seed on USB drive "install" 0.000
And there is 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:339 4.811 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage' (at time 00:45:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:45:43_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:45:43_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_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:45:43_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_test-snapshot-restore-improvements/4/artifact/build-artifacts/00:45:43_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.journal
After features/support/hooks.rb:108 0.001
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
20:3.926
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 3.757
And I set an administration password 20:0.168
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
<internal:kernel>:187:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:89:in `new'
./features/support/helpers/dogtail.rb:89: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:360:in `click'
./features/step_definitions/common_steps.rb:566:in `open_greeter_additional_settings'
./features/step_definitions/common_steps.rb:593:in `/^I set an administration password$/'
features/localization.feature:49:in `And I set an administration password'
features/localization.feature:23:in `And I set an administration password'
When I log in to a new session in French (fr) 0.000
Then the keyboard layout is set to "fr" 0.000
And tpsd is localized to the selected locale 0.000
Given the network is plugged 0.000
And Tor is ready 0.000
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
Given Thunderbird is installed 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "fr" 0.000
After features/support/hooks.rb:339 10.571 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#4)' (at time 02:08:24)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/02:08:24_Tails_is_localized_for_every_tier-1_language,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/02:08:24_Tails_is_localized_for_every_tier-1_language,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/02:08:24_Tails_is_localized_for_every_tier-1_language,_Examples___4_.journal
After features/support/hooks.rb:108 0.000
Feature: Using persistent Tor bridges and pluggable transports
19.162
Background
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 5.464
And I create a persistent partition with the default settings 13.697
The 
The Dogtail init script raised: SearchError: descendant of [frame | Persistent Storage]: 'Create Persistent Storage' button
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:272:in `button'
./features/step_definitions/usb.rb:386:in `/^I try to create a persistent partition( for Additional Software)?( using the wizard that was already open)?$/'
./features/step_definitions/usb.rb:355:in `/^I create a persistent partition( with the default settings)?( for Additional Software)?( using the wizard that was already open)?$/'
features/persistent_tor_bridges.feature:9:in `And I create a persistent partition with the default settings'
Then the "TorConfiguration" tps feature is not enabled 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 0.000
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:339 5.319 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 02:56:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/02:56:30_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/02:56:30_Using_Persistent_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/02:56:30_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/02:56:30_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:108 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:5.903
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails from DVD without network and logged in 3.325
Then the live user's Documents directory exists 0.059
And there is a GNOME bookmark for the Documents directory 1:2.519
try_for() 
try_for() timeout expired
Last ignored exception was: Test::Unit::AssertionFailedError: <Dogtail::Failure> exception was expected but none was thrown.
./features/step_definitions/common_steps.rb:1305:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
<internal:kernel>:187: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:1303:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:1346: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:1303:in `/^I close the "([^"]+)" window via AltF4$/'
./features/step_definitions/common_steps.rb:1346:in `/^there is a GNOME bookmark for the (.*) directory$/'
features/torified_browsing.feature:123:in `And there is a GNOME bookmark for the Documents directory'
features/torified_browsing.feature:118:in `And there is a GNOME bookmark for the <dir> directory'
Then I start the Tor Browser in offline mode 0.000
And I can save the current page as "index.html" to the Documents GNOME bookmark 0.000
After features/support/hooks.rb:339 5.053 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#1)' (at time 03:19:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/03:19:10_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/03:19:10_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/03:19:10_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/03:19:10_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.journal
After features/support/hooks.rb:108 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
37.800
Scenario Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume
Steps
When I plug a USB drive containing a hidden VeraCrypt volume 17.272
And I cancel the GNOME authentication prompt 20.527
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:872:in `/^I cancel the GNOME authentication prompt$/'
features/veracrypt.feature:23:in `And I cancel the GNOME authentication prompt'
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:339 5.162 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume' (at time 03:32:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/03:32:05_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/03:32:05_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/03:32:05_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-snapshot-restore-improvements/4/artifact/build-artifacts/03:32:05_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal
After features/support/hooks.rb:108 0.000