Cucumber Reports (no 5744) - Feature: Additional software

Project	Number	Date
test_Tails_ISO_stable	5744	27 Jun 2025, 10:57

	Steps	Scenarios	Features
Additional software	76	1	2	0	0	79	4	1	5	31:52.060	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

6:39.255

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

Before features/support/hooks.rb:507 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 1:28.799

And I update APT using apt 15.551

And I install "popularity-contest" using apt 33.049

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

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

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

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

And I start Tails from USB drive "__internal" with network unplugged 1:21.552

And I enable persistence 37.948

And I log in to a new session 43.787

And the Additional Software installation service has started 36.951

Then I am notified that the installation succeeded 2.036

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

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

Hooks

After features/support/hooks.rb:515 23.719

After features/support/hooks.rb:330 2.642

After features/support/hooks.rb:100 0.014

Tags: @product @check_tor_leaks @slow

3:14.314

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

Before features/support/hooks.rb:507 0.007

Steps

Given a computer 0.266

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

And I update APT using apt 12.519

When I install "makepp" using apt 30.102

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

And the package "makepp" is installed 0.073

Hooks

After features/support/hooks.rb:515 24.819

After features/support/hooks.rb:330 1.183

After features/support/hooks.rb:100 0.012

Tags: @product @check_tor_leaks @slow

6:38.487

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

Before features/support/hooks.rb:507 0.005

Steps

Given a computer 0.320

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

When I uninstall "popularity-contest" using apt 26.519

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

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

When I start Synaptic 26.251

And I update APT using Synaptic 23.694

And I install "cowsay" using Synaptic 19.871

And I accept adding "cowsay" to Additional Software 5.231

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

When I uninstall "cowsay" using apt 6.418

And I refuse removing "cowsay" from Additional Software 0.638

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

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

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

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

When I install "cowsay" using apt 3.229

And I refuse adding "cowsay" to Additional Software 0.656

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

Hooks

After features/support/hooks.rb:515 0.949

After features/support/hooks.rb:330 0.788

After features/support/hooks.rb:100 0.027

Tags: @product @check_tor_leaks @slow @not_release_blocker

12:3.135

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

Before features/support/hooks.rb:507 0.027

Steps

Given a computer 0.991

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

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

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

And I accept adding "cowsay" to Additional Software 9.077

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

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

And I start Tails from USB drive "__internal" with network unplugged 1:20.150

And I enable persistence 19.785

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

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

And I log in to a new session 53.339

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

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

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

And the network is plugged 0.718

And Tor is ready 25.929

And available upgrades have been checked 0.078

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

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

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

And I start Tails from USB drive "__internal" with network unplugged 1:18.191

And I enable persistence 16.121

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

And I log in to a new session 47.740

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

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

And the network is plugged 0.154

And Tor is ready 12.315

try_for()

try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/additional_software_packages.feature:114:in `And Tor is ready'

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:515 0.098

After features/support/hooks.rb:330 8.110

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:43:20)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5744/artifact/build-artifacts/01:43:20_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_stable/5744/artifact/build-artifacts/01:43:20_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_stable/5744/artifact/build-artifacts/01:43:20_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_stable/5744/artifact/build-artifacts/01:43:20_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_stable/5744/artifact/build-artifacts/01:43:20_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_stable/5744/artifact/build-artifacts/01:43:20_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_stable/5744/artifact/build-artifacts/01:43:20_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_stable/5744/artifact/build-artifacts/01:43:20_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_stable/5744/artifact/build-artifacts/01:43:20_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.025

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

3:16.867

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

Before features/support/hooks.rb:507 0.006

Steps

Given a computer 0.193

And I start Tails from USB drive "__internal" with network unplugged 1:27.296

And I enable persistence 24.663

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

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

And I log in to a new session 52.924

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

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

And the package "cowsay" is not installed 1.824

Hooks

After features/support/hooks.rb:515 0.805

After features/support/hooks.rb:330 2.739

After features/support/hooks.rb:100 0.014

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Additional software	76	1	2	0	0	79	4	1	5	31:52.060	Failed

Feature Report