Cucumber Reports (no 9) - Failures Overview

Project	Number	Date
test_Tails_ISO_17367-per-setting-dconf-persistence	9	09 Aug 2026, 16:35

Feature: Additional software

2:44.703

Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.001

Before features/support/hooks.rb:527 0.003

Steps

Given a computer 0.072

And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:14.657

And I configure APT to prefer an old version of cowsay 0.005

When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 5.009

And I accept adding "cowsay" to Additional Software 4.047

And Additional Software is correctly configured for package "cowsay" 0.505

And I shutdown Tails and wait for the computer to power off 3.916

And I start Tails from USB drive "__internal" with network unplugged 32.353

And I enable persistence 12.578

# 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.042

And I log in to a new session 7.448

And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been installed 10.162

And I revert the APT tweaks that made it prefer an old version of cowsay 0.031

# 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.034

And the network is plugged 0.033

And Tor is ready 12.099

And available upgrades have been checked 0.042

And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.818

And I can open the Additional Software configuration window from the notification 0.837

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/1656 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

Hooks

After features/support/hooks.rb:535 0.040

After features/support/hooks.rb:339 5.309

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/9/artifact/build-artifacts/01:00:07_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_17367-per-setting-dconf-persistence/9/artifact/build-artifacts/01:00:07_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_17367-per-setting-dconf-persistence/9/artifact/build-artifacts/01:00:07_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_17367-per-setting-dconf-persistence/9/artifact/build-artifacts/01:00:07_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_17367-per-setting-dconf-persistence/9/artifact/build-artifacts/01:00:07_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_17367-per-setting-dconf-persistence/9/artifact/build-artifacts/01:00:07_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_17367-per-setting-dconf-persistence/9/artifact/build-artifacts/01:00:07_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_17367-per-setting-dconf-persistence/9/artifact/build-artifacts/01:00:07_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_17367-per-setting-dconf-persistence/9/artifact/build-artifacts/01:00:07_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.010

Feature: Upgrading an old Tails USB installation

Tags: @product @automatic_upgrade

3:28.067

Scenario Upgrading an initial Tails installation with an incremental upgrade

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.001

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.880

And no SquashFS delta is installed 0.046

And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266

And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046

And the file system changes introduced in version 6.2~testoverlayfs are not present 0.148

And the file system changes introduced in version 6.3~testoverlayfs are not present 0.389

When the network is plugged 0.029

And Tor is ready 12.539

Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.919

And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.647

Given I shutdown Tails and wait for the computer to power off 5.531

When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.611

Then Tails is running version 6.2~testoverlayfs 0.004

And all tps features are active 9.591

And the file system changes introduced in version 6.2~testoverlayfs are present 0.194

And only the 6.2~testoverlayfs SquashFS delta is installed 0.033

# Our IUK sets a release date that can make Tor bootstrapping impossible

Given Tails system time is magically synchronized 0.104

# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk

# but we need some way to force upgrading a second time in a row

# even if only the initially installed version is considered

And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.186

When the network is plugged 0.059

And Tor is ready 10.261

Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.294

And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.380

Given I shutdown Tails and wait for the computer to power off 3.895

When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.003

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/step_definitions/common_steps.rb:238:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:109:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'

Then Tails is running version 6.3~testoverlayfs 0.000

And all tps features are active 0.000

And the file system changes introduced in version 6.3~testoverlayfs are present 0.000

And only the 6.3~testoverlayfs SquashFS delta is installed 0.000

# Regression test for #17425 (i.e. the Upgrader would propose

# upgrading to the version that's already running)

Given Tails system time is magically synchronized 0.000

And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000

When the network is plugged 0.000

And Tor is ready 0.000

Then the Upgrader considers the system as up-to-date 0.000

# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)

And I successfully start the Unsafe Browser 0.000

And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000

Hooks

After features/support/hooks.rb:339 4.991

Output 1

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:12:04)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/9/artifact/build-artifacts/01:12:04_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/9/artifact/build-artifacts/01:12:04_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/9/artifact/build-artifacts/01:12:04_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_17367-per-setting-dconf-persistence/9/artifact/build-artifacts/01:12:04_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:108 0.010