Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 111 04 Jul 2025, 20:04

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow
4:38.107
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.014
Before features/support/hooks.rb:512 0.017
Steps
Given a computer 0.433
And I start Tails from USB drive "__internal" and I login with an administration password 4:37.674
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:566:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:522:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
./features/step_definitions/common_steps.rb:295: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:520 0.042
After features/support/hooks.rb:335 5.453 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:15:56)
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_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/01:15:56_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_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/01:15:56_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_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/01:15:56_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_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/01:15:56_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_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/01:15:56_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_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/01:15:56_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_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/01:15:56_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_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/01:15:56_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:105 0.011
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
5:10.869
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.122
And no SquashFS delta is installed 0.648
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.559
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.122
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.350
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.088
And Tor is ready 28.649
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.120
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.931
Given I shutdown Tails and wait for the computer to power off 15.840
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:47.045
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.705
And the file system changes introduced in version 6.2~testoverlayfs are present 0.373
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.466
When the network is plugged 0.100
And Tor is ready 29.166
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.781
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.927
cannot 
cannot find TailsUpgraderApplyUpgradeButton.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/usb.rb:1327:in `/^I can successfully install the incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:107:in `And I can successfully install the incremental upgrade to version 6.3~testoverlayfs'
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:335 5.437 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:02:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/02:02:34_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_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/02:02:34_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/02:02:34_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/02:02:34_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:105 0.009
Feature: Tails persistence
Tags: @product
22.245
Scenario Booting Tails from a USB drive with a disabled persistent partition
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 13.547
When I log in to a new session without activating the Persistent Storage 8.698
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/common_steps.rb:519:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/persistence.feature:14:in `When I log in to a new session without activating the Persistent Storage'
Then Tails is running from USB drive "__internal" 0.000
And persistence is disabled 0.000
But a Tails persistence partition exists on USB drive "__internal" 0.000
After features/support/hooks.rb:335 5.527 
SCENARIO FAILED: 'Booting Tails from a USB drive with a disabled persistent partition' (at time 03:53:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/03:53:15_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/03:53:15_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/03:53:15_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/03:53:15_Booting_Tails_from_a_USB_drive_with_a_disabled_persistent_partition.journal
After features/support/hooks.rb:105 0.000
Feature: Tails persistence
Tags: @product @doc
3:58.854
Scenario Manual filesystem repair fails
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.013
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 16.343
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.116
When I try to enable persistence 1.495
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 50.470
When I repair the filesystem of the Persistent Storage 3.398
Then the Welcome Screen tells me that it failed to repair the Persistent Storage 0.135
When I log in to a new session 48.210
And all notifications have disappeared 1:58.683
Operation 
Operation failed (despite retrying 10 times) with
Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | ]: child with name="Do Not Disturb" roleName='label'
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/step_definitions/common_steps.rb:720:in `/^all notifications have disappeared$/'
features/persistence.feature:192:in `And all notifications have disappeared'
# Now both WhisperBack and Tor Browser has started at the same
# time, so we do not know which window is focused. The steps about
# Tor Browser care about that, but the ones about WhisperBack do
# not, so we first deal with WhisperBack and then kill it to
# ensure that Tor Browser is focused.
Then WhisperBack is prefilled for fsck with summary: "Failed to repair the file system of your Persistent Storage" 0.000
And the file "/var/lib/gdm3/post-greeter-whisperback.json" is empty 0.000
When I close the "whisperback" window 0.000
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:335 9.039 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 04:43:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/04:43:23_Manual_filesystem_repair_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/04:43:23_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/04:43:23_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/04:43:23_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:105 0.000
Feature: Using persistent Tor bridges and pluggable transports
5:20.963
Background
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 15.088
And I create a persistent partition with the default settings 30.527
Then the "TorConfiguration" tps feature is not enabled 4.250
When the network is plugged 1.328
And the Tor Connection Assistant autostarts 9.777
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 12.199
And I wait until Tor is ready 4.690
Then tca.conf includes the configured bridges 0.013
And the "TorConfiguration" tps feature is enabled and active 1.158
When I cold reboot the computer 16.066
And the computer reboots Tails 1:22.603
And I enable persistence 38.417
And I capture all network traffic 0.008
And I log in to a new session 44.746
Then tca.conf includes the configured bridges 0.013
When the network is plugged 0.072
And the Tor Connection Assistant autostarts 1:0.001
TCA 
TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
features/persistent_tor_bridges.feature:24:in `And the Tor Connection Assistant autostarts'
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:335 14.410 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 04:57:20)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/04:57:20_Disabling_persistence_of_Tor_bridges_chutney-data
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/04:57:20_Disabling_persistence_of_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/04:57:20_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/04:57:20_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:105 0.068
Feature: The Tor enforcement is effective
Tags: @product
1:54.094
Scenario Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.017
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.456
And I capture all network traffic 0.195
When I successfully start the Unsafe Browser 27.773
And I open the Tails homepage in the Unsafe Browser 11.993
And the Tails homepage loads in the Unsafe Browser 1:0.675
cannot 
cannot find TailsHomepage.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:316:in `/^the Tails homepage loads in the Unsafe Browser$/'
features/tor_enforcement.feature:20:in `And the Tails homepage loads in the Unsafe Browser'
Then the firewall leak detector has detected leaks 0.000
After features/support/hooks.rb:335 5.864 
SCENARIO FAILED: 'Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector' (at time 05:16:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/05:16:31_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_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/05:16:31_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_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/05:16:31_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_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/05:16:31_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:105 0.033
Feature: Browsing the web using the Unsafe Browser
Tags: @product
2:3.517
Scenario The Unsafe Browser can load a web page from the Internet
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.054
Steps
Given I have started Tails from DVD and logged in and the network is connected 17.839
When I successfully start the Unsafe Browser 30.108
When I open the Tails homepage in the Unsafe Browser 11.201
Then the Tails homepage loads in the Unsafe Browser 1:4.367
cannot 
cannot find TailsHomepage.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:316:in `/^the Tails homepage loads in the Unsafe Browser$/'
features/unsafe_browser.feature:38:in `Then the Tails homepage loads in the Unsafe Browser'
And the Unsafe Browser has sent packets out to the Internet 0.000
After features/support/hooks.rb:335 5.903 
SCENARIO FAILED: 'The Unsafe Browser can load a web page from the Internet' (at time 06:00:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/06:00:13_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_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/06:00:13_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/06:00:13_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/06:00:13_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.journal
After features/support/hooks.rb:105 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
44.029
Scenario Use GNOME Disks to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 32.952
And I unlock and mount this VeraCrypt file container with GNOME Disks 11.076
The 
The Dogtail init script raised: ActionNotSupported: Cannot do 'activate' action on [DEAD]
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:346:in `call_tree_node_method'
./features/support/helpers/dogtail.rb:350:in `doActionNamed'
./features/support/helpers/dogtail.rb:364:in `activate'
./features/step_definitions/veracrypt.rb:240:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:76:in `And I unlock and mount this VeraCrypt file container with GNOME Disks'
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:335 7.816 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 06:14:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/06:14:51_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/06:14:51_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/06:14:51_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/06:14:51_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:105 0.017