Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 69 12 Aug 2026, 08:02

Failures Overview

The following summary displays scenarios that failed.

Feature: Installing and running Flatpak apps in Tails
Tags: @product @check_tor_leaks
2:46.705
Scenario Installing, starting and uninstalling a Flatpak
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 I have started Tails with the Flatpak feature from a USB drive with a persistent partition enabled and logged in and the network is connected 2:30.458
When I start GNOME Software 1.740
And I install Signal Desktop using GNOME Software 14.506
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-software]: child with name='Signal Desktop' roleName='label'
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/flatpak.rb:25:in `/^I install (.*) using GNOME Software$/'
features/flatpak.feature:27:in `And I install Signal Desktop using GNOME Software'
Then the org.signal.Signal Flatpak is installed after at most 600 seconds 0.000
When I start the org.signal.Signal Flatpak 0.000
Then the org.signal.Signal Flatpak is running 0.000
Given I kill the org.signal.Signal Flatpak 0.000
And I go to the main screen of GNOME Software 0.000
When I uninstall Signal Desktop using GNOME Software 0.000
Then the org.signal.Signal Flatpak is uninstalled after at most 60 seconds 0.000
After features/support/hooks.rb:535 0.035
After features/support/hooks.rb:339 4.922 
SCENARIO FAILED: 'Installing, starting and uninstalling a Flatpak' (at time 00:10:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21318-tor-browser-16.0/69/artifact/build-artifacts/00:10:26_Installing,_starting_and_uninstalling_a_Flatpak.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21318-tor-browser-16.0/69/artifact/build-artifacts/00:10:26_Installing,_starting_and_uninstalling_a_Flatpak.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21318-tor-browser-16.0/69/artifact/build-artifacts/00:10:26_Installing,_starting_and_uninstalling_a_Flatpak.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21318-tor-browser-16.0/69/artifact/build-artifacts/00:10:26_Installing,_starting_and_uninstalling_a_Flatpak.journal
After features/support/hooks.rb:108 0.003
Feature: Time syncing
Tags: @product @check_tor_leaks @not_release_blocker
1:39.612
Scenario The system time is not synced to the hardware clock
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 I have started Tails from DVD without network and logged in 6.357
When I bump the system time with "-15 days" 0.196
And I warm reboot the computer 0.009
And the computer reboots Tails 1:33.049
can 
can not find any of the patterns ["TailsGreeter.png", "PlymouthGraphicsCardFailureMessage.png"] on the screen (FindFailed)
./features/support/helpers/screen.rb:248:in `rescue in wait_any'
./features/support/helpers/screen.rb:232:in `wait_any'
./features/step_definitions/common_steps.rb:446:in `/^the computer (?:re)?boots Tails$/'
features/time_syncing.feature:37:in `And the computer reboots Tails'
Then Tails' hardware clock is close to the host system's time 0.000
After features/support/hooks.rb:535 0.039
After features/support/hooks.rb:339 4.877 
SCENARIO FAILED: 'The system time is not synced to the hardware clock' (at time 00:16:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21318-tor-browser-16.0/69/artifact/build-artifacts/00:16:03_The_system_time_is_not_synced_to_the_hardware_clock.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21318-tor-browser-16.0/69/artifact/build-artifacts/00:16:03_The_system_time_is_not_synced_to_the_hardware_clock.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21318-tor-browser-16.0/69/artifact/build-artifacts/00:16:03_The_system_time_is_not_synced_to_the_hardware_clock.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21318-tor-browser-16.0/69/artifact/build-artifacts/00:16:03_The_system_time_is_not_synced_to_the_hardware_clock.journal
After features/support/hooks.rb:108 0.010
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
3:14.261
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.083
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:15.856
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 5.836
And I accept adding "cowsay" to Additional Software 5.132
And Additional Software is correctly configured for package "cowsay" 0.566
And I shutdown Tails and wait for the computer to power off 4.059
And I start Tails from USB drive "__internal" with network unplugged 33.769
And I enable persistence 11.378
# 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.005
# 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.274
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been installed 10.163
And I revert the APT tweaks that made it prefer an old version of cowsay 0.067
# 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.066
And the network is plugged 0.025
And Tor is ready 11.327
And available upgrades have been checked 1.090
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.495
And I can open the Additional Software configuration window from the notification 27.016
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.036
After features/support/hooks.rb:339 5.087 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:03:04)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21318-tor-browser-16.0/69/artifact/build-artifacts/01:03:04_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_21318-tor-browser-16.0/69/artifact/build-artifacts/01:03:04_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_21318-tor-browser-16.0/69/artifact/build-artifacts/01:03:04_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_21318-tor-browser-16.0/69/artifact/build-artifacts/01:03:04_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_21318-tor-browser-16.0/69/artifact/build-artifacts/01:03:04_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_21318-tor-browser-16.0/69/artifact/build-artifacts/01:03:04_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_21318-tor-browser-16.0/69/artifact/build-artifacts/01:03:04_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_21318-tor-browser-16.0/69/artifact/build-artifacts/01:03:04_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_21318-tor-browser-16.0/69/artifact/build-artifacts/01:03:04_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.017