Project Number Date
test_Tails_ISO_stable 6506 15 Jul 2026, 07:41

Failures Overview

The following summary displays scenarios that failed.

Feature: Packages are up-to-date
Tags: @source @fragile
0.730
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 0.730
Command 
Command failed (pid 70977 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-stable@b5a5a57f8b-20260715T0312Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@b5a5a57f8b-20260715T0312Z.build-manifest
INFO: Last successful auto-update of the UDD mirror: 2026-07-15 04:05:03+00:00 (1:58:45.765951 ago)
INFO: Need to upgrade to a new APT snapshot:
  - base-files (13.8+deb13u5) to Debian trixie (13.8+deb13u6)
  - curl[curl] (8.14.1-2+deb13u3) to Debian trixie (8.14.1-2+deb13u4)
  - curl[libcurl3t64-gnutls, libcurl4t64] (8.14.1-2+deb13u3) to Debian trixie (8.14.1-2+deb13u4)
  - dhcpcd (1:10.1.0-11+deb13u2) to Debian trixie (1:10.1.0-11+deb13u3)
  - giflib (5.2.2-1+b1) to Debian trixie (5.2.2-1+deb13u1)
  - gnupg2[dirmngr, gpg-agent, gpg, gpgconf, gpgsm] (2.4.7-21+deb13u1+b3) to Debian trixie (2.4.7-21+deb13u1)
  - gnupg2[scdaemon] (2.4.7-21+deb13u1+b3) to Debian trixie (2.4.7-21+deb13u1)
  - graphite2 (1.3.14-2+b1) to Debian trixie (1.3.14-2+deb13u1)
  - libass (1:0.17.3-1+b1) to Debian trixie (1:0.17.3-1+deb13u1)
  - libcaca (0.99.beta20-5) to Debian trixie (0.99.beta20-5+deb13u1)
  - libhtml-parser-perl (3.83-1+b2) to Debian trixie (3.83-2~deb13u1)
  - libtasn1-6 (4.20.0-2) to Debian trixie (4.20.0-2+deb13u1)
  - libxml-libxml-perl (2.0207+dfsg+really+2.0134-5+b2) to Debian trixie (2.0207+dfsg+really+2.0134-5+deb13u1)
  - libxml2 (2.12.7+dfsg+really2.9.14-2.1+deb13u2) to Debian trixie (2.12.7+dfsg+really2.9.14-2.1+deb13u3)
  - libxpm (1:3.5.17-1+b3) to Debian trixie (1:3.5.17-1+deb13u1)
  - mesa[libgbm1, libegl-mesa0] (25.0.7-2) to Debian trixie (25.0.7-2+deb13u1)
  - mesa[libglx-mesa0, libgl1-mesa-dri] (25.0.7-2) to Debian trixie (25.0.7-2+deb13u1)
  - mesa[mesa-vulkan-drivers, mesa-libgallium] (25.0.7-2) to Debian trixie (25.0.7-2+deb13u1)
  - opencc (1.1.9+ds1-1) to Debian trixie (1.1.9+ds1-1+deb13u1)
  - protobuf[libprotobuf32t64] (3.21.12-11) to Debian trixie (3.21.12-11+deb13u1)
  - protobuf[python3-protobuf] (3.21.12-11) to Debian trixie (3.21.12-11+deb13u1)
  - python-idna (3.10-1) to Debian trixie (3.10-1+deb13u1)
  - python3.13[libpython3.13, libpython3.13-minimal, libpython3.13-stdlib] (3.13.5-2+deb13u2) to Debian trixie (3.13.5-2+deb13u3)
  - python3.13[python3.13-minimal, python3.13] (3.13.5-2+deb13u2) to Debian trixie (3.13.5-2+deb13u3)
  - shim (15.8-1) to Debian trixie (16.1-2~deb13u1)
  - shim-helpers-amd64-signed (1+15.8+1) to Debian trixie (1+16.1+2~deb13u1)
  - shim-signed (1.47+15.8-1) to Debian trixie (1.51~1+deb13u1)
  - wireless-regdb (2026.02.04-1~deb13u1) to Debian trixie (2026.05.30-1~deb13u1)
  - xz-utils[liblzma5] (5.8.1-1) to Debian trixie (5.8.1-1+deb13u1)
  - xz-utils[xz-utils] (5.8.1-1) to Debian trixie (5.8.1-1+deb13u1)
 (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
2:8.369
Scenario LUKS backup header is restored if something goes wrong during upgrade
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 LUKS 1 persistent partition and stopped at Tails Greeter's login screen 7.118
And I enable persistence but something goes wrong during the LUKS header upgrade 2:1.250
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/usb.rb:712:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:730:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:740:in `/^I enable persistence but something goes wrong during the LUKS header upgrade$/'
features/persistence.feature:169:in `And I enable persistence but something goes wrong during the LUKS header upgrade'
Then the Tails persistence partition on USB drive "__internal" still has LUKS version 1 0.000
After features/support/hooks.rb:339 5.013 
SCENARIO FAILED: 'LUKS backup header is restored if something goes wrong during upgrade' (at time 02:45:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6506/artifact/build-artifacts/02:45:38_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6506/artifact/build-artifacts/02:45:38_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6506/artifact/build-artifacts/02:45:38_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6506/artifact/build-artifacts/02:45:38_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.journal
After features/support/hooks.rb:108 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:23.333
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 10.041
And a web server is running on the LAN 1.027
And I capture all network traffic 0.003
When I start the Tor Browser 8.235
And I open a page on the LAN web server in the Tor Browser 4.023
Then the Tor Browser shows the "Unable to connect" error 1:0.000
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/browser.rb:384:in `/^the (Tor|Unsafe) Browser shows the "([^"]+)" error$/'
features/torified_browsing.feature:13:in `Then the Tor Browser shows the "Unable to connect" error'
And no traffic was sent to the web server on the LAN 0.000
After features/support/hooks.rb:339 5.589 
SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 03:27:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6506/artifact/build-artifacts/03:27:28_The_Tor_Browser_cannot_access_the_LAN.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6506/artifact/build-artifacts/03:27:28_The_Tor_Browser_cannot_access_the_LAN.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6506/artifact/build-artifacts/03:27:28_The_Tor_Browser_cannot_access_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6506/artifact/build-artifacts/03:27:28_The_Tor_Browser_cannot_access_the_LAN.journal
After features/support/hooks.rb:108 0.046
Feature: Browsing the web using the Tor Browser
Tags: @product
19.225
Scenario The Tor Browser uses TBB's shared libraries
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 9.695
When I start the Tor Browser 8.706
Then the Tor Browser uses all expected TBB shared libraries 0.823
The 
The loaded shared libraries for the firefox process are not the way we expect them.
Expected TBB libs that are absent: ["libfreeblpriv3.so", "libgkcodecs.so", "liblgpllibs.so", "libmozgtk.so", "libmozsandbox.so", "libmozsqlite3.so", "libmozwayland.so", "libnspr4.so", "libnss3.so", "libnssutil3.so", "libplc4.so", "libplds4.so", "libsmime3.so", "libsoftokn3.so", "libssl3.so", "libxul.so"]
Native libs that we don't want: [].
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/browser.rb:300:in `xul_app_shared_lib_check'
./features/step_definitions/browser.rb:314:in `/^the (.*) uses all expected TBB shared libraries$/'
features/torified_browsing.feature:70:in `Then the Tor Browser uses all expected TBB shared libraries'
After features/support/hooks.rb:339 5.182 
SCENARIO FAILED: 'The Tor Browser uses TBB's shared libraries' (at time 03:31:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6506/artifact/build-artifacts/03:31:19_The_Tor_Browser_uses_TBB_s_shared_libraries.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6506/artifact/build-artifacts/03:31:19_The_Tor_Browser_uses_TBB_s_shared_libraries.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6506/artifact/build-artifacts/03:31:19_The_Tor_Browser_uses_TBB_s_shared_libraries.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6506/artifact/build-artifacts/03:31:19_The_Tor_Browser_uses_TBB_s_shared_libraries.journal
After features/support/hooks.rb:108 0.000