Cucumber Reports (no 4738) - Feature: Additional software

Project	Number	Date
test_Tails_ISO_stable	4738	25 Mar 2024, 11:56

	Steps	Scenarios	Features
Additional software	63	1	11	0	0	75	4	1	5	20:36.065	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:47.676

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

Before features/support/hooks.rb:442 0.002

Steps

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

And I update APT using apt 16.295

And I install "popularity-contest" using apt 19.406

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

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

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

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

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

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

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

Hooks

After features/support/hooks.rb:450 39.056

After features/support/hooks.rb:291 1.316

After features/support/hooks.rb:75 0.030

Tags: @product @check_tor_leaks @slow

2:15.216

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

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

And I update APT using apt 17.203

When I install "makepp" using apt 19.275

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

And the package "makepp" is installed 0.082

Hooks

After features/support/hooks.rb:450 38.986

After features/support/hooks.rb:291 1.074

After features/support/hooks.rb:75 0.015

Tags: @product @check_tor_leaks @slow

5:15.557

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

Before features/support/hooks.rb:442 0.008

Steps

Given a computer 0.179

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

When I uninstall "popularity-contest" using apt 18.685

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

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

When I start Synaptic 23.813

And I update APT using Synaptic 22.116

And I install "cowsay" using Synaptic 9.989

And I accept adding "cowsay" to Additional Software 1.105

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

When I uninstall "cowsay" using apt 3.234

And I refuse removing "cowsay" from Additional Software 0.540

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

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

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

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

When I install "cowsay" using apt 3.204

And I refuse adding "cowsay" to Additional Software 0.539

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

Hooks

After features/support/hooks.rb:450 1.180

After features/support/hooks.rb:291 0.594

After features/support/hooks.rb:75 0.009

Tags: @product @check_tor_leaks @slow @not_release_blocker

6:16.698

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

Before features/support/hooks.rb:442 0.006

Steps

Given a computer 0.155

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

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

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

And I accept adding "cowsay" to Additional Software 5.566

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

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

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

And I enable persistence 10.841

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

And I log in to a new session 33.744

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

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

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

And the network is plugged 0.050

And Tor is ready 19.902

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

And available upgrades have been checked 0.505

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

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

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

After features/support/hooks.rb:291 4.921

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:19:52)

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4738/artifact/build-artifacts/01:19:52_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/4738/artifact/build-artifacts/01:19:52_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/4738/artifact/build-artifacts/01:19:52_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/4738/artifact/build-artifacts/01:19:52_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/4738/artifact/build-artifacts/01:19:52_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/4738/artifact/build-artifacts/01:19:52_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/4738/artifact/build-artifacts/01:19:52_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/4738/artifact/build-artifacts/01:19:52_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/4738/artifact/build-artifacts/01:19:52_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.017

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

2:0.916

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

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

And I enable persistence 10.239

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

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

And I log in to a new session 33.417

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

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

And the package "cowsay" is not installed 0.639

Hooks

After features/support/hooks.rb:450 0.111

After features/support/hooks.rb:291 0.860

After features/support/hooks.rb:75 0.007

	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	20:36.065	Failed

Feature Report