Project Number Date
test_Tails_ISO_stable 6507 15 Jul 2026, 11:36

Failures Overview

The following summary displays scenarios that failed.

Feature: Backing up the persistent storage
Tags: @product
1:37.293
Scenario Using Tails' custom backup tool to backup a newly added file
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.721
# The volume cannot be in use when GuestFs clones it, which we do below
And I shutdown Tails and wait for the computer to power off 9.333
And I clone USB drive "__internal" to a temporary USB drive "backup" 0.658
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.231
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.006
When I start Tails' custom backup tool 1.901
Then the backup tool displays "Plug in your backup Tails USB stick" 0.333
When I plug USB drive "backup" 2.278
And I give the Persistent Storage on drive "backup" its own UUID 0.070
And I click "Retry" in the backup tool 3.144
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.121
When I click "Back Up" in the backup tool 3.101
And I enter my persistent storage passphrase into the polkit prompt 1.389
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 1:0.000
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'zenity' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/backup.rb:7:in `new'
./features/step_definitions/backup.rb:7: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/backup.rb:6: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/backup.rb:6:in `/^the backup tool displays "([^"]+)"$/'
features/backup.feature:22:in `Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!"'
# The backup tool ejects the drive, so we have to replug it
When I unplug USB drive "backup" 0.000
And I plug USB drive "backup" 0.000
Then the USB drive "backup" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:339 8.266 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 01:24:38)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6507/artifact/build-artifacts/01:24:38_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6507/artifact/build-artifacts/01:24:38_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6507/artifact/build-artifacts/01:24:38_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:108 0.120
Feature: Packages are up-to-date
Tags: @source @fragile
0.957
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.957
Command 
Command failed (pid 111700 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-20260715T0716Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@b5a5a57f8b-20260715T0716Z.build-manifest
INFO: Last successful auto-update of the UDD mirror: 2026-07-15 08:32:37+00:00 (1:32:06.721990 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[libcurl4t64, libcurl3t64-gnutls] (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[gpgsm, gpg, gpg-agent, dirmngr, gpgconf] (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[libegl-mesa0, libgbm1] (25.0.7-2) to Debian trixie (25.0.7-2+deb13u1)
  - mesa[libgl1-mesa-dri, libglx-mesa0] (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-stdlib, libpython3.13, libpython3.13-minimal] (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: Browsing the web using the Tor Browser
Tags: @product
18.142
Scenario The Tor Browser uses TBB's shared libraries
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.671
When I start the Tor Browser 7.679
Then the Tor Browser uses all expected TBB shared libraries 0.791
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 4.739 
SCENARIO FAILED: 'The Tor Browser uses TBB's shared libraries' (at time 03:25:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6507/artifact/build-artifacts/03:25:43_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/6507/artifact/build-artifacts/03:25:43_The_Tor_Browser_uses_TBB_s_shared_libraries.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6507/artifact/build-artifacts/03:25:43_The_Tor_Browser_uses_TBB_s_shared_libraries.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6507/artifact/build-artifacts/03:25:43_The_Tor_Browser_uses_TBB_s_shared_libraries.journal
After features/support/hooks.rb:108 0.000