Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 108 01 Jul 2025, 20:17

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
42.779
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 1.941
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 24.479
Then the Tor Connection Assistant reports that it failed to connect 0.122
Given the Tor network and default bridges are unblocked 1.685
When I click "Connect to Tor" 1.164
Then I wait until Tor is ready 12.613
And Tor is configured to use the default bridges 0.602
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.171
Unexpected 
Unexpected connections were made
  #<OpenStruct mac_saddr="50:54:00:54:e7:43", mac_daddr="52:54:00:00:00:01", protocol="IP::TCP", saddr="10.2.1.192", daddr="38.145.60.20", sport=33966, dport=80> (FirewallAssertionFailedError)
./features/support/helpers/firewall_helper.rb:168:in `assert_all_connections'
./features/step_definitions/tor.rb:955:in `/^all Internet traffic has only flowed through (Tor|the \w+ bridges)( or (?:fake )?connectivity check service|)$/'
features/tor_bridges.feature:110:in `And all Internet traffic has only flowed through the default bridges or connectivity check service'
After features/support/hooks.rb:335 4.919 
SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 00:28:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/00:28:27_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.file_content_var_log_boot.log
Network capture: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/00:28:27_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.pcap
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/00:28:27_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/00:28:27_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/00:28:27_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal
After features/support/hooks.rb:105 0.041
Feature: Hardware failures
Tags: @product
4:55.644
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 27.454
And I corrupt the boot device's GPT backup partition table 0.445
And I power off the computer 0.352
When I start the computer 1.528
Then the computer boots Tails 1:20.129
When I log in to a new session 3:5.735
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/hardware_failure.feature:46:in `When I log in to a new session'
features/hardware_failure.feature:39:in `When I log in to a new session'
And all notifications have disappeared 0.000
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.000
And Tails detected partitioning error partitioning-corruption 0.000
After features/support/hooks.rb:335 5.527 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 02:39:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/02:39:18_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/02:39:18_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/02:39:18_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/02:39:18_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:105 0.010
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:7.557
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 10.625
When I log in to a new session in Chinese (zh_CN) 45.288
Then the keyboard layout is set to "cn" 0.127
When the network is plugged 0.067
And Tor is ready 11.448
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:45:in `And Tor is ready'
features/localization.feature:26:in `And Tor is ready'
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:335 6.051 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#2)' (at time 03:04:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/03:04:17_Tails_is_localized_for_every_tier-1_language,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/03:04:17_Tails_is_localized_for_every_tier-1_language,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/03:04:17_Tails_is_localized_for_every_tier-1_language,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/03:04:17_Tails_is_localized_for_every_tier-1_language,_Examples___2_.journal
After features/support/hooks.rb:105 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:28.993
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.088
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 14.314
When I log in to a new session in Russian (ru) 43.604
Then the keyboard layout is set to "ru" 0.323
When the network is plugged 0.224
And Tor is ready 24.974
Then I successfully start the Unsafe Browser 27.080
And I kill the Unsafe Browser 6.926
When I enable the screen keyboard 0.105
Then the screen keyboard works in Tor Browser 31.439
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:411:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:55: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:335 6.674 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#9)' (at time 03:30:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/03:30:44_Tails_is_localized_for_every_tier-1_language,_Examples___9_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/03:30:44_Tails_is_localized_for_every_tier-1_language,_Examples___9_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/03:30:44_Tails_is_localized_for_every_tier-1_language,_Examples___9_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/03:30:44_Tails_is_localized_for_every_tier-1_language,_Examples___9_.journal
After features/support/hooks.rb:105 0.000
Feature: The Tor enforcement is effective
Tags: @product
2:4.581
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.093
Steps
Given I have started Tails from DVD and logged in and the network is connected 16.974
And I capture all network traffic 0.040
When I successfully start the Unsafe Browser 29.713
And I open the Tails homepage in the Unsafe Browser 17.539
And the Tails homepage loads in the Unsafe Browser 1:0.313
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 7.411 
SCENARIO FAILED: 'Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector' (at time 05:25:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/05:25:03_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/108/artifact/build-artifacts/05:25:03_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/108/artifact/build-artifacts/05:25:03_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/108/artifact/build-artifacts/05:25:03_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:105 0.046
Feature: Browsing the web using the Unsafe Browser
Tags: @product
2:6.605
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.009
Steps
Given I have started Tails from DVD and logged in and the network is connected 20.533
When I successfully start the Unsafe Browser 32.541
When I open the Tails homepage in the Unsafe Browser 12.208
Then the Tails homepage loads in the Unsafe Browser 1:1.322
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 7.288 
SCENARIO FAILED: 'The Unsafe Browser can load a web page from the Internet' (at time 06:10:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/06:10:38_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/108/artifact/build-artifacts/06:10:38_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/108/artifact/build-artifacts/06:10:38_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/108/artifact/build-artifacts/06:10:38_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
45.549
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 35.014
And I unlock and mount this VeraCrypt file container with GNOME Disks 10.535
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.253 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 06:24:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/108/artifact/build-artifacts/06:24:57_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/108/artifact/build-artifacts/06:24:57_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/108/artifact/build-artifacts/06:24:57_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/108/artifact/build-artifacts/06:24:57_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:105 0.014