Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 102 25 Jun 2025, 20:55

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:32.227
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.449
And I wait until Tor is ready 3.402
When I disconnect the network through GNOME 4.176
And I connect the network through GNOME 3.837
Then the Tor Connection Assistant autostarts 3.554
And the Tor Connection Assistant connects to Tor 7.322
And I wait until Tor is ready 5:0.483
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:335 6.017 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:33:59)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/00:33:59_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/00:33:59_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_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/00:33:59_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/00:33:59_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/00:33:59_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/00:33:59_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/00:33:59_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:105 0.054
Feature: Additional software
Tags: @product @check_tor_leaks @slow
1:47.615
Scenario My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.011
Before features/support/hooks.rb:512 0.007
Steps
Given a computer 0.252
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:47.362
try_for() 
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42: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:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:460:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:459:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284: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:459:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/additional_software_packages.feature:55:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
When I uninstall "popularity-contest" using apt 0.000
And I accept removing "popularity-contest" from Additional Software 0.000
Then "popularity-contest" is not in the list of Additional Software 0.000
When I start Synaptic 0.000
And I update APT using Synaptic 0.000
And I install "cowsay" using Synaptic 0.000
And I accept adding "cowsay" to Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I uninstall "cowsay" using apt 0.000
And I refuse removing "cowsay" from Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I remove "cowsay" from the list of Additional Software using Additional Software GUI 0.000
Then "cowsay" is not in the list of Additional Software 0.000
When I install "cowsay" using apt 0.000
And I refuse adding "cowsay" to Additional Software 0.000
Then "cowsay" is not in the list of Additional Software 0.000
After features/support/hooks.rb:520 0.037
After features/support/hooks.rb:335 11.586 
SCENARIO FAILED: 'My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic' (at time 01:25:09)
Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/01:25:09_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/01:25:09_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/01:25:09_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/01:25:09_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/01:25:09_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/01:25:09_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/01:25:09_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/01:25:09_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.journal
After features/support/hooks.rb:105 0.024
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
1:20.633
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.020
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:20.633
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/usb_upgrade.feature:82:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And no SquashFS delta is installed 0.000
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.000
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:335 6.937 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:13:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:13:59_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:13:59_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:13:59_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:13:59_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:105 0.000
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
1:15.884
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:15.884
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/usb_upgrade.feature:127:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the signing key used by the Upgrader is outdated 0.000
But a current signing key is available on our website 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
After features/support/hooks.rb:335 7.477 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 02:15:21)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:15:21_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:15:21_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:15:21_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:15:21_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:105 0.000
Feature: Backing up the persistent storage
Tags: @product
2:9.466
Scenario Using Tails' custom backup tool to backup a newly added file
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.011
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 25.111
# 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.988
And I clone USB drive "__internal" to a temporary USB drive "backup" 2.459
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.170
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 1.535
When I start Tails' custom backup tool 9.964
Then the backup tool displays "Plug in your backup Tails USB stick" 0.205
When I plug USB drive "backup" 4.203
And I give the Persistent Storage on drive "backup" its own UUID 0.135
And I click "Retry" in the backup tool 1.268
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 4.116
When I click "Back Up" in the backup tool 4.443
And I enter my persistent storage passphrase into the polkit prompt 6.836
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 30.028
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:335 13.355 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 02:31:19)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:31:19_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:31:19_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:31:19_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:105 1.345
Feature: Hardware failures
Tags: @product @broken_welcome_screen
1:51.946
Scenario Outline Alerting about disk read failures before reaching the Welcome Screen
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.010
Steps
Given a computer 0.195
And SquashFS is damaged in a way that some read operations fail 0.000
When I start the computer 1.413
Then the computer boots Tails 50.253
And I see a disk failure message on the splash screen 1:0.084
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:43:in `/^I see a disk failure message on the splash screen$/'
features/hardware_failure.feature:16:in `And I see a disk failure message on the splash screen'
features/hardware_failure.feature:13:in `And I see a disk failure message on the splash screen'
After features/support/hooks.rb:335 5.044 
SCENARIO FAILED: 'Alerting about disk read failures before reaching the Welcome Screen, Examples (#1)' (at time 02:50:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:50:36_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:50:36_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:50:36_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/02:50:36_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.journal
After features/support/hooks.rb:105 0.010
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
9.304
Scenario Using Persistent Tor bridges
Steps
When I choose to connect to Tor automatically 3.187
And I accept Tor Connection's offer to use my persistent bridges 2.818
And I click "Connect to Tor" 3.298
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:840:in `/^(?:I click "Connect to Tor"|I retry connecting to Tor)$/'
features/persistent_tor_bridges.feature:29:in `And I click "Connect to Tor"'
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:335 5.626 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 05:18:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/05:18:54_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/05:18:54_Using_Persistent_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/05:18:54_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/05:18:54_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:105 0.052
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
1:4.231
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 50.612
And I unlock and mount this VeraCrypt file container with GNOME Disks 13.619
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:335 9.813 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 07:01:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/07:01:58_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_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/07:01:58_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/07:01:58_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_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/07:01:58_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:105 0.028
Feature: I can report a bug with WhisperBack
Tags: @product
40.064
Scenario WhisperBack has access to debugging information
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.020
Steps
Given I have started Tails from DVD without network and logged in 29.413
When I start "WhisperBack" via GNOME Activities Overview 10.651
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:1141:in `/^I start "([^"]+)" via GNOME Activities Overview$/'
features/whisperback.feature:18:in `When I start "WhisperBack" via GNOME Activities Overview'
Then WhisperBack has debugging information 0.000
After features/support/hooks.rb:335 6.311 
SCENARIO FAILED: 'WhisperBack has access to debugging information' (at time 07:07:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/07:07:42_WhisperBack_has_access_to_debugging_information.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/07:07:42_WhisperBack_has_access_to_debugging_information.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/07:07:42_WhisperBack_has_access_to_debugging_information.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/102/artifact/build-artifacts/07:07:42_WhisperBack_has_access_to_debugging_information.journal
After features/support/hooks.rb:105 0.000