Project Number Date
test_Tails_ISO_stable 6566 08 Aug 2026, 11:46

Failures Overview

The following summary displays scenarios that failed.

Feature: Packages are up-to-date
Tags: @source @fragile
2.895
Scenario All packages are up-to-date
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:552 0.000
Steps
Given I have the build manifest for the image under test 0.000
Then all packages listed in the build manifest are up-to-date 2.895
Command 
Command failed (pid 120509 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_stable/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_stable/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-7.10.1.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-7.10.1.build-manifest
INFO: Last successful auto-update of the UDD mirror: 2026-08-08 10:05:02+00:00 (0:04:10.345952 ago)
INFO: Need to upgrade to a new APT snapshot:
  - aom (3.12.1-1) to Debian trixie-security (3.12.1-1+deb13u1)
  - jq[jq] (1.7.1-6+deb13u2) to Debian trixie-security (1.7.1-6+deb13u3)
  - jq[libjq1] (1.7.1-6+deb13u2) to Debian trixie-security (1.7.1-6+deb13u3)
  - libde265 (1.0.15-1+b3) to Debian trixie-security (1.0.15-1+deb13u1)
  - libheif[heif-gdk-pixbuf, heif-thumbnailer] (1.19.8-1) to Debian trixie-security (1.19.8-1+deb13u1)
  - libheif[libheif-plugin-dav1d, libheif1, libheif-plugin-libde265] (1.19.8-1) to Debian trixie-security (1.19.8-1+deb13u1)
  - linux-signed-amd64[linux-headers-amd64, linux-image-amd64] (6.12.100-1) to Debian trixie-security (6.12.101+1)
  - linux[linux-libc-dev] (6.12.100-1) to Debian trixie-security (6.12.101-1)
  - thunderbird (1:140.12.0esr-1~deb13u1) to Debian trixie-security (1:140.13.0esr-2~deb13u1)
  - udisks2[gir1.2-udisks-2.0] (2.10.1-12.1+deb13u1) to Debian trixie-security (2.10.1-12.1+deb13u2)
  - udisks2[libudisks2-0] (2.10.1-12.1+deb13u1) to Debian trixie-security (2.10.1-12.1+deb13u2)
  - udisks2[udisks2] (2.10.1-12.1+deb13u1) to Debian trixie-security (2.10.1-12.1+deb13u2)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:332:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:319:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:319:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/step_definitions/needed_package_updates.rb:10:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:13:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:559 0.000
After features/support/hooks.rb:108 0.000
Feature: Tails persistence
Tags: @product
4:40.777
Scenario Changing the Persistent Storage passphrase
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.662
# 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 31.162
And I shutdown Tails and wait for the computer to power off 5.307
Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 3:55.645
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:603:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:544: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:251: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/persistence.feature:130:in `Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase'
And I change the passphrase of the Persistent Storage back to the original 0.000
After features/support/hooks.rb:339 4.883 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 02:43:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6566/artifact/build-artifacts/02:43:30_Changing_the_Persistent_Storage_passphrase.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6566/artifact/build-artifacts/02:43:30_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6566/artifact/build-artifacts/02:43:30_Changing_the_Persistent_Storage_passphrase.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6566/artifact/build-artifacts/02:43:30_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:108 0.048
Feature: The Tor enforcement is effective
Tags: @product
9.958
Scenario Anti test: Detecting TCP leaks of DNS lookups with the firewall leak detector
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 9.706
And I capture all network traffic 0.004
And I disable Tails' firewall 0.106
When I do a TCP DNS lookup of "torproject.org" 0.142
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
After features/support/hooks.rb:339 4.771 
SCENARIO FAILED: 'Anti test: Detecting TCP leaks of DNS lookups with the firewall leak detector' (at time 03:27:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6566/artifact/build-artifacts/03:27:36_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_stable/6566/artifact/build-artifacts/03:27:36_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6566/artifact/build-artifacts/03:27:36_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_stable/6566/artifact/build-artifacts/03:27:36_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:108 0.058