Cucumber Reports (no 5554) - Feature: Additional software

Project	Number	Date
test_Tails_ISO_stable	5554	04 Apr 2025, 13:16

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

6:20.374

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:511 0.004

Steps

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

And I update APT using apt 1:12.648

And I install "popularity-contest" using apt 23.278

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

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

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

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

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

And I enable persistence 22.936

And I log in to a new session 42.309

And the Additional Software installation service has started 41.568

Then I am notified that the installation succeeded 2.008

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

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

Hooks

After features/support/hooks.rb:519 15.457

After features/support/hooks.rb:330 1.332

After features/support/hooks.rb:100 0.013

Tags: @product @check_tor_leaks @slow

7:28.903

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:511 0.004

Steps

Given a computer 0.218

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

And I update APT using apt 5:13.266

When I install "makepp" using apt 23.076

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

And the package "makepp" is installed 0.084

Hooks

After features/support/hooks.rb:519 17.070

After features/support/hooks.rb:330 1.690

After features/support/hooks.rb:100 0.012

Tags: @product @check_tor_leaks @slow

5:10.550

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:511 0.004

Steps

Given a computer 0.218

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

When I uninstall "popularity-contest" using apt 21.810

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

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

When I start Synaptic 22.628

And I update APT using Synaptic 22.549

And I install "cowsay" using Synaptic 13.190

And I accept adding "cowsay" to Additional Software 1.511

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

When I uninstall "cowsay" using apt 3.294

And I refuse removing "cowsay" from Additional Software 0.589

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

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

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

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

When I install "cowsay" using apt 3.244

And I refuse adding "cowsay" to Additional Software 0.740

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

Hooks

After features/support/hooks.rb:519 0.788

After features/support/hooks.rb:330 0.757

After features/support/hooks.rb:100 0.010

Tags: @product @check_tor_leaks @slow @not_release_blocker

13:48.867

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:511 0.007

Steps

Given a computer 0.206

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

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

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

And I accept adding "cowsay" to Additional Software 4.472

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

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

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

And I enable persistence 12.914

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

# 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 43.867

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

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

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

And the network is plugged 0.073

And Tor is ready 20.286

And available upgrades have been checked 0.065

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

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

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

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

And I enable persistence 13.508

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

And I log in to a new session 41.153

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

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

And the network is plugged 0.079

And Tor is ready 1:2.028

TCA

TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
./features/step_definitions/common_steps.rb:652: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:519 0.037

After features/support/hooks.rb:330 14.509

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:32:49)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5554/artifact/build-artifacts/01:32:49_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online_chutney-data

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5554/artifact/build-artifacts/01:32:49_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/5554/artifact/build-artifacts/01:32:49_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/5554/artifact/build-artifacts/01:32:49_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.026

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

2:18.928

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:511 0.004

Steps

Given a computer 0.588

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

And I enable persistence 12.890

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

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

And I log in to a new session 38.767

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

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

And the package "cowsay" is not installed 0.638

Hooks

After features/support/hooks.rb:519 0.147

After features/support/hooks.rb:330 1.791

After features/support/hooks.rb:100 0.022

	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	35:7.624	Failed

Feature Report