Cucumber Reports (no 2) - Feature: Additional software

Project	Number	Date
test_Tails_ISO_codespell	2	18 Jun 2025, 02:48

	Steps	Scenarios	Features
Additional software	76	1	2	0	0	79	4	1	5	34:49.335	Failed

Feature Additional software

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

Tags: @product @check_tor_leaks @slow

7:16.521

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

Before features/support/hooks.rb:507 0.041

Steps

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

And I update APT using apt 19.219

And I install "popularity-contest" using apt 32.848

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

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

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

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

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

And I enable persistence 37.183

And I log in to a new session 1:2.558

And the Additional Software installation service has started 44.302

Then I am notified that the installation succeeded 4.550

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

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

Hooks

After features/support/hooks.rb:515 28.025

After features/support/hooks.rb:330 3.017

After features/support/hooks.rb:100 0.041

Tags: @product @check_tor_leaks @slow

3:40.888

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

Before features/support/hooks.rb:507 0.126

Steps

Given a computer 0.314

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

And I update APT using apt 18.646

When I install "makepp" using apt 35.516

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

And the package "makepp" is installed 0.098

Hooks

After features/support/hooks.rb:515 30.780

After features/support/hooks.rb:330 1.742

After features/support/hooks.rb:100 0.064

Tags: @product @check_tor_leaks @slow

6:25.946

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

Before features/support/hooks.rb:507 0.014

Steps

Given a computer 0.234

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

When I uninstall "popularity-contest" using apt 20.845

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

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

When I start Synaptic 28.298

And I update APT using Synaptic 23.346

And I install "cowsay" using Synaptic 17.756

And I accept adding "cowsay" to Additional Software 1.452

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

When I uninstall "cowsay" using apt 3.574

And I refuse removing "cowsay" from Additional Software 2.746

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

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

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

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

When I install "cowsay" using apt 3.285

And I refuse adding "cowsay" to Additional Software 0.687

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

Hooks

After features/support/hooks.rb:515 0.923

After features/support/hooks.rb:330 0.842

After features/support/hooks.rb:100 0.010

Tags: @product @check_tor_leaks @slow @not_release_blocker

14:25.371

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

Before features/support/hooks.rb:507 0.005

Steps

Given a computer 0.202

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

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

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

And I accept adding "cowsay" to Additional Software 10.109

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

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

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

And I enable persistence 20.471

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

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

And I log in to a new session 57.256

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

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

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

And the network is plugged 0.126

And Tor is ready 34.737

And available upgrades have been checked 0.307

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

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

And I shutdown Tails and wait for the computer to power off 2:3.028

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

And I enable persistence 19.283

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

And I log in to a new session 50.733

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

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

And the network is plugged 0.074

And Tor is ready 14.153

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

After features/support/hooks.rb:330 6.616

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_codespell/2/artifact/build-artifacts/02:11:39_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_codespell/2/artifact/build-artifacts/02:11:39_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_codespell/2/artifact/build-artifacts/02:11:39_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_codespell/2/artifact/build-artifacts/02:11:39_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_codespell/2/artifact/build-artifacts/02:11:39_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_codespell/2/artifact/build-artifacts/02:11:39_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_codespell/2/artifact/build-artifacts/02:11:39_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_codespell/2/artifact/build-artifacts/02:11:39_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_codespell/2/artifact/build-artifacts/02:11:39_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.033

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

3:0.607

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

Before features/support/hooks.rb:507 0.007

Steps

Given a computer 0.197

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

And I enable persistence 18.003

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

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

And I log in to a new session 1:0.351

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

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

And the package "cowsay" is not installed 0.661

Hooks

After features/support/hooks.rb:515 0.155

After features/support/hooks.rb:330 1.480

After features/support/hooks.rb:100 0.051

	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	34:49.335	Failed

Feature Report