Cucumber Reports (no 3891) - Feature: Additional software

Project	Number	Date
test_Tails_ISO_devel	3891	29 Jun 2025, 13:55

	Steps	Scenarios	Features
Additional software	64	2	18	0	0	84	4	2	6	32:31.839	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 @not_release_blocker @fragile @doc

3:53.673

Scenario I am warned I can not use Additional Software when I start Tails from a DVD and install a package

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.021

Before features/support/hooks.rb:507 0.011

Steps

Given I have started Tails from DVD and logged in with an administration password and the network is connected 2:8.778

And I update APT using apt 20.230

When I install "popularity-contest" using apt 35.190

Then I am notified I can not use Additional Software for "popularity-contest" 7.023

And I can open the Additional Software documentation from the notification 42.450

Hooks

After features/support/hooks.rb:515 27.332

After features/support/hooks.rb:330 3.688

After features/support/hooks.rb:100 0.007

Tags: @product @check_tor_leaks @slow

6:57.516

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

Before features/support/hooks.rb:507 0.009

Steps

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

And I update APT using apt 16.741

And I install "popularity-contest" using apt 26.388

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

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

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

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

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

And I enable persistence 36.486

And I log in to a new session 1:5.253

And the Additional Software installation service has started 32.251

Then I am notified that the installation succeeded 3.453

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

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

Hooks

After features/support/hooks.rb:515 32.871

After features/support/hooks.rb:330 4.890

After features/support/hooks.rb:100 0.049

Tags: @product @check_tor_leaks @slow

4:34.403

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

Before features/support/hooks.rb:507 0.016

Steps

Given a computer 0.361

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

cannot

cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:566:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:522:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
./features/step_definitions/common_steps.rb:295:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/additional_software_packages.feature:46:in `And I start Tails from USB drive "__internal" and I login with an administration password'

And I update APT using apt 0.000

When I install "makepp" using apt 0.000

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

And the package "makepp" is installed 0.000

Hooks

After features/support/hooks.rb:515 0.048

After features/support/hooks.rb:330 5.859

Output 1

SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:46:50)

Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3891/artifact/build-artifacts/01:46:50_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_var_log_boot.log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3891/artifact/build-artifacts/01:46:50_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3891/artifact/build-artifacts/01:46:50_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3891/artifact/build-artifacts/01:46:50_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3891/artifact/build-artifacts/01:46:50_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3891/artifact/build-artifacts/01:46:50_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3891/artifact/build-artifacts/01:46:50_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3891/artifact/build-artifacts/01:46:50_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal

After features/support/hooks.rb:100 0.020

Tags: @product @check_tor_leaks @slow

6:43.766

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

Before features/support/hooks.rb:507 0.012

Steps

Given a computer 0.287

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

When I uninstall "popularity-contest" using apt 25.667

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

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

When I start Synaptic 30.791

And I update APT using Synaptic 23.663

And I install "cowsay" using Synaptic 16.836

And I accept adding "cowsay" to Additional Software 0.778

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

When I uninstall "cowsay" using apt 3.355

And I refuse removing "cowsay" from Additional Software 1.033

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

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

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

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

When I install "cowsay" using apt 3.318

And I refuse adding "cowsay" to Additional Software 0.573

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

Hooks

After features/support/hooks.rb:515 0.914

After features/support/hooks.rb:330 0.698

After features/support/hooks.rb:100 0.014

Tags: @product @check_tor_leaks @slow @not_release_blocker

7:27.490

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

Before features/support/hooks.rb:507 0.007

Steps

Given a computer 0.308

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

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

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

And I accept adding "cowsay" to Additional Software 9.108

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

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

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

And I enable persistence 20.978

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

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

And I log in to a new session 41.532

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

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

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

And the network is plugged 0.096

And Tor is ready 12.622

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:100:in `And Tor is ready'

And available upgrades have been checked 0.000

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

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

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

After features/support/hooks.rb:330 5.410

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3891/artifact/build-artifacts/02:01:10_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_devel/3891/artifact/build-artifacts/02:01:10_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_devel/3891/artifact/build-artifacts/02:01:10_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_devel/3891/artifact/build-artifacts/02:01:10_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_devel/3891/artifact/build-artifacts/02:01:10_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_devel/3891/artifact/build-artifacts/02:01:10_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_devel/3891/artifact/build-artifacts/02:01:10_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_devel/3891/artifact/build-artifacts/02:01:10_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_devel/3891/artifact/build-artifacts/02:01:10_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.071

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

2:54.989

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

Before features/support/hooks.rb:507 0.010

Steps

Given a computer 0.304

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

And I enable persistence 14.533

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

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

And I log in to a new session 49.886

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

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

And the package "cowsay" is not installed 1.819

Hooks

After features/support/hooks.rb:515 1.547

After features/support/hooks.rb:330 2.977

After features/support/hooks.rb:100 0.013

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Additional software	64	2	18	0	0	84	4	2	6	32:31.839	Failed

Feature Report