Cucumber Reports (no 4695) - Feature: Additional software

Project	Number	Date
test_Tails_ISO_stable	4695	03 Mar 2024, 15:28

	Steps	Scenarios	Features
Additional software	63	1	11	0	0	75	4	1	5	21:3.897	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:39.250

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

Steps

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

And I update APT using apt 20.023

And I install "popularity-contest" using apt 19.120

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

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

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

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

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

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

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

Hooks

After features/support/hooks.rb:450 36.744

After features/support/hooks.rb:291 1.041

After features/support/hooks.rb:75 0.013

Tags: @product @check_tor_leaks @slow

2:12.398

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

Hooks

Before features/support/hooks.rb:245 0.006

Before features/support/hooks.rb:442 0.005

Steps

Given a computer 0.204

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

And I update APT using apt 18.942

When I install "makepp" using apt 19.129

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

And the package "makepp" is installed 0.070

Hooks

After features/support/hooks.rb:450 40.047

After features/support/hooks.rb:291 0.948

After features/support/hooks.rb:75 0.027

Tags: @product @check_tor_leaks @slow

4:56.381

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

Before features/support/hooks.rb:442 0.005

Steps

Given a computer 0.188

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

When I uninstall "popularity-contest" using apt 18.630

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

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

When I start Synaptic 23.570

And I update APT using Synaptic 26.601

And I install "cowsay" using Synaptic 9.136

And I accept adding "cowsay" to Additional Software 1.190

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

When I uninstall "cowsay" using apt 3.219

And I refuse removing "cowsay" from Additional Software 0.535

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

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

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

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

When I install "cowsay" using apt 3.208

And I refuse adding "cowsay" to Additional Software 0.520

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

Hooks

After features/support/hooks.rb:450 1.160

After features/support/hooks.rb:291 0.643

After features/support/hooks.rb:75 0.008

Tags: @product @check_tor_leaks @slow @not_release_blocker

6:57.933

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

Before features/support/hooks.rb:442 0.005

Steps

Given a computer 0.179

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

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

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

And I accept adding "cowsay" to Additional Software 4.255

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

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

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

And I enable persistence 29.555

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

And I log in to a new session 34.207

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

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

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

And the network is plugged 0.045

And Tor is ready 22.596

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

And available upgrades have been checked 0.736

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

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

The

The Dogtail init script raised: SearchError: descendent of [application | gnome-shell]: child with name="Configure" roleName='push button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:335:in `initialize'
./features/support/helpers/dogtail.rb:264:in `new'
./features/support/helpers/dogtail.rb:264:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:272:in `child'
./features/step_definitions/additional_software_packages.rb:44:in `click_gnome_shell_notification_button'
./features/step_definitions/additional_software_packages.rb:167:in `/^I can open the Additional Software configuration window from the notification$/'
features/additional_software_packages.feature:102:in `And I can open the Additional Software configuration window from the notification'

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

After features/support/hooks.rb:291 4.697

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:21:44)

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4695/artifact/build-artifacts/01:21:44_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/4695/artifact/build-artifacts/01:21:44_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/4695/artifact/build-artifacts/01:21:44_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/4695/artifact/build-artifacts/01:21:44_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/4695/artifact/build-artifacts/01:21:44_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/4695/artifact/build-artifacts/01:21:44_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/4695/artifact/build-artifacts/01:21:44_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/4695/artifact/build-artifacts/01:21:44_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/4695/artifact/build-artifacts/01:21:44_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.031

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

2:17.932

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

Hooks

Before features/support/hooks.rb:245 0.005

Before features/support/hooks.rb:442 0.005

Steps

Given a computer 0.173

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

And I enable persistence 31.516

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

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

And I log in to a new session 33.375

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

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

And the package "cowsay" is not installed 0.637

Hooks

After features/support/hooks.rb:450 0.098

After features/support/hooks.rb:291 1.109

After features/support/hooks.rb:75 0.013

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Additional software	63	1	11	0	0	75	4	1	5	21:3.897	Failed

Feature Report