Project Number Date
test_Tails_ISO_ignore-private-backports 4 09 Jul 2025, 07:24

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
2:11.000
Scenario The clock is set to the source date when the hardware clock is way in the past
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 a computer 0.169
And the hardware clock is set to "01 Jan 2000 12:34:56" 0.027
And I start the computer 1.184
And the computer boots Tails 2:9.512
Then the system clock is just past Tails' source date 0.106
The
The system time (2025-06-25 12:41:55 +0000) is before the Tails source date (2025-06-26 10:09:02 +0000).
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/time_syncing.rb:126:in `/^the system clock is just past Tails' source date$/'
features/time_syncing.feature:53:in `Then the system clock is just past Tails' source date'
After features/support/hooks.rb:515 0.043
After features/support/hooks.rb:330 6.925

SCENARIO FAILED: 'The clock is set to the source date when the hardware clock is way in the past' (at time 00:29:28)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/00:29:28_The_clock_is_set_to_the_source_date_when_the_hardware_clock_is_way_in_the_past.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/00:29:28_The_clock_is_set_to_the_source_date_when_the_hardware_clock_is_way_in_the_past.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/00:29:28_The_clock_is_set_to_the_source_date_when_the_hardware_clock_is_way_in_the_past.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/00:29:28_The_clock_is_set_to_the_source_date_when_the_hardware_clock_is_way_in_the_past.journal

After features/support/hooks.rb:100 0.053
Tags: @product
10.778
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 4.695
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 6.082
Expected TCAConnectionFailure to be raised but got Timeout::Error: try_for() timeout expired (RuntimeError)
./features/step_definitions/tor.rb:760:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:755:in `/^I unsuccessfully configure (a direct connection|some .* bridges) in the Tor Connection Assistant$/'
features/tor_bridges.feature:104:in `When I unsuccessfully configure some default bridges in the Tor Connection Assistant'
Then the Tor Connection Assistant reports that it failed to connect 0.000
Given the Tor network and default bridges are unblocked 0.000
When I click "Connect to Tor" 0.000
Then I wait until Tor is ready 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 6.637

SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 00:46:14)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/00:46:14_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/00:46:14_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/00:46:14_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/00:46:14_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal

After features/support/hooks.rb:100 0.051
21.198
Scenario Erasure of memory freed by killed userspace processes
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 8.764
And I prepare Tails for memory erasure tests 2.992
When I start a process allocating 128 MiB of memory with a known pattern 4.183
Then patterns cover at least 128 MiB in the guest's memory 5.257
99.610% of the expected size (128 MiB) has the pattern, but more than 100.000% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:186:in `/^patterns cover at least (\d+) MiB in the guest's memory$/'
features/erase_memory.feature:17:in `Then patterns cover at least 128 MiB in the guest's memory'
Output 1

Pattern coverage: 99.610% (127 MiB out of 128 MiB reference memory)

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 5.636

SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:46:41)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/00:46:41_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/00:46:41_Erasure_of_memory_freed_by_killed_userspace_processes.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/00:46:41_Erasure_of_memory_freed_by_killed_userspace_processes.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/00:46:41_Erasure_of_memory_freed_by_killed_userspace_processes.journal

After features/support/hooks.rb:100 0.000
14:52.500
Scenario I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:507 0.005
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:55.312
And I update APT using apt 18.013
And I install "popularity-contest" using apt 31.820
Then I am proposed to add the "popularity-contest" package to my Additional Software 17.763
When I create a persistent storage and activate the Additional Software feature 52.903
Then Additional Software is correctly configured for package "popularity-contest" 2.925
When I shutdown Tails and wait for the computer to power off 17.455
And I start Tails from USB drive "__internal" with network unplugged 2:31.036
And I enable persistence 49.854
And I log in to a new session 1:21.868
And the Additional Software installation service has started 44.108
Then I am notified that the installation succeeded 5:9.439
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:634:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
./features/step_definitions/additional_software_packages.rb:28:in `/^I am notified that the installation succeeded$/'
features/additional_software_packages.feature:39:in `Then I am notified that the installation succeeded'
And Additional Software is correctly configured for package "popularity-contest" 0.000
And the package "popularity-contest" is installed after Additional Software has been started 0.000
After features/support/hooks.rb:515 0.069
After features/support/hooks.rb:330 10.430

SCENARIO FAILED: 'I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails' (at time 01:51:17)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/01:51:17_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/01:51:17_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/01:51:17_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.journal

After features/support/hooks.rb:100 0.015
2:54.545
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package
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 a computer 0.170
And I start Tails from USB drive "__internal" and I login with an administration password 2:54.375
cannot find TailsGreeter.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:480:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/additional_software_packages.feature:46:in `And I start Tails from USB drive "__internal" and I login with an administration password'
And I update APT using apt 0.000
When I install "makepp" using apt 0.000
Then the Additional Software dpkg hook has been run for package "makepp" and notices the persistence is locked 0.000
And the package "makepp" is installed 0.000
After features/support/hooks.rb:515 0.073
After features/support/hooks.rb:330 12.326

SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:54:22)

Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/01:54:22_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_var_log_boot.log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/01:54:22_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/01:54:22_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/01:54:22_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/01:54:22_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/01:54:22_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/01:54:22_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/01:54:22_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal

After features/support/hooks.rb:100 0.138
16:58.330
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.072
Before features/support/hooks.rb:507 0.043
Steps
Given a computer 0.933
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 8:13.895
When I uninstall "popularity-contest" using apt 36.609
And I accept removing "popularity-contest" from Additional Software 6.981
Then "popularity-contest" is not in the list of Additional Software 7.710
When I start Synaptic 26.623
And I update APT using Synaptic 26.556
And I install "cowsay" using Synaptic 6:59.020
Tor
Tor operation failed (despite retrying 10 times) with
Dogtail::Failure: The Dogtail init script raised: SearchError: child of [application | synaptic]: 'Find' dialog
STDOUT:

STDERR:

 (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/apt.rb:180:in `/^I install "(.+)" using Synaptic$/'
features/additional_software_packages.feature:61:in `And I install "cowsay" using Synaptic'
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.100
After features/support/hooks.rb:330 8.399

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:11:35)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/02:11:35_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_ignore-private-backports/4/artifact/build-artifacts/02:11:35_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_ignore-private-backports/4/artifact/build-artifacts/02:11:35_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_ignore-private-backports/4/artifact/build-artifacts/02:11:35_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_ignore-private-backports/4/artifact/build-artifacts/02:11:35_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_ignore-private-backports/4/artifact/build-artifacts/02:11:35_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_ignore-private-backports/4/artifact/build-artifacts/02:11:35_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_ignore-private-backports/4/artifact/build-artifacts/02:11:35_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_ignore-private-backports/4/artifact/build-artifacts/02:11:35_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.006
5:11.465
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:507 0.002
Steps
Given a computer 0.172
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 5:11.292
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:688:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:642:in `/^Tor is ready$/'
./features/step_definitions/common_steps.rb:292:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/additional_software_packages.feature:79:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
And I configure APT to prefer an old version of cowsay 0.000
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 0.000
And I accept adding "cowsay" to Additional Software 0.000
And Additional Software is correctly configured for package "cowsay" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.000
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
# We remove the newest package after it has been downloaded and before
# it is installed, so that the upgrade process fails
And I prepare the Additional Software upgrade process to fail 0.000
And the network is plugged 0.000
And Tor is ready 0.000
And available upgrades have been checked 0.000
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.000
And I can open the Additional Software configuration window from the notification 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
And the network is plugged 0.000
And Tor is ready 0.000
Then the Additional Software upgrade service has started 0.000
And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000
After features/support/hooks.rb:515 0.119
After features/support/hooks.rb:330 6.322

SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 02:16:58)

Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/02:16:58_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/02:16:58_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/02:16:58_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/02:16:58_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/02:16:58_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/02:16:58_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/02:16:58_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/02:16:58_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal

After features/support/hooks.rb:100 0.006
3:38.039
Scenario I am notified when Additional Software fails to install a package
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 a computer 0.243
And I start Tails from USB drive "__internal" with network unplugged 3:0.844
And I enable persistence 36.875
And I remove the "cowsay" deb files from the APT cache 0.076
Command failed: rm /live/persistence/TailsData_unlocked/apt/cache/cowsay_*.deb
error code: 1
stdout: 
stderr: rm: cannot remove '/live/persistence/TailsData_unlocked/apt/cache/cowsay_*.deb': No such file or directory
.
<false> is not true. (ExecutionFailedInVM)
./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/additional_software_packages.rb:134:in `/^I remove the "([^"]*)" deb files from the APT cache$/'
features/additional_software_packages.feature:124:in `And I remove the "cowsay" deb files from the APT cache'
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.000
And I log in to a new session 0.000
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 0.000
And I can open the Additional Software log file from the notification 0.000
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:515 0.059
After features/support/hooks.rb:330 5.743

SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 02:20:42)

Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/02:20:42_I_am_notified_when_Additional_Software_fails_to_install_a_package.file_content_var_log_boot.log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/02:20:42_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/02:20:42_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/02:20:42_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/02:20:42_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/02:20:42_I_am_notified_when_Additional_Software_fails_to_install_a_package.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/02:20:42_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/02:20:42_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal

After features/support/hooks.rb:100 0.007
23:40.160
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.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.920
And no SquashFS delta is installed 0.376
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.435
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.339
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.503
When the network is plugged 0.080
And Tor is ready 36.218
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:38.199
Tor
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderUpgradeTo6.2~testoverlayfs.png", "TailsUpgraderFailure.png"] on the screen (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/usb.rb:1301:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:90:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:330 12.245

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:15:23)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/03:15:23_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_ignore-private-backports/4/artifact/build-artifacts/03:15:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/03:15:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/03:15:23_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:100 0.000
24:29.407
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.187
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:23.513
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the signing key used by the Upgrader is outdated 0.106
But a current signing key is available on our website 0.000
When the network is plugged 0.220
And Tor is ready 25.217
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:38.908
Tor
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderUpgradeTo6.2~testoverlayfs.png", "TailsUpgraderFailure.png"] on the screen (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/usb.rb:1301:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:134:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
After features/support/hooks.rb:330 10.552

SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:40:05)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/03:40:05_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/03:40:05_Upgrading_a_Tails_whose_signing_key_is_outdated.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/03:40:05_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/03:40:05_Upgrading_a_Tails_whose_signing_key_is_outdated.journal

After features/support/hooks.rb:100 0.000
Tags: @product
2:12.391
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.042
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.238
# 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.153
And I clone USB drive "__internal" to a temporary USB drive "backup" 6.288
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:25.709
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81: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.593

SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 03:56:59)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/03:56:59_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_ignore-private-backports/4/artifact/build-artifacts/03:56:59_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/03:56:59_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/03:56:59_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal

After features/support/hooks.rb:100 0.224
1:40.149
Scenario The Tails documentation launcher works when offline
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 29.653
When I start "Tails Documentation" via GNOME Activities Overview 18.927
Then the Tor Browser has started 51.568
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:495:in `/^the Tor Browser (?:has started|starts)$/'
features/documentation.feature:7:in `Then the Tor Browser has started'
Then "Tails - Documentation" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 14.038

SCENARIO FAILED: 'The Tails documentation launcher works when offline' (at time 04:01:42)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/04:01:42_The_Tails_documentation_launcher_works_when_offline.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/04:01:42_The_Tails_documentation_launcher_works_when_offline.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/04:01:42_The_Tails_documentation_launcher_works_when_offline.journal

After features/support/hooks.rb:100 0.000
Feature: Using Evince
Tags: @product
1:16.428
Scenario I can view and print a PDF file stored in persistent /home/amnesia/Persistent
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 enabled and logged in 1:16.428
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:98:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:104:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:81: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:45: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/Persistent" as user "amnesia" 0.000
Then the file "/home/amnesia/Persistent/default-testpage.pdf" exists 0.000
When I open "/home/amnesia/Persistent/default-testpage.pdf" with Evince 0.000
Then I see "CupsTestPage.png" after at most 40 seconds 0.000
And I can print the current document to "/home/amnesia/Persistent/output.pdf" 0.000
After features/support/hooks.rb:330 6.620

SCENARIO FAILED: 'I can view and print a PDF file stored in persistent /home/amnesia/Persistent' (at time 04:09:00)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/04:09:00_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/04:09:00_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/04:09:00_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/04:09:00_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.journal

After features/support/hooks.rb:100 0.000
Tags: @product
53.566
Scenario I can launch various apps via GNOME Activities Overview
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
# Some apps (Electrum and Persistent Storage Backup) only start when
# a Persistent Storage is available.
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 37.376
# Some apps (Tor Browser) only start when the network is plugged.
And the network is plugged 1.686
And Tor is ready 14.504
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:688:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:642:in `/^Tor is ready$/'
features/gnome.feature:25:in `And Tor is ready'
And all notifications have disappeared 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I close the "tails-additional-software-config" window 0.000
When I start "Disks" via GNOME Activities Overview 0.000
# The close button of GNOME Disks is not accessible
And I close the "gnome-disks" window via Alt+F4 0.000
When I start "GNOME Terminal" via GNOME Activities Overview 0.000
And I close the "org.gnome.Terminal" window 0.000
When I start "Files" via GNOME Activities Overview 0.000
And I close the "org.gnome.Nautilus" window 0.000
When I start "Persistent Storage" via GNOME Activities Overview 0.000
And I close the "tps-frontend" window 0.000
When I start "Back Up Persistent Storage" via GNOME Activities Overview 0.000
And I close the "zenity" window 0.000
When I start "Pidgin" via GNOME Activities Overview 0.000
And I close the "Pidgin" window via Alt+F4 0.000
When I start "Thunderbird" via GNOME Activities Overview 0.000
And I close the "Thunderbird" window 0.000
When I start "Tor Browser" via GNOME Activities Overview 0.000
And I close the "Firefox" window 0.000
When I start "Unlock VeraCrypt Volumes" via GNOME Activities Overview 0.000
And I close the "unlock-veracrypt-volumes" window 0.000
When I start "Unsafe Browser" via GNOME Activities Overview 0.000
And I close the "Firefox" window 0.000
After features/support/hooks.rb:330 8.852

SCENARIO FAILED: 'I can launch various apps via GNOME Activities Overview' (at time 04:11:57)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/04:11:57_I_can_launch_various_apps_via_GNOME_Activities_Overview.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/04:11:57_I_can_launch_various_apps_via_GNOME_Activities_Overview.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/04:11:57_I_can_launch_various_apps_via_GNOME_Activities_Overview.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/04:11:57_I_can_launch_various_apps_via_GNOME_Activities_Overview.journal

After features/support/hooks.rb:100 0.000
Feature: Localization
4:30.450
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 18.215
When I log in to a new session in Chinese (zh_CN) 1:25.241
Then the keyboard layout is set to "cn" 1.761
When the network is plugged 1.582
And Tor is ready 41.992
Then I successfully start the Unsafe Browser 1:0.210
And I kill the Unsafe Browser 7.901
When I enable the screen keyboard 1.168
Then the screen keyboard works in Tor Browser 52.376
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:495:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:482:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:438:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:44:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 13.609

SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#2)' (at time 05:22:03)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/05:22:03_Tails_is_localized_for_every_tier-1_language,_Examples___2_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/05:22:03_Tails_is_localized_for_every_tier-1_language,_Examples___2_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/05:22:03_Tails_is_localized_for_every_tier-1_language,_Examples___2_.journal

After features/support/hooks.rb:100 0.011
Feature: Localization
3:16.039
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.003
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 12.828
When I log in to a new session in Hindi (hi) 1:7.779
Then the keyboard layout is set to "in" 0.159
When the network is plugged 0.091
And Tor is ready 24.982
Then I successfully start the Unsafe Browser 26.697
And I kill the Unsafe Browser 8.592
When I enable the screen keyboard 0.205
Then the screen keyboard works in Tor Browser 54.702
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:495:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:482:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:438:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:48: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 11.155

SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#6)' (at time 05:42:19)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/05:42:19_Tails_is_localized_for_every_tier-1_language,_Examples___6_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/05:42:19_Tails_is_localized_for_every_tier-1_language,_Examples___6_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/05:42:19_Tails_is_localized_for_every_tier-1_language,_Examples___6_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/05:42:19_Tails_is_localized_for_every_tier-1_language,_Examples___6_.journal

After features/support/hooks.rb:100 0.000
Feature: Localization
3:11.404
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 13.210
When I log in to a new session in Russian (ru) 1:6.541
Then the keyboard layout is set to "ru" 0.163
When the network is plugged 0.096
And Tor is ready 33.076
Then I successfully start the Unsafe Browser 24.537
And I kill the Unsafe Browser 8.274
When I enable the screen keyboard 0.842
Then the screen keyboard works in Tor Browser 44.660
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:495:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:482:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:438:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:53: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 "ru" 0.000
After features/support/hooks.rb:330 6.832

SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#11)' (at time 06:03:58)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/06:03:58_Tails_is_localized_for_every_tier-1_language,_Examples___11_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/06:03:58_Tails_is_localized_for_every_tier-1_language,_Examples___11_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/06:03:58_Tails_is_localized_for_every_tier-1_language,_Examples___11_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/06:03:58_Tails_is_localized_for_every_tier-1_language,_Examples___11_.journal

After features/support/hooks.rb:100 0.000
Tags: @product
10:5.552
Scenario Persistent Greeter options
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 1:15.181
When I enable persistence 1:30.785
Then no persistent Greeter options were restored 21.402
When I set all Greeter options to non-default values 1:15.903
And I log in to a new session in German (de) after having activated the Persistent Storage 1:21.981
Then all Greeter options are set to non-default values 0.257
When I cold reboot the computer 18.855
And the computer reboots Tails 3:1.511
Given I enable persistence 39.466
Then persistent Greeter options were restored 0.820
When I log in to a new session after having activated the Persistent Storage 19.386
The
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with name='Start Tails' roleName='button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/common_steps.rb:516:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/persistence.feature:113:in `When I log in to a new session after having activated the Persistent Storage'
Then all Greeter options are set to non-default values 0.000
After features/support/hooks.rb:330 9.735

SCENARIO FAILED: 'Persistent Greeter options' (at time 07:13:25)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/07:13:25_Persistent_Greeter_options.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/07:13:25_Persistent_Greeter_options.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/07:13:25_Persistent_Greeter_options.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/07:13:25_Persistent_Greeter_options.journal

After features/support/hooks.rb:100 0.046
Tags: @product
1:30.756
Scenario Changing the Persistent Storage passphrase
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.798
# 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:6.957
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:475:in `/^I change the passphrase of the Persistent Storage( back to the original)?$/'
features/persistence.feature:121:in `When I change the passphrase of the Persistent Storage'
And I shutdown Tails and wait for the computer to power off 0.000
Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 0.000
And I change the passphrase of the Persistent Storage back to the original 0.000
After features/support/hooks.rb:330 19.585

SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 07:15:06)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/07:15:06_Changing_the_Persistent_Storage_passphrase.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/07:15:06_Changing_the_Persistent_Storage_passphrase.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/07:15:06_Changing_the_Persistent_Storage_passphrase.journal

After features/support/hooks.rb:100 0.000
Tags: @product
55.360
Scenario Deleting a Tails persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 46.217
And I log in to a new session without activating the Persistent Storage 9.143
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/common_steps.rb:538:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/persistence.feature:128:in `And I log in to a new session without activating the Persistent Storage'
Then persistence is disabled 0.000
But a Tails persistence partition exists on USB drive "__internal" 0.000
And all notifications have disappeared 0.000
When I delete the persistent partition 0.000
Then there is no persistence partition on USB drive "__internal" 0.000
After features/support/hooks.rb:330 6.896

SCENARIO FAILED: 'Deleting a Tails persistent partition' (at time 07:16:20)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/07:16:20_Deleting_a_Tails_persistent_partition.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/07:16:20_Deleting_a_Tails_persistent_partition.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/07:16:20_Deleting_a_Tails_persistent_partition.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/07:16:20_Deleting_a_Tails_persistent_partition.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:17.890
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 12.995
And I create a symlink "/home/amnesia/Persistent" to "/etc" 1.248
When I try to enable persistence 3.551
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 1:0.095
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:1724:in `/^the Welcome Screen tells me that the Persistent Folder feature couldn't be activated$/'
features/persistence.feature:146:in `Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated'
When I log in to a new session after having activated the Persistent Storage 0.000
And all notifications have disappeared 0.000
Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 0.000
And all tps features are enabled 0.000
And all tps features but the first one are active 0.000
After features/support/hooks.rb:330 15.121

SCENARIO FAILED: 'Feature activation fails' (at time 07:23:39)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/07:23:39_Feature_activation_fails.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/07:23:39_Feature_activation_fails.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/07:23:39_Feature_activation_fails.journal

After features/support/hooks.rb:100 0.000
Tags: @product
1:58.018
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.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 15.158
And I capture all network traffic 0.009
When I successfully start the Unsafe Browser 24.525
And I open the Tails homepage in the Unsafe Browser 17.749
And the Tails homepage loads in the Unsafe Browser 1:0.575
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:345: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 7.214

SCENARIO FAILED: 'Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector' (at time 08:17:59)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/08:17:59_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/08:17:59_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_ignore-private-backports/4/artifact/build-artifacts/08:17:59_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_ignore-private-backports/4/artifact/build-artifacts/08:17:59_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.journal

After features/support/hooks.rb:100 0.040
Feature: Using Totem
Tags: @product
1:9.403
Scenario Watching a MP4 video stored on the non-persistent filesystem
Steps
Given I have started Tails from DVD without network and logged in 25.660
And I plug and mount a USB drive containing sample videos 18.925
And I copy the sample videos to "/home/amnesia" as user "amnesia" 0.099
And the file "/home/amnesia/video.mp4" exists 0.128
Given I start monitoring the AppArmor log of "/usr/bin/totem" 0.363
When I open "/home/amnesia/video.mp4" with Totem 4.428
Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 5.697
And AppArmor has not denied "/usr/bin/totem" from opening "/home/amnesia/video.mp4" 0.083
Given I close Totem 0.187
And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.089
And the file "/home/amnesia/.gnupg/video.mp4" exists 0.060
And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.128
When I try to open "/home/amnesia/.gnupg/video.mp4" with Totem 2.350
Then Totem tells me it is not allowed to open this file 11.200
The
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'totem' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/totem.rb:59:in `new'
./features/step_definitions/totem.rb:59:in `/^Totem tells me it is not allowed to open this file$/'
features/totem.feature:25:in `Then Totem tells me it is not allowed to open this file'
And AppArmor has denied "/usr/bin/totem" from opening "/home/amnesia/.gnupg/video.mp4" 0.000
Given I close Totem 0.000
And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" exists 0.000
And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.000
When I try to open "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" with Totem 0.000
Then Totem tells me it is not allowed to open this file 0.000
And AppArmor has denied "/usr/bin/totem" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" 0.000
Given I close Totem 0.000
And the file "/live/overlay/rw/home/amnesia/.gnupg/video.mp4" exists 0.000
And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.000
When I try to open "/live/overlay/rw/home/amnesia/.gnupg/video.mp4" with Totem 0.000
Then Totem tells me it is not allowed to open this file 0.000
# Due to our AppArmor aliases, /live/overlay will be treated
# as /usr/lib/live/mount/overlay.
And AppArmor has denied "/usr/bin/totem" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" 0.000
Given I close Totem 0.000
And I copy "/home/amnesia/video.mp4" to "/home/amnesia/.purple/otr.private_key" as user "amnesia" 0.000
And the file "/home/amnesia/.purple/otr.private_key" exists 0.000
And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.000
When I try to open "/home/amnesia/.purple/otr.private_key" with Totem 0.000
Then Totem tells me it is not allowed to open this file 0.000
And AppArmor has denied "/usr/bin/totem" from opening "/home/amnesia/.purple/otr.private_key" 0.000
After features/support/hooks.rb:330 6.849

SCENARIO FAILED: 'Watching a MP4 video stored on the non-persistent filesystem' (at time 08:58:01)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/08:58:01_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/08:58:01_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/08:58:01_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/08:58:01_Watching_a_MP4_video_stored_on_the_non-persistent_filesystem.journal

After features/support/hooks.rb:100 0.000
Feature: Using Totem
Tags: @product
59.873
Scenario Watching MP4 videos stored on the persistent volume should work as expected given our AppArmor confinement
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.374
And I plug and mount a USB drive containing sample videos 19.751
And I copy the sample videos to "/home/amnesia/Persistent" as user "amnesia" 0.070
When I open "/home/amnesia/Persistent/video.mp4" with Totem 4.693
Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 5.998
Given I close Totem 1.819
And I start monitoring the AppArmor log of "/usr/bin/totem" 0.259
And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.112
When I try to open "/home/amnesia/.gnupg/video.mp4" with Totem 2.379
Then Totem tells me it is not allowed to open this file 14.413
The
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'totem' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/totem.rb:59:in `new'
./features/step_definitions/totem.rb:59:in `/^Totem tells me it is not allowed to open this file$/'
features/totem.feature:64:in `Then Totem tells me it is not allowed to open this file'
And AppArmor has denied "/usr/bin/totem" from opening "/home/amnesia/.gnupg/video.mp4" 0.000
After features/support/hooks.rb:330 6.154

SCENARIO FAILED: 'Watching MP4 videos stored on the persistent volume should work as expected given our AppArmor confinement' (at time 08:59:37)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/08:59:37_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/08:59:37_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/08:59:37_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/08:59:37_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.journal

After features/support/hooks.rb:100 0.003
Tags: @product
1:56.590
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.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 16.291
When I successfully start the Unsafe Browser 23.595
When I open the Tails homepage in the Unsafe Browser 16.135
Then the Tails homepage loads in the Unsafe Browser 1:0.567
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:345: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 7.580

SCENARIO FAILED: 'The Unsafe Browser can load a web page from the Internet' (at time 09:05:24)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/09:05:24_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_ignore-private-backports/4/artifact/build-artifacts/09:05:24_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/09:05:24_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_ignore-private-backports/4/artifact/build-artifacts/09:05:24_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.journal

After features/support/hooks.rb:100 0.000