Project Number Date
test_Tails_ISO_21565-flatpak-safe 21 31 Aug 2026, 16:31

Failures Overview

The following summary displays scenarios that failed.

2:47.581
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.078
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:15.007
And I configure APT to prefer an old version of cowsay 0.006
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 5.211
And I accept adding "cowsay" to Additional Software 5.088
And Additional Software is correctly configured for package "cowsay" 0.537
And I shutdown Tails and wait for the computer to power off 4.142
And I start Tails from USB drive "__internal" with network unplugged 33.450
And I enable persistence 11.228
# 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.014
# 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.045
And I log in to a new session 7.905
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been installed 10.159
And I revert the APT tweaks that made it prefer an old version of cowsay 0.037
# 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.048
And the network is plugged 0.041
And Tor is ready 12.835
And available upgrades have been checked 0.040
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.955
And I can open the Additional Software configuration window from the notification 0.744
The
The Dogtail init script raised: Error: atspi_error: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" could not be processed as object /org/a11y/atspi/accessible/475 does not exist
 (1)
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:34: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.034
After features/support/hooks.rb:339 5.272

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21565-flatpak-safe/21/artifact/build-artifacts/01:00:09_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_21565-flatpak-safe/21/artifact/build-artifacts/01:00:09_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_21565-flatpak-safe/21/artifact/build-artifacts/01:00:09_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_21565-flatpak-safe/21/artifact/build-artifacts/01:00:09_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_21565-flatpak-safe/21/artifact/build-artifacts/01:00:09_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_21565-flatpak-safe/21/artifact/build-artifacts/01:00:09_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_21565-flatpak-safe/21/artifact/build-artifacts/01:00:09_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_21565-flatpak-safe/21/artifact/build-artifacts/01:00:09_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_21565-flatpak-safe/21/artifact/build-artifacts/01:00:09_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.009
5:33.419
Scenario Configuring WebTunnel with QR code
Steps
When I configure some webtunnel bridges from a QR code in the Tor Connection Assistant in hide mode 31.745
Then I wait until Tor is ready 1.673
And available upgrades have been checked 5:0.000
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/common_steps.rb:764:in `/^available upgrades have been checked$/'
features/webtunnel.feature:23:in `And available upgrades have been checked'
After features/support/hooks.rb:535 0.048
After features/support/hooks.rb:339 4.913

SCENARIO FAILED: 'Configuring WebTunnel with QR code' (at time 03:36:22)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21565-flatpak-safe/21/artifact/build-artifacts/03:36:22_Configuring_WebTunnel_with_QR_code.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21565-flatpak-safe/21/artifact/build-artifacts/03:36:22_Configuring_WebTunnel_with_QR_code.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21565-flatpak-safe/21/artifact/build-artifacts/03:36:22_Configuring_WebTunnel_with_QR_code.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21565-flatpak-safe/21/artifact/build-artifacts/03:36:22_Configuring_WebTunnel_with_QR_code.journal

After features/support/hooks.rb:108 0.035