Cucumber Reports (no 1) - Feature: Additional software

Project	Number	Date
test_Tails_ISO_21565-flatpak-safe	1	18 Aug 2026, 20:00

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

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

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 48.358

And I update the APT lists using apt 6.569

And I install "popularity-contest" using apt 3.175

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

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

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

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

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

And I enable persistence 21.398

And I log in to a new session 8.430

And the Additional Software installation service has started 10.190

Then I am notified that the installation succeeded 1.912

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

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

Hooks

After features/support/hooks.rb:535 0.879

After features/support/hooks.rb:339 0.580

After features/support/hooks.rb:108 0.008

Tags: @product @check_tor_leaks @slow

1:19.304

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

Steps

Given a computer 0.086

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

And I update the APT lists using apt 4.450

When I install "ripgrep" using apt 3.160

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

And the package "ripgrep" is installed 0.045

Hooks

After features/support/hooks.rb:535 0.730

After features/support/hooks.rb:339 0.683

After features/support/hooks.rb:108 0.009

Tags: @product @check_tor_leaks @slow

2:57.734

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

Steps

Given a computer 0.099

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

When I uninstall "popularity-contest" using apt 3.164

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

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

When I start Synaptic 11.649

And I update the APT lists using Synaptic 20.959

And I install "cowsay" using Synaptic 8.193

And I accept adding "cowsay" to Additional Software 2.521

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

When I uninstall "cowsay" using apt 3.177

And I refuse removing "cowsay" from Additional Software 2.314

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

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

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

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

When I install "cowsay" using apt 3.233

And I refuse adding "cowsay" to Additional Software 1.622

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

Hooks

After features/support/hooks.rb:535 0.250

After features/support/hooks.rb:339 0.878

After features/support/hooks.rb:108 0.041

Tags: @product @check_tor_leaks @slow @not_release_blocker

3:16.183

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

Before features/support/hooks.rb:527 0.004

Steps

Given a computer 0.113

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

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

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

And I accept adding "cowsay" to Additional Software 4.738

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

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

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

And I enable persistence 11.240

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

And I log in to a new session 7.903

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

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

And the network is plugged 0.036

And Tor is ready 12.946

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

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

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

After features/support/hooks.rb:339 5.301

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:30)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21565-flatpak-safe/1/artifact/build-artifacts/01:01:30_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/1/artifact/build-artifacts/01:01:30_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/1/artifact/build-artifacts/01:01:30_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/1/artifact/build-artifacts/01:01:30_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/1/artifact/build-artifacts/01:01:30_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/1/artifact/build-artifacts/01:01:30_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/1/artifact/build-artifacts/01:01:30_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/1/artifact/build-artifacts/01:01:30_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/1/artifact/build-artifacts/01:01:30_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.020

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

1:7.710

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

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

And I enable persistence 12.310

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

And I log in to a new session 7.623

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

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

And the package "cowsay" is not installed 0.223

Hooks

After features/support/hooks.rb:535 0.223

After features/support/hooks.rb:339 0.735

After features/support/hooks.rb:108 0.020

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

Feature Report