Project Number Date
test_Tails_ISO_stable 6748 14 Oct 2026, 11:37

Failures Overview

The following summary displays scenarios that failed.

3:9.533
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
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.076
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:11.637
And I configure APT to prefer an old version of cowsay 0.004
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 6.478
And I accept adding "cowsay" to Additional Software 3.989
And Additional Software is correctly configured for package "cowsay" 0.490
And I shutdown Tails and wait for the computer to power off 3.971
And I start Tails from USB drive "__internal" with network unplugged 32.404
And I enable persistence 10.721
# 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.036
And I log in to a new session 6.839
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been installed 10.183
And I revert the APT tweaks that made it prefer an old version of cowsay 0.039
# 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.040
And the network is plugged 0.033
And Tor is ready 16.117
And available upgrades have been checked 0.028
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.203
And I can open the Additional Software configuration window from the notification 26.232
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
After features/support/hooks.rb:535 0.039
After features/support/hooks.rb:339 5.252

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

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6748/artifact/build-artifacts/01:06:23_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.net/job/test_Tails_ISO_stable/6748/artifact/build-artifacts/01:06:23_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.net/job/test_Tails_ISO_stable/6748/artifact/build-artifacts/01:06:23_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.net/job/test_Tails_ISO_stable/6748/artifact/build-artifacts/01:06:23_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.net/job/test_Tails_ISO_stable/6748/artifact/build-artifacts/01:06:23_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.net/job/test_Tails_ISO_stable/6748/artifact/build-artifacts/01:06:23_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.net/job/test_Tails_ISO_stable/6748/artifact/build-artifacts/01:06:23_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6748/artifact/build-artifacts/01:06:23_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6748/artifact/build-artifacts/01:06:23_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.028
2.448
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.448
Command failed (pid 89340 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@d535f574ed-20261014T0716Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@d535f574ed-20261014T0716Z.build-manifest
INFO: Last successful auto-update of the UDD mirror: 2026-10-14 08:31:16+00:00 (1:27:12.540750 ago)
INFO: Need to upgrade to a new APT snapshot:
  - curl (8.14.1-2+deb13u5) to Debian trixie-security (8.14.1-2+deb13u7)
 (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