Cucumber Reports (no 4741) - Feature: Additional software

Project	Number	Date
test_Tails_ISO_stable	4741	26 Mar 2024, 12:18

	Steps	Scenarios	Features
Additional software	62	1	12	0	0	75	4	1	5	23:57.406	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

4:37.852

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:245 0.002

Before features/support/hooks.rb:442 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 51.805

And I update APT using apt 18.622

And I install "popularity-contest" using apt 19.310

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

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

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

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

And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:27.216

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

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

Hooks

After features/support/hooks.rb:450 39.613

After features/support/hooks.rb:291 0.896

After features/support/hooks.rb:75 0.089

Tags: @product @check_tor_leaks @slow

2:14.588

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

Hooks

Before features/support/hooks.rb:245 0.007

Before features/support/hooks.rb:442 0.007

Steps

Given a computer 0.191

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

And I update APT using apt 19.593

When I install "makepp" using apt 19.245

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

And the package "makepp" is installed 0.080

Hooks

After features/support/hooks.rb:450 39.669

After features/support/hooks.rb:291 0.890

After features/support/hooks.rb:75 0.012

Tags: @product @check_tor_leaks @slow

4:32.068

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

Before features/support/hooks.rb:442 0.005

Steps

Given a computer 0.170

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

When I uninstall "popularity-contest" using apt 18.705

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

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

When I start Synaptic 22.685

And I update APT using Synaptic 21.810

And I install "cowsay" using Synaptic 10.725

And I accept adding "cowsay" to Additional Software 0.987

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

When I uninstall "cowsay" using apt 3.211

And I refuse removing "cowsay" from Additional Software 0.506

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

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

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

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

When I install "cowsay" using apt 3.191

And I refuse adding "cowsay" to Additional Software 0.727

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

Hooks

After features/support/hooks.rb:450 1.440

After features/support/hooks.rb:291 1.041

After features/support/hooks.rb:75 0.011

Tags: @product @check_tor_leaks @slow @not_release_blocker

10:30.052

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:245 0.006

Before features/support/hooks.rb:442 0.006

Steps

Given a computer 0.172

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

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

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

And I accept adding "cowsay" to Additional Software 5.336

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

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

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

And I enable persistence 9.619

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

And I log in to a new session 34.705

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

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

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

And the network is plugged 0.028

And Tor is ready 20.187

# Note: the next step races against the appearance of the "The

# upgrade of your additional software failed" notification.

# It should win most of the time, which is good, but there's no

# guarantee it does. If it loses, then it'll remove the notification

# we'll be trying to interact with below ("I can open…")

And all notifications have disappeared 8.595

And available upgrades have been checked 0.056

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

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/common_steps.rb:593:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
features/additional_software_packages.feature:101:in `And I see the "The upgrade of your additional software failed" notification after at most 300 seconds'

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:450 0.035

After features/support/hooks.rb:291 7.322

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:24:03)

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4741/artifact/build-artifacts/01:24:03_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_stable/4741/artifact/build-artifacts/01:24:03_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_stable/4741/artifact/build-artifacts/01:24:03_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_stable/4741/artifact/build-artifacts/01:24:03_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_stable/4741/artifact/build-artifacts/01:24:03_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_stable/4741/artifact/build-artifacts/01:24:03_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/4741/artifact/build-artifacts/01:24:03_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4741/artifact/build-artifacts/01:24:03_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4741/artifact/build-artifacts/01:24:03_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal

After features/support/hooks.rb:75 0.021

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

2:2.845

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

Hooks

Before features/support/hooks.rb:245 0.006

Before features/support/hooks.rb:442 0.006

Steps

Given a computer 0.164

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

And I enable persistence 10.595

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

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

And I log in to a new session 35.275

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

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

And the package "cowsay" is not installed 0.702

Hooks

After features/support/hooks.rb:450 0.098

After features/support/hooks.rb:291 0.745

After features/support/hooks.rb:75 0.008

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Additional software	62	1	12	0	0	75	4	1	5	23:57.406	Failed

Feature Report