Project Number Date
test_Tails_ISO_21027-fix-interactive-debugging-context 4 19 Jun 2025, 00:59

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
14:26.247
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.005
Before features/support/hooks.rb:509 0.005
Steps
Given a computer 0.185
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 3:30.668
And I configure APT to prefer an old version of cowsay 0.058
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 35.875
And I accept adding "cowsay" to Additional Software 9.296
And Additional Software is correctly configured for package "cowsay" 1.085
And I shutdown Tails and wait for the computer to power off 12.358
And I start Tails from USB drive "__internal" with network unplugged 1:31.153
And I enable persistence 25.024
# 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.081
# 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.177
And I log in to a new session 54.148
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 56.745
And I revert the APT tweaks that made it prefer an old version of cowsay 0.085
# 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.107
And the network is plugged 0.102
And Tor is ready 36.665
And available upgrades have been checked 1.234
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 4.112
And I can open the Additional Software configuration window from the notification 8.954
And I shutdown Tails and wait for the computer to power off 22.382
And I start Tails from USB drive "__internal" with network unplugged 1:44.050
And I enable persistence 26.188
# 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.030
And I log in to a new session 1:20.580
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 1:2.223
And I revert the APT tweaks that made it prefer an old version of cowsay 1.624
And the network is plugged 3.218
And Tor is ready 17.825
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/additional_software_packages.feature:114:in `And Tor is ready'
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:517 0.117
After features/support/hooks.rb:330 9.039 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:44:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/01:44:53_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/01:44:53_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.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_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/01:44:53_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_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/01:44:53_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_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/01:44:53_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_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/01:44:53_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_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/01:44:53_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_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/01:44:53_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_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/01:44:53_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.033
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
1:20.930
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.027
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:20.930
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_upgrade.feature:82:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And no SquashFS delta is installed 0.000
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.000
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:330 6.536 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:13:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/02:13:55_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_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/02:13:55_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/02:13:55_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/02:13:55_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Feature: Emergency shutdown
Tags: @product @not_release_blocker
1:18.034
Scenario Tails erases memory on DVD boot medium removal: overlayfs read-write branch
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:18.034
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/emergency_shutdown.feature:17:in `Given I have started Tails from DVD without network and logged in'
And I prepare Tails for memory erasure tests 0.000
And I fill a 128 MiB file with a known pattern on the root filesystem 0.000
And patterns cover at least 128 MiB in the guest's memory 0.000
When I eject the boot medium 0.000
And I wait for Tails to finish wiping the memory 0.000
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:330 5.734 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: overlayfs read-write branch' (at time 02:18:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/02:18:36_Tails_erases_memory_on_DVD_boot_medium_removal:_overlayfs_read-write_branch.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/02:18:36_Tails_erases_memory_on_DVD_boot_medium_removal:_overlayfs_read-write_branch.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/02:18:36_Tails_erases_memory_on_DVD_boot_medium_removal:_overlayfs_read-write_branch.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/02:18:36_Tails_erases_memory_on_DVD_boot_medium_removal:_overlayfs_read-write_branch.journal
After features/support/hooks.rb:100 0.000
Feature: Emergency shutdown
Tags: @product @not_release_blocker
1:14.492
Scenario Tails erases memory and shuts down on USB boot medium removal: persistent data
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 1:14.492
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/emergency_shutdown.feature:48: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
And I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
And patterns cover at least 100 MiB in the guest's memory 0.000
When I eject the boot medium 0.000
And I wait for Tails to finish wiping the memory 0.000
Then I find very few patterns in the guest's memory 0.000
And Tails eventually shuts down 0.000
After features/support/hooks.rb:330 6.889 
SCENARIO FAILED: 'Tails erases memory and shuts down on USB boot medium removal: persistent data' (at time 02:23:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/02:23:37_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/02:23:37_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/02:23:37_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/02:23:37_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.journal
After features/support/hooks.rb:100 0.000
Feature: Tails documentation
Tags: @product @doc @not_release_blocker
21.397
Scenario The Tails documentation launcher works when offline
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.216
Steps
Given I have started Tails from DVD without network and logged in 10.108
When I start "Tails Documentation" via GNOME Activities Overview 11.289
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:1141:in `/^I start "([^"]+)" via GNOME Activities Overview$/'
features/documentation.feature:6:in `When I start "Tails Documentation" via GNOME Activities Overview'
Then the Tor Browser has started 0.000
Then "Tails - Documentation" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 5.880 
SCENARIO FAILED: 'The Tails documentation launcher works when offline' (at time 02:31:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/02:31:37_The_Tails_documentation_launcher_works_when_offline.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/02:31:37_The_Tails_documentation_launcher_works_when_offline.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/02:31:37_The_Tails_documentation_launcher_works_when_offline.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/02:31:37_The_Tails_documentation_launcher_works_when_offline.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:9.560
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 12.915
When I log in to a new session in Turkish (tr) 44.213
Then the keyboard layout is set to "tr" 0.244
When the network is plugged 0.110
And Tor is ready 12.075
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/localization.feature:57: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 5.398 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#11)' (at time 03:53:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/03:53:10_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_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/03:53:10_Tails_is_localized_for_every_tier-1_language,_Examples___11_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/03:53:10_Tails_is_localized_for_every_tier-1_language,_Examples___11_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/03:53:10_Tails_is_localized_for_every_tier-1_language,_Examples___11_.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:13.774
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 29.287
And a web server is running on the LAN 1.458
And I capture all network traffic 0.035
When I start the Tor Browser 42.993
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:11:in `When I start the Tor Browser'
And the Tor Browser loads the startup page 0.000
And I open a page on the LAN web server in the Tor Browser 0.000
Then the Tor Browser shows the "Unable to connect" error 0.000
And no traffic was sent to the web server on the LAN 0.000
After features/support/hooks.rb:330 6.593 
SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 05:48:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/05:48:38_The_Tor_Browser_cannot_access_the_LAN.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/05:48:38_The_Tor_Browser_cannot_access_the_LAN.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/05:48:38_The_Tor_Browser_cannot_access_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/05:48:38_The_Tor_Browser_cannot_access_the_LAN.journal
After features/support/hooks.rb:100 0.056
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
1:13.275
Scenario The Downloads directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.151
Before features/support/hooks.rb:509 0.144
Steps
Given I have started Tails from DVD and logged in and the network is connected 24.482
Then the live user's Downloads directory exists 0.528
And there is a GNOME bookmark for the Downloads directory 7.285
When I start the Tor Browser 40.980
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:22:in `When I start the Tor Browser'
And the Tor Browser loads the startup page 0.000
Then I can save the current page as "index.html" to the Downloads directory 0.000
And I can print the current page as "output.pdf" to the Downloads directory 0.000
After features/support/hooks.rb:517 0.039
After features/support/hooks.rb:330 8.867 
SCENARIO FAILED: 'The Downloads directory is usable in Tor Browser' (at time 05:49:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/05:49:59_The_Downloads_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/05:49:59_The_Downloads_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/05:49:59_The_Downloads_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/05:49:59_The_Downloads_directory_is_usable_in_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
2:14.828
Scenario I can view a file stored in "~/Downloads" but not in ~/.gnupg
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Steps
Given I have started Tails from DVD and logged in and the network is connected 36.419
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/Downloads/synaptic.html" as user "amnesia" 0.119
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/.gnupg/synaptic.html" as user "amnesia" 0.081
And I copy "/usr/share/synaptic/html/index.html" to "/tmp/synaptic.html" as user "amnesia" 0.069
Then the file "/home/amnesia/.gnupg/synaptic.html" exists 0.054
And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.077
And the file "/live/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.067
And the file "/tmp/synaptic.html" exists 0.058
Given I start monitoring the AppArmor log of "torbrowser_firefox" 0.156
When I start the Tor Browser 44.412
And the Tor Browser loads the startup page 1.221
And I open the address "file:///home/amnesia/Downloads/synaptic.html" in the Tor Browser 28.947
Then I see "TorBrowserSynapticManual.png" after at most 5 seconds 3.269
And AppArmor has not denied "torbrowser_firefox" from opening "/home/amnesia/Downloads/synaptic.html" 0.394
When I open the address "file:///home/amnesia/.gnupg/synaptic.html" in the Tor Browser 7.226
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 12.252
can 
can still find TorBrowserSynapticManual.png on the screen (FindFailed)
./features/support/helpers/screen.rb:207:in `rescue in wait_vanish'
./features/support/helpers/screen.rb:192:in `wait_vanish'
./features/step_definitions/common_steps.rb:757:in `/^I (do not )?see "([^"]*)" after at most (\d+) seconds$/'
features/torified_browsing.feature:65:in `Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds'
When I open the address "file:///lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
When I open the address "file:///live/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
When I open the address "file:///tmp/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
After features/support/hooks.rb:330 7.013 
SCENARIO FAILED: 'I can view a file stored in "~/Downloads" but not in ~/.gnupg' (at time 05:59:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/05:59:57_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/05:59:57_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/05:59:57_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/05:59:57_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:13.509
Scenario The Tor Browser uses TBB's shared libraries
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Steps
Given I have started Tails from DVD and logged in and the network is connected 30.330
When I start the Tor Browser 43.179
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:75:in `When I start the Tor Browser'
Then the Tor Browser uses all expected TBB shared libraries 0.000
After features/support/hooks.rb:330 6.761 
SCENARIO FAILED: 'The Tor Browser uses TBB's shared libraries' (at time 06:01:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/06:01:17_The_Tor_Browser_uses_TBB_s_shared_libraries.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/06:01:17_The_Tor_Browser_uses_TBB_s_shared_libraries.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/06:01:17_The_Tor_Browser_uses_TBB_s_shared_libraries.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/06:01:17_The_Tor_Browser_uses_TBB_s_shared_libraries.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
1:14.132
Scenario The Tor Browser's "New identity" feature works as expected
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:509 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 30.595
When I start the Tor Browser 43.537
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:81:in `When I start the Tor Browser'
And the Tor Browser loads the startup page 0.000
When I open the address "https://example.com/" in the Tor Browser 0.000
Then Tor Browser displays a "Example Domain" heading on the "Example Domain" page 0.000
And the Tor Browser has 2 tabs open 0.000
When I request a new identity in Tor Browser 0.000
Then the Tor Browser loads the startup page 0.000
And the Tor Browser has 1 tab open 0.000
After features/support/hooks.rb:517 0.032
After features/support/hooks.rb:330 9.871 
SCENARIO FAILED: 'The Tor Browser's "New identity" feature works as expected' (at time 06:02:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/06:02:38_The_Tor_Browser_s__New_identity__feature_works_as_expected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/06:02:38_The_Tor_Browser_s__New_identity__feature_works_as_expected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/06:02:38_The_Tor_Browser_s__New_identity__feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/06:02:38_The_Tor_Browser_s__New_identity__feature_works_as_expected.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
42.583
Scenario Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile
Steps
When I plug a USB drive containing a basic VeraCrypt volume with a keyfile 8.339
And I cancel the GNOME authentication prompt 1.993
And I unlock and mount this VeraCrypt volume with GNOME Disks 32.250
The 
The Dogtail init script raised: SearchError: descendent of [application | gnome-disks]: child with name="Select a Keyfile" roleName='file chooser'
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/veracrypt.rb:269:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:51:in `And I unlock and mount this VeraCrypt volume with GNOME Disks'
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt volume 0.000
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.915 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 06:42:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/06:42:37_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/06:42:37_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/06:42:37_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/4/artifact/build-artifacts/06:42:37_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.journal
After features/support/hooks.rb:100 0.000