Cucumber Reports (no 4) - Feature: Additional software

Project	Number	Date
test_Tails_ISO_21079-secure-boot-disabled	4	02 May 2026, 13:23

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

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:266 0.000

Before features/support/hooks.rb:273 0.015

Before features/support/hooks.rb:519 0.003

Steps

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

And I update APT using apt 5.897

And I install "popularity-contest" using apt 6.297

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

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

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

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

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

And I enable persistence 17.034

And I log in to a new session 10.187

And the Additional Software installation service has started 10.184

Then I am notified that the installation succeeded 1.740

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

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

Hooks

After features/support/hooks.rb:527 6.603

After features/support/hooks.rb:331 0.933

After features/support/hooks.rb:100 0.010

Tags: @product @check_tor_leaks @slow

1:26.035

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

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.002

Before features/support/hooks.rb:519 0.002

Steps

Given a computer 0.097

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

And I update APT using apt 4.912

When I install "ripgrep" using apt 6.264

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

And the package "ripgrep" is installed 0.072

Hooks

After features/support/hooks.rb:527 8.397

After features/support/hooks.rb:331 0.886

After features/support/hooks.rb:100 0.012

Tags: @product @check_tor_leaks @slow

3:4.627

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:266 0.000

Before features/support/hooks.rb:273 0.004

Before features/support/hooks.rb:519 0.009

Steps

Given a computer 0.084

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

When I uninstall "popularity-contest" using apt 6.262

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

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

When I start Synaptic 12.566

And I update APT using Synaptic 21.546

And I install "cowsay" using Synaptic 11.334

And I accept adding "cowsay" to Additional Software 2.521

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

When I uninstall "cowsay" using apt 3.193

And I refuse removing "cowsay" from Additional Software 2.419

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

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

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

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

When I install "cowsay" using apt 3.167

And I refuse adding "cowsay" to Additional Software 1.402

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

Hooks

After features/support/hooks.rb:527 0.454

After features/support/hooks.rb:331 0.745

After features/support/hooks.rb:100 0.008

Tags: @product @check_tor_leaks @slow @not_release_blocker

3:15.317

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:266 0.000

Before features/support/hooks.rb:273 0.005

Before features/support/hooks.rb:519 0.004

Steps

Given a computer 0.060

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

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 8.587

And I accept adding "cowsay" to Additional Software 4.952

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

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

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

And I enable persistence 7.443

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

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

And I log in to a new session 10.001

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

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

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

And the network is plugged 0.015

And Tor is ready 13.197

And available upgrades have been checked 2.211

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

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

The

The Dogtail init script raised: SearchError: descendant of [notification | ]: child with name='Configure' roleName='button'
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 started 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:527 0.032

After features/support/hooks.rb:331 5.674

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21079-secure-boot-disabled/4/artifact/build-artifacts/00:54:54_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_21079-secure-boot-disabled/4/artifact/build-artifacts/00:54:54_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_21079-secure-boot-disabled/4/artifact/build-artifacts/00:54:54_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_21079-secure-boot-disabled/4/artifact/build-artifacts/00:54:54_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_21079-secure-boot-disabled/4/artifact/build-artifacts/00:54:54_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_21079-secure-boot-disabled/4/artifact/build-artifacts/00:54:54_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_21079-secure-boot-disabled/4/artifact/build-artifacts/00:54:54_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_21079-secure-boot-disabled/4/artifact/build-artifacts/00:54:54_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_21079-secure-boot-disabled/4/artifact/build-artifacts/00:54:54_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal

After features/support/hooks.rb:100 0.010

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

1:13.506

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

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.002

Before features/support/hooks.rb:519 0.001

Steps

Given a computer 0.066

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

And I enable persistence 8.099

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

And I log in to a new session 11.295

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

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

And the package "cowsay" is not installed 0.407

Hooks

After features/support/hooks.rb:527 0.083

After features/support/hooks.rb:331 0.703

After features/support/hooks.rb:100 0.006

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

Feature Report