Cucumber Reports (no 120) - Feature: Additional software

Project	Number	Date
test_Tails_ISO_21565-flatpak-safe	120	03 Nov 2026, 21:14

	Steps	Scenarios	Features
Additional software	66	1	11	0	0	78	4	1	5	11:56.953	Failed

Feature Additional software

As a Tails user I may want to install software not shipped in Tails And have them installed automatically when I enable persistence in the Greeter

Tags: @product @check_tor_leaks @slow

2:58.339

Scenario I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.002

Before features/support/hooks.rb:527 0.002

Steps

Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 45.175

And I update the APT lists using apt 35.078

And I install "popularity-contest" using apt 3.453

Then I am proposed to add the "popularity-contest" package to my Additional Software 3.167

When I create a persistent storage and activate the Additional Software feature 14.847

Then Additional Software is correctly configured for package "popularity-contest" 0.609

When I shutdown Tails and wait for the computer to power off 4.025

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

And I enable persistence 18.414

And I log in to a new session 8.176

And the Additional Software installation service has started 10.164

Then I am notified that the installation succeeded 1.594

And Additional Software is correctly configured for package "popularity-contest" 0.668

And the package "popularity-contest" is installed after Additional Software has been installed 0.111

Hooks

After features/support/hooks.rb:535 0.704

After features/support/hooks.rb:339 0.628

After features/support/hooks.rb:108 0.008

Tags: @product @check_tor_leaks @slow

1:45.708

Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.001

Before features/support/hooks.rb:527 0.004

Steps

Given a computer 0.075

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

And I update the APT lists using apt 34.527

When I install "ripgrep" using apt 3.374

Then the Additional Software dpkg hook has been run for package "ripgrep" and notices the persistence is locked 2.141

And the package "ripgrep" is installed 0.057

Hooks

After features/support/hooks.rb:535 0.749

After features/support/hooks.rb:339 0.714

After features/support/hooks.rb:108 0.009

Tags: @product @check_tor_leaks @slow

2:50.377

Scenario My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic

Hooks

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.074

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

When I uninstall "popularity-contest" using apt 3.141

And I accept removing "popularity-contest" from Additional Software 2.525

Then "popularity-contest" is not in the list of Additional Software 0.468

When I start Synaptic 11.500

And I update the APT lists using Synaptic 21.209

And I install "cowsay" using Synaptic 7.745

And I accept adding "cowsay" to Additional Software 2.310

Then Additional Software is correctly configured for package "cowsay" 0.608

When I uninstall "cowsay" using apt 3.134

And I refuse removing "cowsay" from Additional Software 2.509

Then Additional Software is correctly configured for package "cowsay" 0.529

When I start "Additional Software" via GNOME Activities Overview 9.199

And I remove "cowsay" from the list of Additional Software using Additional Software GUI 3.355

Then "cowsay" is not in the list of Additional Software 0.713

When I install "cowsay" using apt 3.180

And I refuse adding "cowsay" to Additional Software 1.374

Then "cowsay" is not in the list of Additional Software 0.463

Hooks

After features/support/hooks.rb:535 0.283

After features/support/hooks.rb:339 0.619

After features/support/hooks.rb:108 0.005

Tags: @product @check_tor_leaks @slow @not_release_blocker

3:15.256

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.001

Steps

Given a computer 0.111

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

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.030

And I accept adding "cowsay" to Additional Software 4.878

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

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

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

And I enable persistence 10.834

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

And I log in to a new session 8.264

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

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

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

And the network is plugged 0.024

And Tor is ready 12.838

And available upgrades have been checked 0.034

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

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

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

Hooks

After features/support/hooks.rb:535 0.037

After features/support/hooks.rb:339 5.124

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:08:09)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/120/artifact/build-artifacts/01:08: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.net/job/test_Tails_ISO_21565-flatpak-safe/120/artifact/build-artifacts/01:08: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.net/job/test_Tails_ISO_21565-flatpak-safe/120/artifact/build-artifacts/01:08: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.net/job/test_Tails_ISO_21565-flatpak-safe/120/artifact/build-artifacts/01:08: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.net/job/test_Tails_ISO_21565-flatpak-safe/120/artifact/build-artifacts/01:08: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.net/job/test_Tails_ISO_21565-flatpak-safe/120/artifact/build-artifacts/01:08: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.net/job/test_Tails_ISO_21565-flatpak-safe/120/artifact/build-artifacts/01:08:09_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_21565-flatpak-safe/120/artifact/build-artifacts/01:08: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.net/job/test_Tails_ISO_21565-flatpak-safe/120/artifact/build-artifacts/01:08: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.040

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

1:7.270

Scenario I am notified when Additional Software fails to install a package

Hooks

Before features/support/hooks.rb:274 0.000

Before features/support/hooks.rb:281 0.002

Before features/support/hooks.rb:527 0.002

Steps

Given a computer 0.086

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

And I enable persistence 11.822

And I remove the "cowsay" deb files from the APT cache 0.039

And I log in to a new session 6.477

Then I see the "The installation of your additional software failed" notification after at most 300 seconds 8.054

And I can open the Additional Software log file from the notification 6.027

And the package "cowsay" is not installed 0.319

Hooks

After features/support/hooks.rb:535 0.292

After features/support/hooks.rb:339 0.691

After features/support/hooks.rb:108 0.010

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Additional software	66	1	11	0	0	78	4	1	5	11:56.953	Failed

Feature Report