Project Number Date
test_Tails_ISO_5501-plaintext-locale-greeter 51 08 Jul 2025, 04:20

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
1:18.447
Scenario Clock with host's time
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:507 0.003
Steps
Given I have started Tails from DVD without network and logged in 1:18.447
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/time_syncing.feature:8:in `Given I have started Tails from DVD without network and logged in'
When the network is plugged 0.000
And I successfully configure Tor 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:515 0.049
After features/support/hooks.rb:330 5.564 
SCENARIO FAILED: 'Clock with host's time' (at time 00:21:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:21:23_Clock_with_host_s_time.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:21:23_Clock_with_host_s_time.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:21:23_Clock_with_host_s_time.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:21:23_Clock_with_host_s_time.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
1:9.944
Scenario Clock with host's time while using bridges
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 1:9.944
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/time_syncing.feature:14:in `Given I have started Tails from DVD without network and logged in'
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
And I configure some normal bridges in the Tor Connection Assistant 0.000
And I wait until Tor is ready 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:515 0.172
After features/support/hooks.rb:330 5.927 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:22:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:22:40_Clock_with_host_s_time_while_using_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:22:40_Clock_with_host_s_time_while_using_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:22:40_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:22:40_Clock_with_host_s_time_while_using_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
1:12.171
Scenario Clock is one day in the future while using obfs4 bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:507 0.003
Steps
Given I have started Tails from DVD without network and logged in 31.088
When I bump the system time with "+1 day" 3.051
And I capture all network traffic 0.282
And the network is plugged 15.762
And the Tor Connection Assistant autostarts 10.020
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 11.966
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:628:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/time_syncing.feature:27:in `And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode'
And I wait until Tor is ready 0.000
Then the system clock is less than 5 minutes incorrect 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:515 0.059
After features/support/hooks.rb:330 7.589 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:24:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:24:00_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:24:00_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:24:00_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:24:00_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.051
Feature: Using Tor bridges and pluggable transports
Tags: @product
7.874
Scenario Fall back to default bridges if failing to connect directly to the Tor network
Steps
Given the Tor network is blocked 3.051
When I configure a direct connection in the Tor Connection Assistant 4.823
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/tor_bridges.feature:58:in `When 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 available upgrades have been checked 0.000
And Tor is configured to use the default bridges 0.000
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000
After features/support/hooks.rb:330 8.928 
SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 00:45:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:45:58_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:45:58_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:45:58_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:45:58_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal
After features/support/hooks.rb:100 0.034
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:47.878
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 14.637
And I wait until Tor is ready 6.956
When I disconnect the network through GNOME 3.515
And I connect the network through GNOME 10.346
Then the Tor Connection Assistant autostarts 5.327
And the Tor Connection Assistant connects to Tor 6.727
And I wait until Tor is ready 5:0.367
Time 
Time syncing failed (HtpdateError)
./features/step_definitions/common_steps.rb:724:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:722:in `/^the time has synced$/'
./features/step_definitions/common_steps.rb:675:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:89:in `And I wait until Tor is ready'
And Tor is using the same configuration as before 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 13.722 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:55:38)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:55:38_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:55:38_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log
Htpdate logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:55:38_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:55:38_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:55:38_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:55:38_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/00:55:38_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.054
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
1:9.965
Scenario Erasure of memory freed by killed userspace processes
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails from DVD without network and logged in 1:9.965
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/erase_memory.feature:14:in `Given I have started Tails from DVD without network and logged in'
And I prepare Tails for memory erasure tests 0.000
When I start a process allocating 128 MiB of memory with a known pattern 0.000
Then patterns cover at least 128 MiB in the guest's memory 0.000
When I kill the allocating process 0.000
Then I find very few patterns in the guest's memory after 5 seconds 0.000
After features/support/hooks.rb:330 7.251 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 01:00:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/01:00:20_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/01:00:20_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/01:00:20_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/01:00:20_Erasure_of_memory_freed_by_killed_userspace_processes.journal
After features/support/hooks.rb:100 0.000
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
13:47.037
Scenario Erasure of read and write disk caches of persistent data on shutdown
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 13:47.037
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:137: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/erase_memory.feature:75:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I prepare Tails for memory erasure tests 0.000
When I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
When I trigger shutdown 0.000
Then I find very few patterns in the guest's memory after 20 seconds 0.000
After features/support/hooks.rb:330 5.702 
SCENARIO FAILED: 'Erasure of read and write disk caches of persistent data on shutdown' (at time 01:22:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/01:22:42_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/01:22:42_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/01:22:42_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/01:22:42_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal
After features/support/hooks.rb:100 0.037
Feature: Installing Tails to a USB drive
Tags: @product
12:11.874
Scenario Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12:11.874
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:137: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_install.feature:45:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I create a file in the Persistent directory 0.000
And I temporarily create a 7200 MiB disk named "install" 0.000
And I create a gpt partition with a vfat filesystem on disk "install" 0.000
And I plug USB drive "install" 0.000
And I install Tails with Persistent Storage to USB drive "install" by cloning 0.000
Then the running Tails is installed on USB drive "install" 0.000
And there is a random seed on USB drive "install" 0.000
And there is a persistence partition on USB drive "install" 0.000
And the USB drive "install" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:330 5.377 
SCENARIO FAILED: 'Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage' (at time 01:45:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/01:45:03_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/01:45:03_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/01:45:03_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/01:45:03_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.journal
After features/support/hooks.rb:100 0.016
Feature: Additional software
Tags: @product @check_tor_leaks @slow
6:50.502
Scenario My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Before features/support/hooks.rb:507 0.010
Steps
Given a computer 0.396
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 5:42.649
When I uninstall "popularity-contest" using apt 31.261
And I accept removing "popularity-contest" from Additional Software 1.747
Then "popularity-contest" is not in the list of Additional Software 1.554
When I start Synaptic 32.892
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: "synaptic" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/apt.rb:143:in `new'
./features/step_definitions/apt.rb:143:in `/^I start Synaptic$/'
features/additional_software_packages.feature:59:in `When I start Synaptic'
And I update APT using Synaptic 0.000
And I install "cowsay" using Synaptic 0.000
And I accept adding "cowsay" to Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I uninstall "cowsay" using apt 0.000
And I refuse removing "cowsay" from Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I remove "cowsay" from the list of Additional Software using Additional Software GUI 0.000
Then "cowsay" is not in the list of Additional Software 0.000
When I install "cowsay" using apt 0.000
And I refuse adding "cowsay" to Additional Software 0.000
Then "cowsay" is not in the list of Additional Software 0.000
After features/support/hooks.rb:515 0.067
After features/support/hooks.rb:330 9.018 
SCENARIO FAILED: 'My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic' (at time 02:38:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/02:38:40_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/02:38:40_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/02:38:40_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/02:38:40_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/02:38:40_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/02:38:40_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/02:38:40_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/02:38:40_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/02:38:40_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.journal
After features/support/hooks.rb:100 0.060
Feature: Upgrading an old Tails USB installation
Tags: @product
4:13.813
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given a computer 0.220
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.092
And I write an old version of the Tails USB image to disk "old" 59.333
When I start Tails from USB drive "old" with network unplugged 3:13.114
try_for() 
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:460:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:459:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:459:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:25:in `When I start Tails from USB drive "old" with network unplugged'
Then the boot device has safe access rights 0.000
And Tails is running from USB drive "old" 0.000
And there is no persistence partition on USB drive "old" 0.000
And process "udev-watchdog" is running 0.000
And udev-watchdog is monitoring the correct device 0.000
And I unplug USB drive "old" 0.000
After features/support/hooks.rb:330 8.659 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 03:05:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:05:06_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:05:06_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:05:06_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:05:06_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.323
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
7:32.874
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.009
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:29.600
And no SquashFS delta is installed 0.691
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 2.113
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.647
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.536
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.559
When the network is plugged 0.085
And Tor is ready 41.416
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.126
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 31.436
Given I shutdown Tails and wait for the computer to power off 15.192
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:6.386
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.076
And the file system changes introduced in version 6.2~testoverlayfs are present 0.526
And only the 6.2~testoverlayfs SquashFS delta is installed 0.134
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.444
# 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.570
When the network is plugged 0.115
And Tor is ready 14.198
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 connect to tor. Maybe it's running without a ControlPort?

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:629: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:628:in `check_disable_network'
./features/step_definitions/common_steps.rb:656:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:620: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:628:in `check_disable_network'
./features/step_definitions/common_steps.rb:656:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:620:in `/^Tor is ready$/'
features/usb_upgrade.feature:105:in `And Tor is ready'
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:330 5.598 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:32:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:32:05_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_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:32:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:32:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:32:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.013
Feature: Backing up the persistent storage
Tags: @product
2:14.639
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.039
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.821
# 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 18.862
And I clone USB drive "__internal" to a temporary USB drive "backup" 5.088
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:27.867
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/backup.feature:12:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.000
When I start Tails' custom backup tool 0.000
Then the backup tool displays "Plug in your backup Tails USB stick" 0.000
When I plug USB drive "backup" 0.000
And I give the Persistent Storage on drive "backup" its own UUID 0.000
And I click "Retry" in the backup tool 0.000
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.000
When I click "Back Up" in the backup tool 0.000
And I enter my persistent storage passphrase into the polkit prompt 0.000
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 6.051 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 03:47:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:47:43_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:47:43_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:47:43_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:47:43_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.182
Feature: Using Evince
Tags: @product @not_release_blocker
1:12.141
Scenario I cannot view a PDF file stored in persistent /home/amnesia/.gnupg
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:12.141
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/evince.feature:54:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I copy "/usr/share/cups/data/default-testpage.pdf" to "/home/amnesia/.gnupg" as user "amnesia" 0.000
Then the file "/home/amnesia/.gnupg/default-testpage.pdf" exists 0.000
Given I start monitoring the AppArmor log of "/usr/bin/evince" 0.000
And I try to open "/home/amnesia/.gnupg/default-testpage.pdf" with Evince 0.000
Then Evince tells me it cannot open "/home/amnesia/.gnupg/default-testpage.pdf" 0.000
And AppArmor has denied "/usr/bin/evince" from opening "/home/amnesia/.gnupg/default-testpage.pdf" 0.000
After features/support/hooks.rb:330 6.289 
SCENARIO FAILED: 'I cannot view a PDF file stored in persistent /home/amnesia/.gnupg' (at time 04:01:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/04:01:00_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/04:01:00_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/04:01:00_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/04:01:00_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.journal
After features/support/hooks.rb:100 0.000
Feature: GNOME is well-integrated into Tails
Tags: @product
1:17.105
Scenario GNOME notifications are shown to the user
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.105
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/gnome.feature:15:in `Given I have started Tails from DVD without network and logged in'
When the "Dogtail rules!" notification is sent 0.000
Then the "Dogtail rules!" notification is shown to the user 0.000
After features/support/hooks.rb:330 5.705 
SCENARIO FAILED: 'GNOME notifications are shown to the user' (at time 04:03:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/04:03:03_GNOME_notifications_are_shown_to_the_user.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/04:03:03_GNOME_notifications_are_shown_to_the_user.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/04:03:03_GNOME_notifications_are_shown_to_the_user.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/04:03:03_GNOME_notifications_are_shown_to_the_user.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
31.327
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given a computer 0.323
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.436
When Tails detects disk read failures on the SquashFS 0.553
Then I see a disk failure message 10.013
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:29: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.648 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 04:13:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/04:13:41_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/04:13:41_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/04:13:41_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/04:13:41_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
1:19.397
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.027
Steps
Given a computer 0.384
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:19.013
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/hardware_failure.feature:31:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
features/hardware_failure.feature:23:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
When Tails detects disk read failures on the boot device with a target error 0.000
Then I see a disk failure message 0.000
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:330 6.128 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 04:17:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/04:17:23_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/04:17:23_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/04:17:23_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/04:17:23_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:36.303
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.165
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 14.086
When I log in to a new session in Chinese (zh_CN) 1:2.166
Then the keyboard layout is set to "cn" 3.119
When the network is plugged 3.838
And Tor is ready 13.092
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:666:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:620:in `/^Tor is ready$/'
features/localization.feature:45:in `And Tor is ready'
features/localization.feature:26:in `And Tor is ready'
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 7.812 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#2)' (at time 05:00:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/05:00:00_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_5501-plaintext-locale-greeter/51/artifact/build-artifacts/05:00:00_Tails_is_localized_for_every_tier-1_language,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/05:00:00_Tails_is_localized_for_every_tier-1_language,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/05:00:00_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
1:9.721
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.008
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 16.265
When I log in to a new session in English (en) 39.564
Then the keyboard layout is set to "us" 1.449
When the network is plugged 1.265
And Tor is ready 11.175
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:666:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:620:in `/^Tor is ready$/'
features/localization.feature:46:in `And Tor is ready'
features/localization.feature:26:in `And Tor is ready'
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 6.714 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#3)' (at time 05:01:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/05:01:18_Tails_is_localized_for_every_tier-1_language,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/05:01:18_Tails_is_localized_for_every_tier-1_language,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/05:01:18_Tails_is_localized_for_every_tier-1_language,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/05:01:18_Tails_is_localized_for_every_tier-1_language,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:40.268
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.007
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 10.761
When I log in to a new session in French (fr) 1:15.169
Then the keyboard layout is set to "fr" 0.195
When the network is plugged 0.080
And Tor is ready 55.854
Then I successfully start the Unsafe Browser 34.119
And I kill the Unsafe Browser 8.107
When I enable the screen keyboard 0.141
Then the screen keyboard works in Tor Browser 35.838
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:47: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 "fr" 0.000
After features/support/hooks.rb:330 15.866 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#4)' (at time 05:05:05)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/05:05:05_Tails_is_localized_for_every_tier-1_language,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/05:05:05_Tails_is_localized_for_every_tier-1_language,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/05:05:05_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:15.753
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.056
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 21.222
When I log in to a new session in Spanish (es) 59.553
Then the keyboard layout is set to "es" 0.209
When the network is plugged 0.224
And Tor is ready 33.106
Then I successfully start the Unsafe Browser 38.104
And I kill the Unsafe Browser 7.362
When I enable the screen keyboard 0.154
Then the screen keyboard works in Tor Browser 35.816
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 12.359 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#10)' (at time 05:35:07)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/05:35:07_Tails_is_localized_for_every_tier-1_language,_Examples___10_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/05:35:07_Tails_is_localized_for_every_tier-1_language,_Examples___10_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/05:35:07_Tails_is_localized_for_every_tier-1_language,_Examples___10_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product
1:0.030
Scenario Tails doesn't store localization preferences in cleartext unless it's asked to
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.463
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 51.946
When I set the language to Italian (it) 8.083
Then the language has not been saved in cleartext 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 0.000
Then the Greeter's language is set to English 0.000
After features/support/hooks.rb:330 4.006
After features/support/hooks.rb:100 0.000
Feature: Spoofing MAC addresses
Tags: @product
1:29.604
Scenario MAC address spoofing is successful
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 25.326
And I capture all network traffic 0.335
When I log in to a new session 47.701
And the network is plugged 2.125
And Tor is ready 14.116
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:666:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:620:in `/^Tor is ready$/'
features/mac_spoofing.feature:27:in `And Tor is ready'
Then 1 network interface is enabled 0.000
And the 1st network device has a spoofed 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 a spoofed MAC address configured 0.000
And no network device leaked the real MAC address 0.000
After features/support/hooks.rb:330 7.201 
SCENARIO FAILED: 'MAC address spoofing is successful' (at time 05:48:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/05:48:40_MAC_address_spoofing_is_successful.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/05:48:40_MAC_address_spoofing_is_successful.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/05:48:40_MAC_address_spoofing_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/05:48:40_MAC_address_spoofing_is_successful.journal
After features/support/hooks.rb:100 0.034
Feature: Tails persistence
Tags: @product
1:12.833
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.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:12.833
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.951 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition' (at time 06:26:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/06:26:40_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_5501-plaintext-locale-greeter/51/artifact/build-artifacts/06:26:40_Writing_files_to_a_read_write-enabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/06:26:40_Writing_files_to_a_read_write-enabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/06:26:40_Writing_files_to_a_read_write-enabled_persistent_partition.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:8.688
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 50.569
And the network is plugged 1.441
And Tor is ready 16.677
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:666:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:620:in `/^Tor is ready$/'
features/persistence.feature:85:in `And Tor is ready'
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 11.179 
SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 06:27:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/06:27:57_Creating_and_using_a_persistent_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/06:27:57_Creating_and_using_a_persistent_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/06:27:57_Creating_and_using_a_persistent_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/06:27:57_Creating_and_using_a_persistent_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
2:56.112
Scenario Persistent Greeter options
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 25.258
When I enable persistence 1:52.137
Then no persistent Greeter options were restored 17.971
When I set all Greeter options to non-default values 20.745
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:574: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 7.229 
SCENARIO FAILED: 'Persistent Greeter options' (at time 06:33:22)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/06:33:22_Persistent_Greeter_options.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/06:33:22_Persistent_Greeter_options.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/06:33:22_Persistent_Greeter_options.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/06:33:22_Persistent_Greeter_options.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
7:23.242
Scenario Changing the Persistent Storage passphrase
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.521
# 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:9.588
And I shutdown Tails and wait for the computer to power off 24.216
Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 4:20.649
And I change the passphrase of the Persistent Storage back to the original 1:7.267
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:124:in `And I change the passphrase of the Persistent Storage back to the original'
After features/support/hooks.rb:330 13.051 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 06:40:56)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/06:40:56_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/06:40:56_Changing_the_Persistent_Storage_passphrase.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/06:40:56_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:100 0.010
Feature: Tails persistence
Tags: @product
1:56.366
Scenario Feature activation 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 49.989
And I create a symlink "/home/amnesia/Persistent" to "/etc" 2.043
When I try to enable persistence 4.328
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 1:0.003
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 16.173 
SCENARIO FAILED: 'Feature activation fails' (at time 06:50:23)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/06:50:23_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/06:50:23_Feature_activation_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/06:50:23_Feature_activation_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
1:39.021
Scenario Manual filesystem repair is successful
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 21.182
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 17.184
When I try to enable persistence 0.651
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 25.621 
SCENARIO FAILED: 'Manual filesystem repair is successful' (at time 07:04:00)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/07:04:00_Manual_filesystem_repair_is_successful.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/07:04:00_Manual_filesystem_repair_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/07:04:00_Manual_filesystem_repair_is_successful.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:22.465
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.043
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:22.465
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:185:in `Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen'
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.000
When I try to enable persistence 0.000
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 0.000
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 7.408 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 07:05:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/07:05:40_Manual_filesystem_repair_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/07:05:40_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/07:05:40_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/07:05:40_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
1:28.653
Scenario Filesystem and I/O errors
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 and stopped at Tails Greeter's login screen 16.654
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 8.146
And Tails detects disk read failures on the boot device 0.627
When I try to enable persistence 3.183
Then the Welcome Screen tells me that my hardware is probably failing 1:0.041
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 14.292 
SCENARIO FAILED: 'Filesystem and I/O errors' (at time 07:07:19)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/07:07:19_Filesystem_and_I_O_errors.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/07:07:19_Filesystem_and_I_O_errors.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/07:07:19_Filesystem_and_I_O_errors.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product @not_release_blocker
1:14.179
Scenario No unexpected network services
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Steps
Given I have started Tails from DVD and logged in and the network is connected 1:14.179
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 7.949 
SCENARIO FAILED: 'No unexpected network services' (at time 07:30:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/07:30:40_No_unexpected_network_services.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/07:30:40_No_unexpected_network_services.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/07:30:40_No_unexpected_network_services.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/07:30:40_No_unexpected_network_services.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
1:20.187
Scenario No unexpected error messages in the journal after booting from USB drive
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:20.187
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/sane_defaults.feature:24:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
Then there are no unexpected messages of priority "err" or higher in the journal 0.000
After features/support/hooks.rb:330 5.997 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 07:33:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/07:33:43_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/07:33:43_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/07:33:43_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/07:33:43_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal
After features/support/hooks.rb:100 0.000
Feature: Thunderbird email client
Tags: @product @check_tor_leaks
39:17.972
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 21.080
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.720
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.694
When I accept the autoconfiguration wizard's configuration 38:55.476
Tor 
Tor operation failed (despite retrying 10 times) with
Timeout::Error: try_for() timeout expired (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/thunderbird.rb:136:in `/^I accept the (?:autoconfiguration wizard's|manual) configuration$/'
features/thunderbird.feature:22:in `When I accept the autoconfiguration wizard's configuration'
And I send an email to myself 0.000
And I fetch my email 0.000
Then I can find the email I sent to myself in my inbox 0.000
After features/support/hooks.rb:515 0.038
After features/support/hooks.rb:330 11.962 
SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 08:21:25)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/08:21:25_I_can_send_emails,_and_receive_emails_over_IMAP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/08:21:25_I_can_send_emails,_and_receive_emails_over_IMAP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/08:21:25_I_can_send_emails,_and_receive_emails_over_IMAP.journal
After features/support/hooks.rb:100 0.000
Feature: The Tor enforcement is effective
Tags: @product
1:57.791
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 20.394
And I capture all network traffic 0.064
When I successfully start the Unsafe Browser 25.951
And I open the Tails homepage in the Unsafe Browser 11.081
And the Tails homepage loads in the Unsafe Browser 1:0.300
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 10.045 
SCENARIO FAILED: 'Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector' (at time 08:27:11)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/08:27:11_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_5501-plaintext-locale-greeter/51/artifact/build-artifacts/08:27:11_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_5501-plaintext-locale-greeter/51/artifact/build-artifacts/08:27:11_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:100 0.043
Feature: Browsing the web using the Unsafe Browser
Tags: @product
1:54.958
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.009
Steps
Given I have started Tails from DVD and logged in and the network is connected 17.597
When I successfully start the Unsafe Browser 23.501
When I open the Tails homepage in the Unsafe Browser 13.685
Then the Tails homepage loads in the Unsafe Browser 1:0.173
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 5.722 
SCENARIO FAILED: 'The Unsafe Browser can load a web page from the Internet' (at time 09:08:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/09:08:25_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_5501-plaintext-locale-greeter/51/artifact/build-artifacts/09:08:25_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/09:08:25_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/09:08:25_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.journal
After features/support/hooks.rb:100 0.000