Cucumber Reports (no 18) - Failures Overview

Project	Number	Date
test_Tails_ISO_21461-update-chutney	18	09 Aug 2026, 22:19

Feature: Additional software

3:5.277

Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.001

Before features/support/hooks.rb:527 0.001

Steps

Given a computer 0.075

And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:12.129

And I configure APT to prefer an old version of cowsay 0.005

When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 5.665

And I accept adding "cowsay" to Additional Software 3.989

And Additional Software is correctly configured for package "cowsay" 0.437

And I shutdown Tails and wait for the computer to power off 2.536

And I start Tails from USB drive "__internal" with network unplugged 32.374

And I enable persistence 10.258

# 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.004

# 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.041

And I log in to a new session 7.465

And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been installed 10.161

And I revert the APT tweaks that made it prefer an old version of cowsay 0.032

# 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.035

And the network is plugged 0.037

And Tor is ready 12.266

And available upgrades have been checked 0.039

And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.306

And I can open the Additional Software configuration window from the notification 26.415

The

The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with roleName='notification'
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/additional_software_packages.rb:33:in `click_gnome_shell_notification_button'
./features/step_definitions/additional_software_packages.rb:160:in `/^I can open the Additional Software configuration window from the notification$/'
features/additional_software_packages.feature:103:in `And I can open the Additional Software configuration window from the notification'

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 installed 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

Hooks

After features/support/hooks.rb:535 0.055

After features/support/hooks.rb:339 5.424

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21461-update-chutney/18/artifact/build-artifacts/01:03:27_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_21461-update-chutney/18/artifact/build-artifacts/01:03:27_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_21461-update-chutney/18/artifact/build-artifacts/01:03:27_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_21461-update-chutney/18/artifact/build-artifacts/01:03:27_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_21461-update-chutney/18/artifact/build-artifacts/01:03:27_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_21461-update-chutney/18/artifact/build-artifacts/01:03:27_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_21461-update-chutney/18/artifact/build-artifacts/01:03:27_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_21461-update-chutney/18/artifact/build-artifacts/01:03:27_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_21461-update-chutney/18/artifact/build-artifacts/01:03:27_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal

After features/support/hooks.rb:108 0.009

Feature: The Tor enforcement is effective

Tags: @product

9.688

Scenario Anti test: Detecting TCP leaks of DNS lookups with the firewall leak detector

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.002

Steps

Given I have started Tails from DVD and logged in and the network is connected 9.414

And I capture all network traffic 0.004

And I disable Tails' firewall 0.103

When I do a TCP DNS lookup of "torproject.org" 0.164

Failed

Failed to resolve torproject.org:
;; communications error to 9.9.9.9#53: connection reset
;; communications error to 9.9.9.9#53: connection reset
;; no servers could be reached
.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/firewall_leaks.rb:22:in `/^I do a TCP DNS lookup of "(.*?)"$/'
features/tor_enforcement.feature:28:in `When I do a TCP DNS lookup of "torproject.org"'

Then the firewall leak detector has detected leaks 0.000

Hooks

After features/support/hooks.rb:339 5.112

Output 1

SCENARIO FAILED: 'Anti test: Detecting TCP leaks of DNS lookups with the firewall leak detector' (at time 03:16:04)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21461-update-chutney/18/artifact/build-artifacts/03:16:04_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21461-update-chutney/18/artifact/build-artifacts/03:16:04_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21461-update-chutney/18/artifact/build-artifacts/03:16:04_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21461-update-chutney/18/artifact/build-artifacts/03:16:04_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.journal

After features/support/hooks.rb:108 0.048

Feature: Browsing the web using the Tor Browser

Tags: @product

3:59.526

Scenario Persistent browser bookmarks

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.003

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.249

And all tps features are active 8.278

And all persistent filesystems have safe access rights 0.165

And all persistence configuration files have safe access rights 0.302

And all persistent directories have safe access rights 1.901

When I start the Tor Browser in offline mode 13.750

And I add a bookmark to eff.org in the Tor Browser 8.021

And I cold reboot the computer 6.152

And the computer reboots Tails 34.194

And I enable persistence 13.845

And I log in to a new session 6.664

And all notifications have disappeared 8.649

And I start the Tor Browser in offline mode 2:9.350

try_for()

try_for() timeout expired
Last ignored exception was: FindFailed: can still find TorBrowserStopButton.png on the screen
./features/support/helpers/screen.rb:207:in `rescue in wait_vanish'
./features/support/helpers/screen.rb:192:in `wait_vanish'
./features/step_definitions/browser.rb:522:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
<internal:kernel>:187:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/browser.rb:518:in `block in <top (required)>'
./features/step_definitions/browser.rb:507:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:518:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:507:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:142:in `And I start the Tor Browser in offline mode'

Then the Tor Browser has a bookmark to eff.org 0.000

Hooks

After features/support/hooks.rb:339 5.179

Output 1

SCENARIO FAILED: 'Persistent browser bookmarks' (at time 03:33:05)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21461-update-chutney/18/artifact/build-artifacts/03:33:05_Persistent_browser_bookmarks.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21461-update-chutney/18/artifact/build-artifacts/03:33:05_Persistent_browser_bookmarks.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21461-update-chutney/18/artifact/build-artifacts/03:33:05_Persistent_browser_bookmarks.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21461-update-chutney/18/artifact/build-artifacts/03:33:05_Persistent_browser_bookmarks.journal

After features/support/hooks.rb:108 0.011