Cucumber Reports (no 5217) - Feature: Additional software

Project	Number	Date
test_Tails_ISO_stable	5217	24 Oct 2024, 12:47

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

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

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 59.881

And I update APT using apt 11.954

And I install "popularity-contest" using apt 25.647

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

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

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

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

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

And I enable persistence 21.595

And I log in to a new session 42.539

And the Additional Software installation service has started 32.019

Then I am notified that the installation succeeded 1.651

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

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

Hooks

After features/support/hooks.rb:515 13.912

After features/support/hooks.rb:326 1.313

After features/support/hooks.rb:100 0.011

Tags: @product @check_tor_leaks @slow

2:55.007

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

Hooks

Before features/support/hooks.rb:269 0.003

Before features/support/hooks.rb:507 0.003

Steps

Given a computer 0.196

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

And I update APT using apt 11.638

When I install "makepp" using apt 25.712

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

And the package "makepp" is installed 0.091

Hooks

After features/support/hooks.rb:515 15.044

After features/support/hooks.rb:326 0.952

After features/support/hooks.rb:100 0.012

Tags: @product @check_tor_leaks @slow

4:57.245

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

Before features/support/hooks.rb:507 0.006

Steps

Given a computer 0.233

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

When I uninstall "popularity-contest" using apt 15.672

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

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

When I start Synaptic 24.154

And I update APT using Synaptic 22.715

And I install "cowsay" using Synaptic 8.630

And I accept adding "cowsay" to Additional Software 2.227

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

When I uninstall "cowsay" using apt 3.261

And I refuse removing "cowsay" from Additional Software 0.468

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

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

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

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

When I install "cowsay" using apt 3.221

And I refuse adding "cowsay" to Additional Software 0.604

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

Hooks

After features/support/hooks.rb:515 0.604

After features/support/hooks.rb:326 0.705

After features/support/hooks.rb:100 0.008

Tags: @product @check_tor_leaks @slow @not_release_blocker

8:13.881

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

Steps

Given a computer 0.219

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

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

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

And I accept adding "cowsay" to Additional Software 4.644

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

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

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

And I enable persistence 16.596

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

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

And I log in to a new session 39.960

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

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

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

And Tor is ready 1:2.152

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

After features/support/hooks.rb:326 14.392

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:28:58)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5217/artifact/build-artifacts/01:28:58_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/5217/artifact/build-artifacts/01:28:58_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/5217/artifact/build-artifacts/01:28:58_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/5217/artifact/build-artifacts/01:28:58_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.018

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

2:11.317

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

Hooks

Before features/support/hooks.rb:269 0.005

Before features/support/hooks.rb:507 0.029

Steps

Given a computer 0.268

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

And I enable persistence 10.946

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

And I log in to a new session 40.101

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

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

And the package "cowsay" is not installed 0.515

Hooks

After features/support/hooks.rb:515 0.135

After features/support/hooks.rb:326 1.153

After features/support/hooks.rb:100 0.011

	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:17.874	Failed

Feature Report