Cucumber Reports (no 5270) - Feature: Additional software

Project	Number	Date
test_Tails_ISO_stable	5270	16 Nov 2024, 08:41

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

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 1:0.116

And I update APT using apt 13.528

And I install "popularity-contest" using apt 22.437

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

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

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

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

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

And I enable persistence 24.774

And I log in to a new session 31.054

And the Additional Software installation service has started 32.721

Then I am notified that the installation succeeded 1.609

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

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

Hooks

After features/support/hooks.rb:515 14.838

After features/support/hooks.rb:326 1.064

After features/support/hooks.rb:100 0.010

Tags: @product @check_tor_leaks @slow

2:28.269

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

Steps

Given a computer 0.264

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

And I update APT using apt 11.871

When I install "makepp" using apt 22.682

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

And the package "makepp" is installed 0.073

Hooks

After features/support/hooks.rb:515 15.271

After features/support/hooks.rb:326 0.980

After features/support/hooks.rb:100 0.016

Tags: @product @check_tor_leaks @slow

4:59.387

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

Before features/support/hooks.rb:507 0.008

Steps

Given a computer 0.274

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

When I uninstall "popularity-contest" using apt 15.638

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

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

When I start Synaptic 26.068

And I update APT using Synaptic 22.203

And I install "cowsay" using Synaptic 8.836

And I accept adding "cowsay" to Additional Software 2.121

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

When I uninstall "cowsay" using apt 3.238

And I refuse removing "cowsay" from Additional Software 0.583

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

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

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

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

When I install "cowsay" using apt 3.217

And I refuse adding "cowsay" to Additional Software 0.573

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

Hooks

After features/support/hooks.rb:515 0.656

After features/support/hooks.rb:326 0.689

After features/support/hooks.rb:100 0.007

Tags: @product @check_tor_leaks @slow @not_release_blocker

8:25.674

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

Before features/support/hooks.rb:507 0.006

Steps

Given a computer 0.193

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

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

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

And I accept adding "cowsay" to Additional Software 4.706

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

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

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

And I enable persistence 21.021

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

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

And I log in to a new session 38.911

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

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

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

And the network is plugged 0.072

And Tor is ready 1:1.781

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

After features/support/hooks.rb:326 14.305

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:54)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5270/artifact/build-artifacts/01:24:54_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/5270/artifact/build-artifacts/01:24:54_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/5270/artifact/build-artifacts/01:24:54_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/5270/artifact/build-artifacts/01:24:54_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.015

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

2:15.426

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

Hooks

Before features/support/hooks.rb:269 0.004

Before features/support/hooks.rb:507 0.004

Steps

Given a computer 0.211

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

And I enable persistence 12.598

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

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

And I log in to a new session 44.123

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

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

And the package "cowsay" is not installed 1.274

Hooks

After features/support/hooks.rb:515 0.147

After features/support/hooks.rb:326 1.238

After features/support/hooks.rb:100 0.008

	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	22:55.641	Failed

Feature Report