Cucumber Reports (no 5408) - Feature: Additional software

Project	Number	Date
test_Tails_ISO_stable	5408	21 Jan 2025, 18:12

	Steps	Scenarios	Features
Additional software	64	1	14	0	0	79	4	1	5	23:24.810	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

5:8.239

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

Before features/support/hooks.rb:507 0.014

Steps

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

And I update APT using apt 12.641

And I install "popularity-contest" using apt 22.393

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

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

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

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

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

And I enable persistence 25.578

And I log in to a new session 46.046

And the Additional Software installation service has started 32.225

Then I am notified that the installation succeeded 2.062

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

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

Hooks

After features/support/hooks.rb:515 14.975

After features/support/hooks.rb:326 1.666

After features/support/hooks.rb:100 0.014

Tags: @product @check_tor_leaks @slow

2:29.447

Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package

Hooks

Before features/support/hooks.rb:269 0.006

Before features/support/hooks.rb:507 0.006

Steps

Given a computer 0.239

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

And I update APT using apt 12.420

When I install "makepp" using apt 25.915

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

And the package "makepp" is installed 0.098

Hooks

After features/support/hooks.rb:515 14.520

After features/support/hooks.rb:326 0.933

After features/support/hooks.rb:100 0.011

Tags: @product @check_tor_leaks @slow

4:59.834

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

Before features/support/hooks.rb:507 0.005

Steps

Given a computer 0.211

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

When I uninstall "popularity-contest" using apt 21.850

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

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

When I start Synaptic 23.095

And I update APT using Synaptic 21.904

And I install "cowsay" using Synaptic 9.279

And I accept adding "cowsay" to Additional Software 1.081

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

When I uninstall "cowsay" using apt 3.237

And I refuse removing "cowsay" from Additional Software 0.620

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

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

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

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

When I install "cowsay" using apt 3.203

And I refuse adding "cowsay" to Additional Software 0.558

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

Hooks

After features/support/hooks.rb:515 0.617

After features/support/hooks.rb:326 0.668

After features/support/hooks.rb:100 0.018

Tags: @product @check_tor_leaks @slow @not_release_blocker

8:27.064

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:269 0.005

Before features/support/hooks.rb:507 0.007

Steps

Given a computer 0.199

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

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

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

And I accept adding "cowsay" to Additional Software 7.694

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

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

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

And I enable persistence 20.082

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

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

And I log in to a new session 44.941

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

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

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

And the network is plugged 0.218

And Tor is ready 1:1.699

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:645:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:600: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.029

After features/support/hooks.rb:326 14.418

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:22:15)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5408/artifact/build-artifacts/01:22:15_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/5408/artifact/build-artifacts/01:22:15_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/5408/artifact/build-artifacts/01:22:15_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/5408/artifact/build-artifacts/01:22:15_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.022

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

2:20.224

Scenario I am notified when Additional Software fails to install a package

Hooks

Before features/support/hooks.rb:269 0.007

Before features/support/hooks.rb:507 0.005

Steps

Given a computer 0.245

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

And I enable persistence 17.060

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

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

And I log in to a new session 39.100

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

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

And the package "cowsay" is not installed 0.664

Hooks

After features/support/hooks.rb:515 0.138

After features/support/hooks.rb:326 1.112

After features/support/hooks.rb:100 0.012

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Additional software	64	1	14	0	0	79	4	1	5	23:24.810	Failed

Feature Report