Project Number Date
test_Tails_ISO_devel 3871 17 Jun 2025, 15:14

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:30.350
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.547
And I wait until Tor is ready 2.485
When I disconnect the network through GNOME 3.070
And I connect the network through GNOME 5.709
Then the Tor Connection Assistant autostarts 2.925
And the Tor Connection Assistant connects to Tor 6.276
And I wait until Tor is ready 5:0.334
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 7.361 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:33:02)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/00:33:02_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/00:33:02_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_devel/3871/artifact/build-artifacts/00:33:02_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/00:33:02_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/00:33:02_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/00:33:02_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/00:33:02_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.041
Feature: Hardware failures
Tags: @product @doc
29.646
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given a computer 0.242
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.513
When Tails detects disk read failures on the boot device with a target error 0.874
Then I see a disk failure message 10.015
FindTextFailed 
FindTextFailed (FindTextFailed)
./features/support/helpers/screen.rb:274:in `rescue in wait_text'
./features/support/helpers/screen.rb:266:in `wait_text'
./features/step_definitions/hardware.rb:39:in `/^I see a disk failure message$/'
features/hardware_failure.feature:31:in `Then I see a disk failure message'
features/hardware_failure.feature:25:in `Then I see a disk failure message'
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:330 6.189 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:51:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/02:51:34_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/02:51:34_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/02:51:34_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/02:51:34_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
4:57.985
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.023
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 28.216
When I log in to a new session in Arabic (ar) 57.582
Then the keyboard layout is set to "us" 0.813
When the network is plugged 0.350
And Tor is ready 34.245
Then I successfully start the Unsafe Browser 31.159
And I kill the Unsafe Browser 8.725
When I enable the screen keyboard 0.262
Then the screen keyboard works in Tor Browser 1:1.416
And DuckDuckGo is the default search engine 37.690
And I kill the Tor Browser 7.130
And the screen keyboard works in Thunderbird 30.392
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:44: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 5.685 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#1)' (at time 03:28:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/03:28:15_Tails_is_localized_for_every_tier-1_language,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/03:28:15_Tails_is_localized_for_every_tier-1_language,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/03:28:15_Tails_is_localized_for_every_tier-1_language,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/03:28:15_Tails_is_localized_for_every_tier-1_language,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:49.225
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.024
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 28.917
When I log in to a new session in Chinese (zh_CN) 1:3.003
Then the keyboard layout is set to "cn" 1.683
When the network is plugged 1.772
And Tor is ready 13.847
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/localization.feature:45:in `And Tor is ready'
features/localization.feature:26:in `And Tor is ready'
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 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 "us" 0.000
After features/support/hooks.rb:330 7.246 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#2)' (at time 03:30:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/03:30:14_Tails_is_localized_for_every_tier-1_language,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/03:30:14_Tails_is_localized_for_every_tier-1_language,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/03:30:14_Tails_is_localized_for_every_tier-1_language,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/03:30:14_Tails_is_localized_for_every_tier-1_language,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
4:18.060
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.010
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 10.840
When I log in to a new session in German (de) 57.173
Then the keyboard layout is set to "de" 0.250
When the network is plugged 0.119
And Tor is ready 32.582
Then I successfully start the Unsafe Browser 25.368
And I kill the Unsafe Browser 6.855
When I enable the screen keyboard 1.957
Then the screen keyboard works in Tor Browser 49.910
And DuckDuckGo is the default search engine 36.020
And I kill the Tor Browser 6.600
And the screen keyboard works in Thunderbird 30.379
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:48: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 "de" 0.000
After features/support/hooks.rb:330 6.027 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#5)' (at time 03:46:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/03:46:17_Tails_is_localized_for_every_tier-1_language,_Examples___5_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/03:46:17_Tails_is_localized_for_every_tier-1_language,_Examples___5_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/03:46:17_Tails_is_localized_for_every_tier-1_language,_Examples___5_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/03:46:17_Tails_is_localized_for_every_tier-1_language,_Examples___5_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:12.815
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.177
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 19.870
When I log in to a new session in Portuguese (pt) 59.173
Then the keyboard layout is set to "pt" 0.838
When the network is plugged 6.503
And Tor is ready 26.957
Then I successfully start the Unsafe Browser 38.667
And I kill the Unsafe Browser 6.600
When I enable the screen keyboard 0.139
Then the screen keyboard works in Tor Browser 34.065
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:54: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.296 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#8)' (at time 03:59:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/03:59:20_Tails_is_localized_for_every_tier-1_language,_Examples___8_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/03:59:20_Tails_is_localized_for_every_tier-1_language,_Examples___8_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/03:59:20_Tails_is_localized_for_every_tier-1_language,_Examples___8_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/03:59:20_Tails_is_localized_for_every_tier-1_language,_Examples___8_.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:17.010
Scenario Feature activation fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 16.570
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.105
When I try to enable persistence 0.321
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 1:0.013
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 8.488 
SCENARIO FAILED: 'Feature activation fails' (at time 05:21:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/05:21:55_Feature_activation_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/05:21:55_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/05:21:55_Feature_activation_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/05:21:55_Feature_activation_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
6:9.268
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 18.265
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.137
When I try to enable persistence 0.432
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 54.089
When I repair the filesystem of the Persistent Storage 5.178
Then the Welcome Screen tells me that it failed to repair the Persistent Storage 0.191
When I log in to a new session 57.874
And all notifications have disappeared 17.594
# 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.504
And the file "/var/lib/gdm3/post-greeter-whisperback.json" is empty 0.477
When I close the "whisperback" window 1.468
Then the Tor Browser starts 3:33.053
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/browser.rb:463:in `/^the Tor Browser (?:has started|starts)$/'
features/persistence.feature:201:in `Then the Tor Browser starts'
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 9.184 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 05:42:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/05:42:12_Manual_filesystem_repair_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/05:42:12_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/05:42:12_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/05:42:12_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
44.798
Scenario Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile
Steps
When I plug a USB drive containing a basic VeraCrypt volume with a keyfile 8.271
And I cancel the GNOME authentication prompt 2.420
And I unlock and mount this VeraCrypt volume with GNOME Disks 34.107
The 
The Dogtail init script raised: SearchError: descendent of [application | gnome-disks]: child with name="Select a Keyfile" roleName='file chooser'
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/veracrypt.rb:269:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:51:in `And I unlock and mount this VeraCrypt volume 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 volume 0.000
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 8.733 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 07:41:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/07:41:00_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/07:41:00_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/07:41:00_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/07:41:00_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.journal
After features/support/hooks.rb:100 0.001
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
44.793
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a keyfile 32.696
And I unlock and mount this VeraCrypt file container with GNOME Disks 12.096
The 
The Dogtail init script raised: ActionNotSupported: Cannot do 'activate' action on [DEAD]
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:346:in `call_tree_node_method'
./features/support/helpers/dogtail.rb:350:in `doActionNamed'
./features/support/helpers/dogtail.rb:364:in `activate'
./features/step_definitions/veracrypt.rb:240:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:68:in `And I unlock and mount this VeraCrypt file container with GNOME Disks'
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 6.984 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 07:42:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3871/artifact/build-artifacts/07:42: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_devel/3871/artifact/build-artifacts/07:42: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_devel/3871/artifact/build-artifacts/07:42: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_devel/3871/artifact/build-artifacts/07:42:51_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.019