Project Number Date
test_Tails_ISO_21565-flatpak-safe 52 26 Sep 2026, 03:39

Failures Overview

The following summary displays scenarios that failed.

2:36.853
Scenario GNOME Software does not start until Tor is ready
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Before features/support/hooks.rb:527 0.010
Steps
Given I have started Tails without network with the Flatpak feature from a USB drive with a persistent partition enabled and logged in 2:36.853
Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:800:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:795:in `each'
./features/step_definitions/usb.rb:795:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:206:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:203:in `each'
./features/step_definitions/snapshots.rb:203:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:226:in `/^I\ have\ started\ Tails\ without\ network\ with\ the\ Flatpak\ feature\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/flatpak.feature:13:in `Given I have started Tails without network with the Flatpak feature from a USB drive with a persistent partition enabled and logged in'
Then process "gnome-software" is not running 0.000
When I try to start GNOME Software 0.000
Then I see an error about GNOME Software requiring Tor to be ready 0.000
And I close the "zenity" window 0.000
And process "gnome-software" is not running 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then process "gnome-software" is running within 10 seconds 0.000
After features/support/hooks.rb:535 0.028
After features/support/hooks.rb:339 4.896

SCENARIO FAILED: 'GNOME Software does not start until Tor is ready' (at time 00:06:47)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:06:47_GNOME_Software_does_not_start_until_Tor_is_ready.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:06:47_GNOME_Software_does_not_start_until_Tor_is_ready.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:06:47_GNOME_Software_does_not_start_until_Tor_is_ready.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:06:47_GNOME_Software_does_not_start_until_Tor_is_ready.journal

After features/support/hooks.rb:108 0.032
2:44.620
Scenario Installing, starting and uninstalling a Flatpak
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.001
Steps
Given I have started Tails with the Flatpak feature from a USB drive with a persistent partition enabled and logged in and the network is connected 2:44.620
Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:800:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:795:in `each'
./features/step_definitions/usb.rb:795:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:206:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:203:in `each'
./features/step_definitions/snapshots.rb:203:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:190:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:226:in `/^I\ have\ started\ Tails\ with\ the\ Flatpak\ feature\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/flatpak.feature:25:in `Given I have started Tails with the Flatpak feature from a USB drive with a persistent partition enabled and logged in and the network is connected'
When I start GNOME Software 0.000
And I install Signal Desktop using GNOME Software 0.000
Then the org.signal.Signal Flatpak is installed after at most 600 seconds 0.000
When I start the org.signal.Signal Flatpak 0.000
Then the org.signal.Signal Flatpak is running 0.000
Given I kill the org.signal.Signal Flatpak 0.000
And I go to the main screen of GNOME Software 0.000
When I uninstall Signal Desktop using GNOME Software 0.000
Then the org.signal.Signal Flatpak is uninstalled after at most 60 seconds 0.000
After features/support/hooks.rb:535 0.038
After features/support/hooks.rb:339 4.570

SCENARIO FAILED: 'Installing, starting and uninstalling a Flatpak' (at time 00:09:36)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:09:36_Installing,_starting_and_uninstalling_a_Flatpak.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:09:36_Installing,_starting_and_uninstalling_a_Flatpak.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:09:36_Installing,_starting_and_uninstalling_a_Flatpak.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:09:36_Installing,_starting_and_uninstalling_a_Flatpak.journal

After features/support/hooks.rb:108 0.007
2:44.062
Scenario Changing locale after installing a Flatpak
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.001
Steps
Given I have started Tails with the Flatpak feature from a USB drive with a persistent partition enabled and logged in and the network is connected 2:44.062
Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:800:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:795:in `each'
./features/step_definitions/usb.rb:795:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./features/step_definitions/snapshots.rb:206:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:203:in `each'
./features/step_definitions/snapshots.rb:203:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:190:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:226:in `/^I\ have\ started\ Tails\ with\ the\ Flatpak\ feature\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/flatpak.feature:38:in `Given I have started Tails with the Flatpak feature from a USB drive with a persistent partition enabled and logged in and the network is connected'
When I start GNOME Software 0.000
And I install Thunderbird using GNOME Software 0.000
Then the org.mozilla.thunderbird Flatpak is installed after at most 600 seconds 0.000
And the "de" locale is not present in the org.mozilla.thunderbird.Locale Flatpak extension 0.000
Given I set Tails to boot with options "flatpak" 0.000
When I cold reboot the computer 0.000
Then the computer boots Tails 0.000
When I enable persistence 0.000
And I log in to a new session in German (de) 0.000
Given it has been 3 days since GNOME Software checked for updates 0.000
And GNOME Software thinks it is after 06:00 but before 23:00 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the "de" locale is present in the org.mozilla.thunderbird.Locale Flatpak extension after at most 600 seconds 0.000
After features/support/hooks.rb:535 0.037
After features/support/hooks.rb:339 4.700

SCENARIO FAILED: 'Changing locale after installing a Flatpak' (at time 00:12:25)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:12:25_Changing_locale_after_installing_a_Flatpak.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:12:25_Changing_locale_after_installing_a_Flatpak.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:12:25_Changing_locale_after_installing_a_Flatpak.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:12:25_Changing_locale_after_installing_a_Flatpak.journal

After features/support/hooks.rb:108 0.007
Tags: @product
5:29.365
Scenario Using obfs4 pluggable transports from a QR code
Steps
When I configure some obfs4 bridges from a QR code in the Tor Connection Assistant in hide mode 28.521
Then I wait until Tor is ready 0.839
And tca.conf includes the configured bridges 0.004
And available upgrades have been checked 5:0.000
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:764:in `/^available upgrades have been checked$/'
features/tor_bridges.feature:31:in `And available upgrades have been checked'
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:339 4.929

SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:27:20)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:27:20_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:27:20_Using_obfs4_pluggable_transports_from_a_QR_code.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:27:20_Using_obfs4_pluggable_transports_from_a_QR_code.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:27:20_Using_obfs4_pluggable_transports_from_a_QR_code.journal

After features/support/hooks.rb:108 0.057
Tags: @product
5:21.843
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 5.263
And I wait until Tor is ready 1.556
When I disconnect the network through GNOME 7.560
And I connect the network through GNOME 6.211
Then the Tor Connection Assistant autostarts 0.113
And the Tor Connection Assistant connects to Tor 0.142
And I wait until Tor is ready 0.994
And Tor is using the same configuration as before 0.000
And available upgrades have been checked 5:0.000
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:764:in `/^available upgrades have been checked$/'
features/tor_bridges.feature:80:in `And available upgrades have been checked'
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:339 4.973

SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:35:03)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:35:03_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:35:03_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:35:03_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/00:35:03_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal

After features/support/hooks.rb:108 0.048
5:43.624
Scenario I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Before features/support/hooks.rb:527 0.010
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 5:43.624
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:764:in `/^available upgrades have been checked$/'
./features/step_definitions/common_steps.rb:273:in `/^I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login$/'
features/additional_software_packages.feature:28:in `Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login'
And I update the APT lists using apt 0.000
And I install "popularity-contest" using apt 0.000
Then I am proposed to add the "popularity-contest" package to my Additional Software 0.000
When I create a persistent storage and activate the Additional Software feature 0.000
Then Additional Software is correctly configured for package "popularity-contest" 0.000
When 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
And I log in to a new session 0.000
And the Additional Software installation service has started 0.000
Then I am notified that the installation succeeded 0.000
And Additional Software is correctly configured for package "popularity-contest" 0.000
And the package "popularity-contest" is installed after Additional Software has been installed 0.000
After features/support/hooks.rb:535 0.030
After features/support/hooks.rb:339 4.869

SCENARIO FAILED: 'I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails' (at time 01:06:39)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:06:39_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.file_content_var_log_boot.log

Content of /run/live-additional-software/log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:06:39_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.file_content_run_live-additional-software_log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:06:39_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:06:39_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:06:39_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:06:39_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_mount

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:06:39_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:06:39_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:06:39_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.journal

After features/support/hooks.rb:108 0.000
2:42.153
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.001
Steps
Given a computer 0.077
And I start Tails from USB drive "__internal" and I login with an administration password 1:1.241
And I update the APT lists using apt 35.501
When I install "ripgrep" using apt 3.201
Then the Additional Software dpkg hook has been run for package "ripgrep" and notices the persistence is locked 1:2.132
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/additional_software_packages.rb:153:in `/^the Additional Software dpkg hook has been run for package "([^"]*)" and notices the persistence is locked$/'
features/additional_software_packages.feature:49:in `Then the Additional Software dpkg hook has been run for package "ripgrep" and notices the persistence is locked'
And the package "ripgrep" is installed 0.000
After features/support/hooks.rb:535 0.040
After features/support/hooks.rb:339 4.912

SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:09:26)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:09:26_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_var_log_boot.log

Content of /run/live-additional-software/log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:09:26_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_run_live-additional-software_log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:09:26_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:09:26_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:09:26_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:09:26_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_mount

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:09:26_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:09:26_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:09:26_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal

After features/support/hooks.rb:108 0.012
46.383
Scenario My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.004
Steps
Given a computer 0.080
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 46.302
The
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:698:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:729:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:245:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/additional_software_packages.feature:55:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
When I uninstall "popularity-contest" using apt 0.000
And I accept removing "popularity-contest" from Additional Software 0.000
Then "popularity-contest" is not in the list of Additional Software 0.000
When I start Synaptic 0.000
And I update the APT lists using Synaptic 0.000
And I install "cowsay" using Synaptic 0.000
And I accept adding "cowsay" to Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I uninstall "cowsay" using apt 0.000
And I refuse removing "cowsay" from Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I remove "cowsay" from the list of Additional Software using Additional Software GUI 0.000
Then "cowsay" is not in the list of Additional Software 0.000
When I install "cowsay" using apt 0.000
And I refuse adding "cowsay" to Additional Software 0.000
Then "cowsay" is not in the list of Additional Software 0.000
After features/support/hooks.rb:535 0.029
After features/support/hooks.rb:339 5.271

SCENARIO FAILED: 'My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic' (at time 01:10:18)

Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:10:18_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_var_log_boot.log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:10:18_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:10:18_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:10:18_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:10:18_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_mount

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:10:18_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:10:18_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:10:18_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.journal

After features/support/hooks.rb:108 0.004
44.900
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.001
Steps
Given a computer 0.076
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 44.824
The
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:698:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:729:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:245:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/additional_software_packages.feature:79:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
And I configure APT to prefer an old version of cowsay 0.000
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 0.000
And I accept adding "cowsay" to Additional Software 0.000
And Additional Software is correctly configured for package "cowsay" 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
# 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.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 installed 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
# 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.000
And the network is plugged 0.000
And Tor is ready 0.000
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 installed 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
After features/support/hooks.rb:535 0.030
After features/support/hooks.rb:339 5.163

SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:11:08)

Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:11:08_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:11:08_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.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:11:08_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.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:11:08_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.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:11:08_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.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:11:08_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:11:08_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:11:08_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal

After features/support/hooks.rb:108 0.004
45.152
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.001
Steps
Given a computer 0.076
And I start Tails from USB drive "__internal" with network unplugged 31.606
And I enable persistence 13.468
The
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:698:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:729:in `/^I enable persistence( with the changed passphrase)?$/'
features/additional_software_packages.feature:123:in `And I enable persistence'
And I remove the "cowsay" deb files from the APT cache 0.000
And I log in to a new session 0.000
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 0.000
And I can open the Additional Software log file from the notification 0.000
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:535 0.035
After features/support/hooks.rb:339 4.827

SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:11:58)

Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:11:58_I_am_notified_when_Additional_Software_fails_to_install_a_package.file_content_var_log_boot.log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:11:58_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:11:58_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:11:58_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:11:58_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:11:58_I_am_notified_when_Additional_Software_fails_to_install_a_package.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:11:58_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:11:58_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal

After features/support/hooks.rb:108 0.004
5:21.195
Scenario Tails shuts down on DVD boot medium removal
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Steps
Given I have started Tails from DVD and logged in and the network is connected 5:21.195
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:764:in `/^available upgrades have been checked$/'
./features/step_definitions/snapshots.rb:206:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:203:in `each'
./features/step_definitions/snapshots.rb:203:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:226:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/emergency_shutdown.feature:12:in `Given I have started Tails from DVD and logged in and the network is connected'
When I eject the boot medium 0.000
Then Tails eventually shuts down 0.000
After features/support/hooks.rb:339 4.729

SCENARIO FAILED: 'Tails shuts down on DVD boot medium removal' (at time 01:32:40)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:32:40_Tails_shuts_down_on_DVD_boot_medium_removal.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:32:40_Tails_shuts_down_on_DVD_boot_medium_removal.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:32:40_Tails_shuts_down_on_DVD_boot_medium_removal.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:32:40_Tails_shuts_down_on_DVD_boot_medium_removal.journal

After features/support/hooks.rb:108 0.000
5:21.032
Background
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Steps
Given I have started Tails from DVD without network and logged in 6.243
And I capture all network traffic 0.004
And the network is plugged 0.049
And Tor is ready 7.735
And all notifications have disappeared 6.998
And available upgrades have been checked 5:0.000
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:764:in `/^available upgrades have been checked$/'
features/dhcp.feature:14:in `And available upgrades have been checked'
Tags: @product
0.000
Scenario Getting a DHCP lease with a manually configured NetworkManager connection
Steps
When I add a wired DHCP NetworkManager connection called "manually-added-con" 0.000
And I switch to the "manually-added-con" NetworkManager connection 0.000
Then the hostname should not have been leaked on the network 0.000
After features/support/hooks.rb:339 4.755

SCENARIO FAILED: 'Getting a DHCP lease with a manually configured NetworkManager connection' (at time 01:45:09)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:45:09_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:45:09_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:45:09_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:45:09_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.journal

After features/support/hooks.rb:108 0.038
4:1.419
Scenario The Tails documentation launcher works when online
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Steps
Given I have started Tails from DVD and logged in and the network is connected 34.871
When I start "Tails Documentation" via GNOME Activities Overview 9.314
Then the Tor Browser has started 17.223
And "Tails - Documentation" has loaded in the Tor Browser 3:0.009
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/browser.rb:263:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:278:in `/^"([^"]+)" has loaded in the Tor Browser$/'
features/documentation.feature:14:in `And "Tails - Documentation" has loaded in the Tor Browser'
After features/support/hooks.rb:339 5.175

SCENARIO FAILED: 'The Tails documentation launcher works when online' (at time 01:49:42)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:49:42_The_Tails_documentation_launcher_works_when_online.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:49:42_The_Tails_documentation_launcher_works_when_online.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:49:42_The_Tails_documentation_launcher_works_when_online.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/01:49:42_The_Tails_documentation_launcher_works_when_online.journal

After features/support/hooks.rb:108 0.000
Tags: @product
5:15.809
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.972
And the network is plugged 0.043
And I successfully configure Tor 7.794
And available upgrades have been checked 5:0.000
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:764:in `/^available upgrades have been checked$/'
features/torified_browsing.feature:105:in `And available upgrades have been checked'
And all notifications have disappeared 0.000
And there is a GNOME bookmark for the Persistent directory 0.000
When I start the Tor Browser 0.000
And I download some file in the Tor Browser to the Persistent directory 0.000
Then the file is saved to the Persistent directory 0.000
When I open the address "https://tails.net/about" in the Tor Browser 0.000
Then "Tails - How Tails works" has loaded in the Tor Browser 0.000
And I can print the current page as "output.pdf" to the Persistent directory 0.000
After features/support/hooks.rb:339 5.045

SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 03:32:20)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/03:32:20_The_Persistent_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/03:32:20_The_Persistent_directory_is_usable_in_Tor_Browser.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/03:32:20_The_Persistent_directory_is_usable_in_Tor_Browser.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/52/artifact/build-artifacts/03:32:20_The_Persistent_directory_is_usable_in_Tor_Browser.journal

After features/support/hooks.rb:108 0.000