Project Number Date
test_Tails_ISO_test-suite-options 24 09 Jul 2025, 05:36

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks @not_release_blocker
2:8.071
Scenario Anti-test: Changes to the hardware clock are kept when rebooting
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:507 0.002
Steps
Given I have started Tails from DVD without network and logged in 11.531
When I bump the hardware clock's time with "-15 days" 1.562
And I warm reboot the computer 0.018
And the computer reboots Tails 1:54.958
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)>' (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/time_syncing.feature:45:in `And the computer reboots Tails'
Then the hardware clock is still off by "-15 days" 0.000
After features/support/hooks.rb:515 0.052
After features/support/hooks.rb:330 4.996 
SCENARIO FAILED: 'Anti-test: Changes to the hardware clock are kept when rebooting' (at time 00:18:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/00:18:23_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/00:18:23_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/00:18:23_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/00:18:23_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.journal
After features/support/hooks.rb:100 0.006
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
11:30.356
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 30.696
And no SquashFS delta is installed 0.309
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.655
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.255
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.576
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.839
When the network is plugged 0.092
And Tor is ready 40.299
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 18.438
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 21.372
Given I shutdown Tails and wait for the computer to power off 17.171
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:44.404
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.274
And the file system changes introduced in version 6.2~testoverlayfs are present 0.431
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.306
When the network is plugged 0.198
And Tor is ready 34.435
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 19.526
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 24.367
Given I shutdown Tails and wait for the computer to power off 13.373
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:24.093
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 3.878
And the file system changes introduced in version 6.3~testoverlayfs are present 5.755
And only the 6.3~testoverlayfs SquashFS delta is installed 1.434
# 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.970
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 1.836
When the network is plugged 1.135
And Tor is ready 18.801
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/usb_upgrade.feature:119:in `And Tor is ready'
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:330 5.110 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:23:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:23:26_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_test-suite-options/24/artifact/build-artifacts/02:23:26_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:23:26_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:23:26_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.062
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
1:9.955
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.086
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:9.955
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:330 8.518 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 02:24:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:24:43_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:24:43_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:24:43_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:24:43_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000
Feature: Backing up the persistent storage
Tags: @product
1:44.993
Scenario Using Tails' custom backup tool to backup a newly added file
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.052
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.284
# 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 13.339
And I clone USB drive "__internal" to a temporary USB drive "backup" 2.888
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.081
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.019
When I start Tails' custom backup tool 9.789
Then the backup tool displays "Plug in your backup Tails USB stick" 3.293
When I plug USB drive "backup" 2.858
And I give the Persistent Storage on drive "backup" its own UUID 0.243
And I click "Retry" in the backup tool 1.199
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 1.545
When I click "Back Up" in the backup tool 1.372
And I enter my persistent storage passphrase into the polkit prompt 24.078
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:791:in `deal_with_polkit_prompt'
./features/step_definitions/backup.rb:18:in `/^I enter my persistent storage passphrase into the polkit prompt$/'
features/backup.feature:21:in `And I enter my persistent storage passphrase into the polkit prompt'
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 0.000
# The backup tool ejects the drive, so we have to replug it
When I unplug USB drive "backup" 0.000
And I plug USB drive "backup" 0.000
Then the USB drive "backup" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:330 21.780 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 02:39:06)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:39:06_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:39:06_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:39:06_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 1.161
Feature: Tails documentation
Tags: @product @doc @not_release_blocker
1:13.844
Scenario The Tails documentation launcher works when offline
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Steps
Given I have started Tails from DVD without network and logged in 1:13.844
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/documentation.feature:5:in `Given I have started Tails from DVD without network and logged in'
When I start "Tails Documentation" via GNOME Activities Overview 0.000
Then the Tor Browser has started 0.000
Then "Tails - Documentation" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 6.685 
SCENARIO FAILED: 'The Tails documentation launcher works when offline' (at time 02:43:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:43:44_The_Tails_documentation_launcher_works_when_offline.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:43:44_The_Tails_documentation_launcher_works_when_offline.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:43:44_The_Tails_documentation_launcher_works_when_offline.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/02:43:44_The_Tails_documentation_launcher_works_when_offline.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
34.763
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.408
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.577
When Tails detects disk read failures on the boot device 1.380
Then I see a disk failure message 10.396
FindTextFailed 
FindTextFailed (FindTextFailed)
./features/support/helpers/screen.rb:274:in `rescue in wait_text'
./features/support/helpers/screen.rb:266:in `wait_text'
./features/step_definitions/hardware.rb:39:in `/^I see a disk failure message$/'
features/hardware_failure.feature:30:in `Then I see a disk failure message'
features/hardware_failure.feature:25:in `Then I see a disk failure message'
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:330 5.832 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 03:06:07)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/03:06:07_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/03:06:07_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/03:06:07_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/03:06:07_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:8.782
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.128
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 15.004
When I log in to a new session in Chinese (zh_CN) 1:0.146
Then the keyboard layout is set to "cn" 1.670
When the network is plugged 7.512
And Tor is ready 23.842
Then I successfully start the Unsafe Browser 39.601
And I kill the Unsafe Browser 6.604
When I enable the screen keyboard 0.114
Then the screen keyboard works in Tor Browser 34.285
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:411:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:45:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 12.611 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#2)' (at time 03:52:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/03:52:30_Tails_is_localized_for_every_tier-1_language,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/03:52:30_Tails_is_localized_for_every_tier-1_language,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/03:52:30_Tails_is_localized_for_every_tier-1_language,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/03:52:30_Tails_is_localized_for_every_tier-1_language,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:22.456
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.144
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 10.525
When I log in to a new session in Italian (it) 55.546
Then the keyboard layout is set to "it" 0.442
When the network is plugged 0.126
And Tor is ready 1:0.169
Then I successfully start the Unsafe Browser 35.082
And I kill the Unsafe Browser 6.454
When I enable the screen keyboard 0.218
Then the screen keyboard works in Tor Browser 33.890
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:411:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:52:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 6.620 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#6)' (at time 04:10:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:10:09_Tails_is_localized_for_every_tier-1_language,_Examples___6_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:10:09_Tails_is_localized_for_every_tier-1_language,_Examples___6_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:10:09_Tails_is_localized_for_every_tier-1_language,_Examples___6_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:10:09_Tails_is_localized_for_every_tier-1_language,_Examples___6_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
5:29.991
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.009
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 19.209
When I log in to a new session in Persian (fa) 1:0.099
Then the keyboard layout is set to "ir" 0.177
When the network is plugged 0.081
And Tor is ready 35.225
Then I successfully start the Unsafe Browser 39.772
And I kill the Unsafe Browser 6.941
When I enable the screen keyboard 2.327
Then the screen keyboard works in Tor Browser 1:12.596
And DuckDuckGo is the default search engine 56.148
And I kill the Tor Browser 7.030
And the screen keyboard works in Thunderbird 30.378
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: "Thunderbird" application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:1047:in `new'
./features/step_definitions/common_steps.rb:1047:in `block in launch_app'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:1046:in `launch_app'
./features/step_definitions/common_steps.rb:1093:in `launch_thunderbird'
./features/step_definitions/thunderbird.rb:33:in `block in <top (required)>'
./features/step_definitions/thunderbird.rb:212:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:1046:in `launch_app'
./features/step_definitions/common_steps.rb:1093:in `launch_thunderbird'
./features/step_definitions/thunderbird.rb:33:in `/^I start Thunderbird$/'
./features/step_definitions/thunderbird.rb:212:in `/^the screen keyboard works in Thunderbird$/'
features/localization.feature:53:in `And the screen keyboard works in Thunderbird'
features/localization.feature:33:in `And the screen keyboard works in Thunderbird'
And the layout of the screen keyboard is set to "ir" 0.000
After features/support/hooks.rb:330 6.798 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#7)' (at time 04:15:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:15:47_Tails_is_localized_for_every_tier-1_language,_Examples___7_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:15:47_Tails_is_localized_for_every_tier-1_language,_Examples___7_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:15:47_Tails_is_localized_for_every_tier-1_language,_Examples___7_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:15:47_Tails_is_localized_for_every_tier-1_language,_Examples___7_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
4:18.189
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.014
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 1:7.123
When I log in to a new session in Spanish (es) 57.663
Then the keyboard layout is set to "es" 0.206
When the network is plugged 0.144
And Tor is ready 57.593
Then I successfully start the Unsafe Browser 34.708
And I kill the Unsafe Browser 6.721
When I enable the screen keyboard 0.166
Then the screen keyboard works in Tor Browser 33.861
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:411:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:56:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 6.401 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#10)' (at time 04:30:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:30:49_Tails_is_localized_for_every_tier-1_language,_Examples___10_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:30:49_Tails_is_localized_for_every_tier-1_language,_Examples___10_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:30:49_Tails_is_localized_for_every_tier-1_language,_Examples___10_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:30:49_Tails_is_localized_for_every_tier-1_language,_Examples___10_.journal
After features/support/hooks.rb:100 0.000
Feature: Spoofing MAC addresses
Tags: @product
1:22.804
Scenario MAC address spoofing is disabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.122
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 18.099
And I capture all network traffic 0.023
When I disable MAC spoofing in Tails Greeter 15.792
And I log in to a new session 39.075
And the network is plugged 0.071
And Tor is ready 9.742
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/mac_spoofing.feature:14:in `And Tor is ready'
Then 1 network interface is enabled 0.000
And the 1st network device has its real MAC address configured 0.000
When I hotplug a network device and wait for it to be initialized 0.000
Then 2 network interfaces are enabled 0.000
And the 2nd network device has its real MAC address configured 0.000
And some network device leaked the real MAC address 0.000
After features/support/hooks.rb:330 11.365 
SCENARIO FAILED: 'MAC address spoofing is disabled' (at time 04:37:24)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:37:24_MAC_address_spoofing_is_disabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:37:24_MAC_address_spoofing_is_disabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:37:24_MAC_address_spoofing_is_disabled.journal
After features/support/hooks.rb:100 0.063
Feature: Tails persistence
Tags: @product
1:26.695
Scenario Booting Tails from a USB drive with a disabled persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 1:26.695
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ and\ stopped\ at\ Tails\ Greeter's\ login\ screen$/'
features/persistence.feature:13:in `Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen'
When I log in to a new session without activating the Persistent Storage 0.000
Then Tails is running from USB drive "__internal" 0.000
And persistence is disabled 0.000
But a Tails persistence partition exists on USB drive "__internal" 0.000
After features/support/hooks.rb:330 6.941 
SCENARIO FAILED: 'Booting Tails from a USB drive with a disabled persistent partition' (at time 04:59:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:59:44_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:59:44_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:59:44_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/04:59:44_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:14.841
Scenario Creating a Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 1:14.841
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ without\ a\ persistent\ partition\ and\ logged\ in$/'
features/persistence.feature:20:in `Given I have started Tails without network from a USB drive without a persistent partition and logged in'
Then Tails is running from USB drive "__internal" 0.000
When I create a file in the Persistent directory 0.000
And I create a persistent partition with the default settings 0.000
Then the file I created was copied to the Persistent Storage 0.000
When 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 persistence for "Persistent" is active 0.000
And the file I created in the Persistent directory exists 0.000
After features/support/hooks.rb:330 5.913 
SCENARIO FAILED: 'Creating a Persistent Storage' (at time 05:01:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/05:01:05_Creating_a_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/05:01:05_Creating_a_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/05:01:05_Creating_a_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/05:01:05_Creating_a_Persistent_Storage.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:10.811
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.017
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 55.485
And the network is plugged 2.064
And Tor is ready 13.261
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/persistence.feature:75:in `And Tor is ready'
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 8.470 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition' (at time 05:11:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/05:11:42_Writing_files_to_a_read_write-enabled_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/05:11:42_Writing_files_to_a_read_write-enabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/05:11:42_Writing_files_to_a_read_write-enabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/05:11:42_Writing_files_to_a_read_write-enabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:14.499
Scenario Creating and using a persistent NetworkManager connection
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:14.499
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:83: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 add a wired DHCP NetworkManager connection called "persistent-con-current" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
And I capture all network traffic 0.000
And the network is plugged 0.000
And Tor is ready 0.000
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 6.662 
SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 05:13:04)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/05:13:04_Creating_and_using_a_persistent_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/05:13:04_Creating_and_using_a_persistent_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/05:13:04_Creating_and_using_a_persistent_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/05:13:04_Creating_and_using_a_persistent_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:29.549
Scenario Changing the Persistent Storage passphrase
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.766
# Note that if anything fails after the passphrase was changed and
# before it's changed back below, subsequent scenarios might fail
# because the Persistent Storage doesn't have the expected passphrase.
When I change the passphrase of the Persistent Storage 1:14.783
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:475:in `/^I change the passphrase of the Persistent Storage( back to the original)?$/'
features/persistence.feature:121:in `When I change the passphrase of the Persistent Storage'
And I shutdown Tails and wait for the computer to power off 0.000
Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 0.000
And I change the passphrase of the Persistent Storage back to the original 0.000
After features/support/hooks.rb:330 12.287 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 05:25:13)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/05:25:13_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/05:25:13_Changing_the_Persistent_Storage_passphrase.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/05:25:13_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:24.149
Scenario Feature activation fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 20.548
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.537
When I try to enable persistence 3.058
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 1:0.004
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 14.732 
SCENARIO FAILED: 'Feature activation fails' (at time 05:33:26)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/05:33:26_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/05:33:26_Feature_activation_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/05:33:26_Feature_activation_fails.journal
After features/support/hooks.rb:100 0.000
Feature: The Tor enforcement is effective
Tags: @product
1:59.299
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.009
Steps
Given I have started Tails from DVD and logged in and the network is connected 15.269
And I capture all network traffic 0.261
When I successfully start the Unsafe Browser 29.695
And I open the Tails homepage in the Unsafe Browser 10.981
And the Tails homepage loads in the Unsafe Browser 1:3.090
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.471 
SCENARIO FAILED: 'Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector' (at time 06:24:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/06:24:42_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_test-suite-options/24/artifact/build-artifacts/06:24:42_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_test-suite-options/24/artifact/build-artifacts/06:24:42_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_test-suite-options/24/artifact/build-artifacts/06:24:42_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:100 0.044
Feature: Browsing the web using the Tor Browser
Tags: @product
1:52.563
Scenario I can view a file stored in "~/Downloads" but not in ~/.gnupg
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Steps
Given I have started Tails from DVD and logged in and the network is connected 18.020
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/Downloads/synaptic.html" as user "amnesia" 0.134
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/.gnupg/synaptic.html" as user "amnesia" 0.077
And I copy "/usr/share/synaptic/html/index.html" to "/tmp/synaptic.html" as user "amnesia" 0.085
Then the file "/home/amnesia/.gnupg/synaptic.html" exists 0.064
And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.059
And the file "/live/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.075
And the file "/tmp/synaptic.html" exists 0.077
Given I start monitoring the AppArmor log of "torbrowser_firefox" 0.169
When I start the Tor Browser 55.119
And the Tor Browser loads the startup page 1.773
And I open the address "file:///home/amnesia/Downloads/synaptic.html" in the Tor Browser 20.791
Then I see "TorBrowserSynapticManual.png" after at most 5 seconds 0.663
And AppArmor has not denied "torbrowser_firefox" from opening "/home/amnesia/Downloads/synaptic.html" 1.043
When I open the address "file:///home/amnesia/.gnupg/synaptic.html" in the Tor Browser 8.148
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 6.260
can 
can still find TorBrowserSynapticManual.png on the screen (FindFailed)
./features/support/helpers/screen.rb:207:in `rescue in wait_vanish'
./features/support/helpers/screen.rb:192:in `wait_vanish'
./features/step_definitions/common_steps.rb:757:in `/^I (do not )?see "([^"]*)" after at most (\d+) seconds$/'
features/torified_browsing.feature:65:in `Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds'
When I open the address "file:///lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
When I open the address "file:///live/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
When I open the address "file:///tmp/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
After features/support/hooks.rb:330 5.978 
SCENARIO FAILED: 'I can view a file stored in "~/Downloads" but not in ~/.gnupg' (at time 06:41:24)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/06:41:24_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/06:41:24_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/06:41:24_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/06:41:24_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product
2:34.864
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.010
Steps
Given I have started Tails from DVD and logged in and the network is connected 30.517
When I successfully start the Unsafe Browser 43.939
When I open the Tails homepage in the Unsafe Browser 19.848
Then the Tails homepage loads in the Unsafe Browser 1:0.559
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.088 
SCENARIO FAILED: 'The Unsafe Browser can load a web page from the Internet' (at time 07:16:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:16:50_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_test-suite-options/24/artifact/build-artifacts/07:16:50_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:16:50_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:16:50_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:10.162
Scenario Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 35.465
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 19.827
And I open this VeraCrypt volume in GNOME Files 14.869
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:33: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 12.905 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM' (at time 07:31:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:31:10_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:31:10_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:31:10_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:31:10_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.020
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
49.307
Scenario Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume
Steps
When I plug a USB drive containing a hidden VeraCrypt volume 15.207
And I cancel the GNOME authentication prompt 7.350
And I unlock and mount this VeraCrypt volume with GNOME Disks 12.524
And I open this VeraCrypt volume in GNOME Files 14.224
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:61: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 volume 0.000
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 11.868 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:36:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:36:09_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:36:09_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:36:09_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:36:09_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.005
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
1:5.487
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 51.319
And I unlock and mount this VeraCrypt file container with GNOME Disks 14.168
The 
The Dogtail init script raised: ActionNotSupported: Cannot do 'activate' action on [DEAD]
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:346:in `call_tree_node_method'
./features/support/helpers/dogtail.rb:350:in `doActionNamed'
./features/support/helpers/dogtail.rb:364:in `activate'
./features/step_definitions/veracrypt.rb:240:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:68:in `And I unlock and mount this VeraCrypt file container with GNOME Disks'
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 6.991 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 07:37:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:37:44_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:37:44_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:37:44_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:37:44_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.015
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
1:7.104
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 51.308
And I unlock and mount this VeraCrypt file container with GNOME Disks 15.796
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 6.685 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 07:39:45)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:39:45_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:39:45_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:39:45_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/24/artifact/build-artifacts/07:39:45_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.017