Cucumber Reports (no 2) - Feature: Additional software

Project	Number	Date
test_Tails_ISO_21641-update-moat-frontends	2	13 Aug 2026, 16:05

	Steps	Scenarios	Features
Additional software	66	1	11	0	0	78	4	1	5	11:8.598	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:36.333

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

Before features/support/hooks.rb:527 0.006

Steps

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

And I update the APT lists using apt 6.205

And I install "popularity-contest" using apt 3.182

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

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

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

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

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

And I enable persistence 20.089

And I log in to a new session 7.554

And the Additional Software installation service has started 10.137

Then I am notified that the installation succeeded 1.447

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

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

Hooks

After features/support/hooks.rb:535 0.732

After features/support/hooks.rb:339 0.688

After features/support/hooks.rb:108 0.012

Tags: @product @check_tor_leaks @slow

1:17.265

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

Steps

Given a computer 0.097

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

And I update the APT lists using apt 4.445

When I install "ripgrep" using apt 3.156

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

And the package "ripgrep" is installed 0.048

Hooks

After features/support/hooks.rb:535 0.670

After features/support/hooks.rb:339 0.713

After features/support/hooks.rb:108 0.013

Tags: @product @check_tor_leaks @slow

2:52.811

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

Before features/support/hooks.rb:527 0.002

Steps

Given a computer 0.112

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

When I uninstall "popularity-contest" using apt 3.130

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

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

When I start Synaptic 11.936

And I update the APT lists using Synaptic 21.356

And I install "cowsay" using Synaptic 7.835

And I accept adding "cowsay" to Additional Software 2.331

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

When I uninstall "cowsay" using apt 3.163

And I refuse removing "cowsay" from Additional Software 2.286

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

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

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

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

When I install "cowsay" using apt 3.169

And I refuse adding "cowsay" to Additional Software 1.498

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

Hooks

After features/support/hooks.rb:535 0.236

After features/support/hooks.rb:339 0.769

After features/support/hooks.rb:108 0.006

Tags: @product @check_tor_leaks @slow @not_release_blocker

3:15.339

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

Before features/support/hooks.rb:527 0.005

Steps

Given a computer 0.071

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

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

And I accept adding "cowsay" to Additional Software 4.749

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

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

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

And I enable persistence 11.482

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

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

And I log in to a new session 9.082

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

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

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

And the network is plugged 0.036

And Tor is ready 12.547

And available upgrades have been checked 0.045

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

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

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

After features/support/hooks.rb:339 5.565

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:01:58)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21641-update-moat-frontends/2/artifact/build-artifacts/01:01:58_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_21641-update-moat-frontends/2/artifact/build-artifacts/01:01:58_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_21641-update-moat-frontends/2/artifact/build-artifacts/01:01:58_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_21641-update-moat-frontends/2/artifact/build-artifacts/01:01:58_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_21641-update-moat-frontends/2/artifact/build-artifacts/01:01:58_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_21641-update-moat-frontends/2/artifact/build-artifacts/01:01:58_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_21641-update-moat-frontends/2/artifact/build-artifacts/01:01:58_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_21641-update-moat-frontends/2/artifact/build-artifacts/01:01:58_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_21641-update-moat-frontends/2/artifact/build-artifacts/01:01:58_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.019

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

1:6.847

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

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

And I enable persistence 11.591

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

And I log in to a new session 8.199

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

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

And the package "cowsay" is not installed 0.245

Hooks

After features/support/hooks.rb:535 0.311

After features/support/hooks.rb:339 0.596

After features/support/hooks.rb:108 0.008

	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:8.598	Failed

Feature Report