Project Number Date
test_Tails_ISO_stable 5766 14 Jul 2025, 18:31

Failures Overview

The following summary displays scenarios that failed.

Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:33.958
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.004
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 25.957
When I log in to a new session in French (fr) 53.596
Then the keyboard layout is set to "fr" 0.220
When the network is plugged 0.106
And Tor is ready 14.077
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:47: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 "fr" 0.000
After features/support/hooks.rb:330 5.702 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#4)' (at time 03:03:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/03:03:29_Tails_is_localized_for_every_tier-1_language,_Examples___4_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/03:03:29_Tails_is_localized_for_every_tier-1_language,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/03:03:29_Tails_is_localized_for_every_tier-1_language,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/03:03:29_Tails_is_localized_for_every_tier-1_language,_Examples___4_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:34.811
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.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 12.485
When I log in to a new session in Spanish (es) 3:22.325
cannot 
cannot find GnomeApplicationsMenuSpanish.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:566:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:522:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/localization.feature:56:in `When I log in to a new session in Spanish (es)'
features/localization.feature:23:in `When I log in to a new session in <language> (<lang_code>)'
Then the keyboard layout is set to "es" 0.000
When 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
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 6.023 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#10)' (at time 03:26:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/03:26:33_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_stable/5766/artifact/build-artifacts/03:26:33_Tails_is_localized_for_every_tier-1_language,_Examples___10_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/03:26:33_Tails_is_localized_for_every_tier-1_language,_Examples___10_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/03:26:33_Tails_is_localized_for_every_tier-1_language,_Examples___10_.journal
After features/support/hooks.rb:100 0.000
Feature: Packages are up-to-date
Tags: @source
10.974
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:532 0.000
Steps
Given I have the build manifest for the image under test 0.000
Then all packages listed in the build manifest are up-to-date 10.974
Command 
Command failed (pid 94426 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_stable/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_stable/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@9f98e6d92e-20250714T1048Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@9f98e6d92e-20250714T1048Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - b43-fwcutter (1:019-8tails1) to Debian trixie (1:019-13)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:321:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:314:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:314:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:539 0.000
After features/support/hooks.rb:100 0.000
Feature: Networking
Tags: @product
1:4.120
Scenario No initial network
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.104
Steps
Given I have started Tails from DVD without network and logged in 13.711
And I wait between 30 and 60 seconds 39.046 
Slept for 39 seconds
Then the Tor Status icon tells me that Tor is not usable 11.362
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 6.195 
SCENARIO FAILED: 'No initial network' (at time 03:45:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/03:45:32_No_initial_network.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/03:45:32_No_initial_network.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/03:45:32_No_initial_network.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/03:45:32_No_initial_network.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:17.454
Scenario Deleting data of a Persistent Storage feature
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.031
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:17.454
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:65:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then persistence for "Persistent" is active 0.000
When I create a file in the Persistent directory 0.000
And I disable the first tps feature 0.000
And I delete the data of the Persistent Folder feature 0.000
Then the file I created does not exist on the Persistent Storage 0.000
After features/support/hooks.rb:330 7.396 
SCENARIO FAILED: 'Deleting data of a Persistent Storage feature' (at time 04:13:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:13:09_Deleting_data_of_a_Persistent_Storage_feature.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:13:09_Deleting_data_of_a_Persistent_Storage_feature.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:13:09_Deleting_data_of_a_Persistent_Storage_feature.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:13:09_Deleting_data_of_a_Persistent_Storage_feature.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:15.108
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.041
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:15.108
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.893 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition' (at time 04:14:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:14:32_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_stable/5766/artifact/build-artifacts/04:14:32_Writing_files_to_a_read_write-enabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:14:32_Writing_files_to_a_read_write-enabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:14:32_Writing_files_to_a_read_write-enabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
5:33.791
Scenario Creating and using a persistent NetworkManager connection
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.324
And the network is plugged 0.257
And Tor is ready 37.796
And I add a wired DHCP NetworkManager connection called "persistent-con-current" 0.215
And I shutdown Tails and wait for the computer to power off 17.178
Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:7.231
And I capture all network traffic 0.039
And the network is plugged 0.098
And Tor is ready 12.648
try_for() 
try_for() timeout expired
Last ignored exception was: ExecutionFailedInVM: Command failed: /usr/local/lib/tor_variable get --type=conf DisableNetwork
error code: 1
stdout: Unable to authenticate: socket connection failed ([Errno 111] Connection refused)

stderr: SocketError: Cannot connect to Tor's control port
.
<false> is not true.
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/common_steps.rb:616:in `block in check_disable_network'
./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:615:in `check_disable_network'
./features/step_definitions/common_steps.rb:643:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:607: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:615:in `check_disable_network'
./features/step_definitions/common_steps.rb:643:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/persistence.feature:91:in `And Tor is ready'
And I switch to the "persistent-con-current" NetworkManager connection 0.000
And the 1st network device has a spoofed MAC address configured 0.000
And no network device leaked the real MAC address 0.000
After features/support/hooks.rb:330 5.377 
SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 04:20:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:20:13_Creating_and_using_a_persistent_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:20:13_Creating_and_using_a_persistent_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:20:13_Creating_and_using_a_persistent_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:20:13_Creating_and_using_a_persistent_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.103
Feature: Tails persistence
Tags: @product
3:2.169
Scenario Persistent Greeter options
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.038
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 34.926
When I enable persistence 1:34.591
Then no persistent Greeter options were restored 20.538
When I set all Greeter options to non-default values 32.112
cannot 
cannot find TailsGreeterAdditionalSettingsAdd.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:561:in `/^I disable the Unsafe Browser$/'
./features/step_definitions/usb.rb:1577:in `/^I set all Greeter options to non-default values$/'
features/persistence.feature:106:in `When I set all Greeter options to non-default values'
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 6.774 
SCENARIO FAILED: 'Persistent Greeter options' (at time 04:25:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:25:32_Persistent_Greeter_options.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:25:32_Persistent_Greeter_options.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:25:32_Persistent_Greeter_options.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:25:32_Persistent_Greeter_options.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
49.732
Scenario Deleting a Tails persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 43.365
And I log in to a new session without activating the Persistent Storage 6.367
<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:128:in `And I log in to a new session without activating the Persistent Storage'
Then persistence is disabled 0.000
But a Tails persistence partition exists on USB drive "__internal" 0.000
And all notifications have disappeared 0.000
When I delete the persistent partition 0.000
Then there is no persistence partition on USB drive "__internal" 0.000
After features/support/hooks.rb:330 7.803 
SCENARIO FAILED: 'Deleting a Tails persistent partition' (at time 04:34:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:34:08_Deleting_a_Tails_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:34:08_Deleting_a_Tails_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:34:08_Deleting_a_Tails_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:34:08_Deleting_a_Tails_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:19.359
Scenario Dotfiles persistence
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:19.359
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:136:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When I write some dotfile expected to persist 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then the expected persistent dotfile is present in the filesystem 0.000
After features/support/hooks.rb:330 11.079 
SCENARIO FAILED: 'Dotfiles persistence' (at time 04:35:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:35:34_Dotfiles_persistence.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:35:34_Dotfiles_persistence.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:35:34_Dotfiles_persistence.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:35:34_Dotfiles_persistence.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:22.925
Scenario Feature activation fails
Before features/support/hooks.rb:266 0.044
Before features/support/hooks.rb:273 0.155
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 19.005
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.527
When I try to enable persistence 3.199
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 1:0.193
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 15.134 
SCENARIO FAILED: 'Feature activation fails' (at time 04:37:12)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:37:12_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:37:12_Feature_activation_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:37:12_Feature_activation_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:27.564
Scenario LUKS header is automatically upgraded when unlocking the Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.243
Steps
Given I have started Tails without network from a USB drive with a LUKS 1 persistent partition and stopped at Tails Greeter's login screen 1:27.564
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:139:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ LUKS\ 1\ persistent\ partition\ and\ stopped\ at\ Tails\ Greeter's\ login\ screen$/'
features/persistence.feature:154:in `Given I have started Tails without network from a USB drive with a LUKS 1 persistent partition and stopped at Tails Greeter's login screen'
And I enable persistence 0.000
And I log in to a new session after having activated the Persistent Storage 0.000
Then a Tails persistence partition with LUKS version 2 and argon2id exists on USB drive "__internal" 0.000
And persistence is enabled 0.000
After features/support/hooks.rb:330 5.513 
SCENARIO FAILED: 'LUKS header is automatically upgraded when unlocking the Persistent Storage' (at time 04:38:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:38:53_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:38:53_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:38:53_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:38:53_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
2:7.541
Scenario Manual filesystem repair is successful
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.234
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 51.427
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 15.436
When I try to enable persistence 0.674
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.002
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1732:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:176:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that the filesystem was repaired successfully 0.000
And the filesystem of the Persistent Storage was repaired 0.000
When I close the filesystem repair dialog 0.000
Then persistence is successfully enabled 0.000
After features/support/hooks.rb:330 19.681 
SCENARIO FAILED: 'Manual filesystem repair is successful' (at time 04:53:05)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:53:05_Manual_filesystem_repair_is_successful.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:53:05_Manual_filesystem_repair_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:53:05_Manual_filesystem_repair_is_successful.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:21.574
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 21.160
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.119
When I try to enable persistence 0.293
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.001
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1732:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:188:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that it failed to repair the Persistent Storage 0.000
When I log in to a new session 0.000
And all notifications have disappeared 0.000
# Now both WhisperBack and Tor Browser has started at the same
# time, so we do not know which window is focused. The steps about
# Tor Browser care about that, but the ones about WhisperBack do
# not, so we first deal with WhisperBack and then kill it to
# ensure that Tor Browser is focused.
Then WhisperBack is prefilled for fsck with summary: "Failed to repair the file system of your Persistent Storage" 0.000
And the file "/var/lib/gdm3/post-greeter-whisperback.json" is empty 0.000
When I close the "whisperback" window 0.000
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 23.780 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 04:54:51)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:54:51_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:54:51_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:54:51_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:36.455
Scenario Filesystem and I/O errors
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.110
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.925
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 16.930
And Tails detects disk read failures on the boot device 1.851
When I try to enable persistence 0.746
Then the Welcome Screen tells me that my hardware is probably failing 1:0.001
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1835:in `/^the Welcome Screen tells me that my hardware is probably failing$/'
features/persistence.feature:210:in `Then the Welcome Screen tells me that my hardware is probably failing'
When I log in to a new session 0.000
And all notifications have disappeared 0.000
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 20.783 
SCENARIO FAILED: 'Filesystem and I/O errors' (at time 04:56:51)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:56:51_Filesystem_and_I_O_errors.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:56:51_Filesystem_and_I_O_errors.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/04:56:51_Filesystem_and_I_O_errors.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
25.434
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 14.303
And I accept Tor Connection's offer to use my persistent bridges 2.004
And I disable saving bridges to Persistent Storage 1.477
And I configure a direct connection in the Tor Connection Assistant 7.649
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/persistent_tor_bridges.feature:39:in `And I configure a direct connection in the Tor Connection Assistant'
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 7.174 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 05:11:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:11:29_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:11:29_Disabling_persistence_of_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:11:29_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:11:29_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.050
Feature: Tails has a sane default configuration
Tags: @product @not_release_blocker
1:17.071
Scenario No unexpected network services
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:17.071
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/sane_defaults.feature:12:in `Given I have started Tails from DVD and logged in and the network is connected'
Then no unexpected services are listening for network connections 0.000
After features/support/hooks.rb:330 6.618 
SCENARIO FAILED: 'No unexpected network services' (at time 05:19:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:19:50_No_unexpected_network_services.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:19:50_No_unexpected_network_services.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:19:50_No_unexpected_network_services.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:19:50_No_unexpected_network_services.journal
After features/support/hooks.rb:100 0.000
Feature: Tor Connection helps the user in connecting to Tor
1:17.948
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and logged in 1:17.948
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/tor_connection.feature:7:in `Given I have started Tails from DVD without network and logged in'
Feature: Tor Connection helps the user in connecting to Tor
Tags: @product @not_release_blocker
0.000
Scenario Bridges are not enabled in automatic mode when going back from hiding Tor
Steps
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
And I look at the hide mode but then I go back 0.000
And I choose to connect to Tor automatically 0.000
Then Tor Connection does not propose me to use Tor bridges 0.000
After features/support/hooks.rb:330 5.749 
SCENARIO FAILED: 'Bridges are not enabled in automatic mode when going back from hiding Tor' (at time 05:36:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:36:13_Bridges_are_not_enabled_in_automatic_mode_when_going_back_from_hiding_Tor.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:36:13_Bridges_are_not_enabled_in_automatic_mode_when_going_back_from_hiding_Tor.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:36:13_Bridges_are_not_enabled_in_automatic_mode_when_going_back_from_hiding_Tor.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:36:13_Bridges_are_not_enabled_in_automatic_mode_when_going_back_from_hiding_Tor.journal
After features/support/hooks.rb:100 0.000
Feature: Tor Connection helps the user in connecting to Tor
Tags: @product
1:41.603
Scenario I can use a network with captive portal
Steps
Given the Tor network and default bridges are blocked 4.849
And the network is plugged 0.115
And I make sure time sync before Tor connects indicates a captive portal 1.214
And the Tor Connection Assistant autostarts 6.141
When I choose to connect to Tor automatically 10.211
And I click "Connect to Tor" 1.579
Then the Tor Connection Assistant fails to connect to Tor 32.538
And the Tor Connection Assistant knows that it's not the time sync that failed 13.484
And the Tor Connection Assistant knows that there might be a captive portal 0.147
When I open the Unsafe Browser from Tor Connection 31.319
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: "Firefox" application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/tor.rb:1064:in `new'
./features/step_definitions/tor.rb:1064: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/tor.rb:1063: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/tor.rb:1063:in `/^I open the Unsafe Browser from Tor Connection$/'
features/tor_connection.feature:60:in `When I open the Unsafe Browser from Tor Connection'
And I log-in to the Captive Portal 0.000
And I close the Unsafe Browser 0.000
And the Tor network and default bridges are unblocked 0.000
And I allow time sync before Tor connects to work again 0.000
And I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
After features/support/hooks.rb:330 7.351 
SCENARIO FAILED: 'I can use a network with captive portal' (at time 05:38:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:38:32_I_can_use_a_network_with_captive_portal.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:38:32_I_can_use_a_network_with_captive_portal.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:38:32_I_can_use_a_network_with_captive_portal.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:38:32_I_can_use_a_network_with_captive_portal.journal
After features/support/hooks.rb:100 0.000
Feature: The Tor enforcement is effective
Tags: @product
2:20.495
Scenario Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given I have started Tails from DVD and logged in and the network is connected 21.128
And I capture all network traffic 0.006
When I successfully start the Unsafe Browser 40.346
And I open the Tails homepage in the Unsafe Browser 18.979
And the Tails homepage loads in the Unsafe Browser 1:0.034
cannot 
cannot find TailsHomepage.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:316:in `/^the Tails homepage loads in the Unsafe Browser$/'
features/tor_enforcement.feature:20:in `And the Tails homepage loads in the Unsafe Browser'
Then the firewall leak detector has detected leaks 0.000
After features/support/hooks.rb:330 5.775 
SCENARIO FAILED: 'Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector' (at time 05:41:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:41:34_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:41:34_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:41:34_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:41:34_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:100 0.036
Feature: Tor stream isolation is effective
Tags: @product @check_tor_leaks
30.367
Scenario The Tor Browser is using the web browser-specific SocksPort
Steps
When I monitor the network connections of Tor Browser 0.117
And I start the Tor Browser 30.249
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: "Firefox" 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:1101:in `launch_tor_browser'
./features/step_definitions/browser.rb:445: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:1101:in `launch_tor_browser'
./features/step_definitions/browser.rb:445:in `/^I start the Tor Browser( in offline mode)?$/'
features/tor_stream_isolation.feature:29:in `And I start the Tor Browser'
And the Tor Browser loads the startup page 0.000
Then I see that Tor Browser is properly stream isolated 0.000
After features/support/hooks.rb:515 0.080
After features/support/hooks.rb:330 13.510 
SCENARIO FAILED: 'The Tor Browser is using the web browser-specific SocksPort' (at time 05:50:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:50:32_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:50:32_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:50:32_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:50:32_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
1:30.188
Scenario Downloading files with the Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Before features/support/hooks.rb:507 0.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 59.853
When I start the Tor Browser 30.335
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: "Firefox" 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:1101:in `launch_tor_browser'
./features/step_definitions/browser.rb:445: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:1101:in `launch_tor_browser'
./features/step_definitions/browser.rb:445:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:30:in `When I start the Tor Browser'
Then the Tor Browser loads the startup page 0.000
When I download some file in the Tor Browser to the Downloads directory 0.000
Then the file is saved to the Downloads directory 0.000
After features/support/hooks.rb:515 0.208
After features/support/hooks.rb:330 11.232 
SCENARIO FAILED: 'Downloading files with the Tor Browser' (at time 05:56:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:56:31_Downloading_files_with_the_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:56:31_Downloading_files_with_the_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:56:31_Downloading_files_with_the_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:56:31_Downloading_files_with_the_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
1:37.359
Scenario Playing an Ogg audio track
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Before features/support/hooks.rb:507 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 55.018
When I start the Tor Browser 42.341
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:38:in `When I start the Tor Browser'
And the Tor Browser loads the startup page 0.000
Then I can listen to an Ogg audio track in Tor Browser 0.000
After features/support/hooks.rb:515 0.038
After features/support/hooks.rb:330 15.377 
SCENARIO FAILED: 'Playing an Ogg audio track' (at time 05:58:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:58:16_Playing_an_Ogg_audio_track.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:58:16_Playing_an_Ogg_audio_track.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:58:16_Playing_an_Ogg_audio_track.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/05:58:16_Playing_an_Ogg_audio_track.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:16.845
Scenario Persistent browser bookmarks
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:16.845
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/torified_browsing.feature:134:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And all tps features are active 0.000
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories have safe access rights 0.000
When I start the Tor Browser in offline mode 0.000
And I add a bookmark to eff.org in the Tor Browser 0.000
And I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I log in to a new session 0.000
And all notifications have disappeared 0.000
And I start the Tor Browser in offline mode 0.000
Then the Tor Browser has a bookmark to eff.org 0.000
After features/support/hooks.rb:330 6.965 
SCENARIO FAILED: 'Persistent browser bookmarks' (at time 06:28:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/06:28:32_Persistent_browser_bookmarks.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/06:28:32_Persistent_browser_bookmarks.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/06:28:32_Persistent_browser_bookmarks.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/06:28:32_Persistent_browser_bookmarks.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product
2:19.877
Scenario The Unsafe Browser can load a web page from the Internet
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Steps
Given I have started Tails from DVD and logged in and the network is connected 19.339
When I successfully start the Unsafe Browser 41.351
When I open the Tails homepage in the Unsafe Browser 16.421
Then the Tails homepage loads in the Unsafe Browser 1:2.765
cannot 
cannot find TailsHomepage.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:316:in `/^the Tails homepage loads in the Unsafe Browser$/'
features/unsafe_browser.feature:38:in `Then the Tails homepage loads in the Unsafe Browser'
And the Unsafe Browser has sent packets out to the Internet 0.000
After features/support/hooks.rb:330 6.013 
SCENARIO FAILED: 'The Unsafe Browser can load a web page from the Internet' (at time 06:45:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/06:45:33_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/06:45:33_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/06:45:33_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/06:45:33_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
1:23.271
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 50.504
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 17.603
And I open this VeraCrypt volume in GNOME Files 15.163
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.454 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container' (at time 07:01:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/07:01:53_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_stable/5766/artifact/build-artifacts/07:01:53_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/07:01:53_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/07:01:53_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.023
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
1:3.393
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 50.099
And I unlock and mount this VeraCrypt file container with GNOME Disks 13.293
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:76: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.948 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 07:07:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/07:07:48_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_stable/5766/artifact/build-artifacts/07:07:48_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/07:07:48_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5766/artifact/build-artifacts/07:07:48_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.015