Project Number Date
test_Tails_ISO_test-suite-trixie-2 2 06 Jun 2025, 23:34

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
41.908
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 41.908
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/tor.rb:663:in `block (2 levels) in <top (required)>'
./features/step_definitions/tor.rb:499:in `tca_configure'
./features/step_definitions/tor.rb:626:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/tor_bridges.feature:28:in `When I configure some obfs4 bridges from a QR code in the Tor Connection Assistant in hide mode'
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:330 6.893 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:30:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/00:30:16_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/00:30:16_Using_obfs4_pluggable_transports_from_a_QR_code.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/00:30:16_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/00:30:16_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:100 0.045
Feature: Using Tor bridges and pluggable transports
Tags: @product
1:11.154
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 2.285
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 30.972
Then the Tor Connection Assistant reports that it failed to connect 0.122
And tca.conf is empty 0.963
Given I scan a QR code from the error page in Tor Connection Assistant 36.810
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/tor.rb:737:in `/^I scan a QR code from the error page in Tor Connection Assistant$/'
features/tor_bridges.feature:39:in `Given I scan a QR code from the error page in Tor Connection Assistant'
And I retry connecting to Tor 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 9.873 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:31:52)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/00:31:52_TCA_can_scan_QR_code_after_a_connection_failure.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/00:31:52_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/00:31:52_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.038
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
16.638
Scenario Erasure of memory freed by killed userspace processes
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails from DVD without network and logged in 9.129
And I prepare Tails for memory erasure tests 1.072
When I start a process allocating 128 MiB of memory with a known pattern 2.337
Then patterns cover at least 128 MiB in the guest's memory 4.099
99.610% 
99.610% of the expected size (128 MiB) has the pattern, but more than 100.000% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:186:in `/^patterns cover at least (\d+) MiB in the guest's memory$/'
features/erase_memory.feature:17:in `Then patterns cover at least 128 MiB in the guest's memory'
Output 1 
Pattern coverage: 99.610% (127 MiB out of 128 MiB reference memory)
When I kill the allocating process 0.000
Then I find very few patterns in the guest's memory after 5 seconds 0.000
After features/support/hooks.rb:330 5.471 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:38:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/00:38:50_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/00:38:50_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/00:38:50_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/00:38:50_Erasure_of_memory_freed_by_killed_userspace_processes.journal
After features/support/hooks.rb:100 0.000
Feature: Additional software
Tags: @product @check_tor_leaks @slow
11:52.303
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:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:513 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:27.437
And I update APT using apt 12.249
And I install "popularity-contest" using apt 27.485
Then I am proposed to add the "popularity-contest" package to my Additional Software 10.374
When I create a persistent storage and activate the Additional Software feature 26.799
Then Additional Software is correctly configured for package "popularity-contest" 3.067
When I shutdown Tails and wait for the computer to power off 13.940
And I start Tails from USB drive "__internal" with network unplugged 1:49.727
And I enable persistence 30.392
And I log in to a new session 52.627
And the Additional Software installation service has started 33.630
Then I am notified that the installation succeeded 5:4.572
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:598:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
./features/step_definitions/additional_software_packages.rb:28:in `/^I am notified that the installation succeeded$/'
features/additional_software_packages.feature:39:in `Then I am notified that the installation succeeded'
And Additional Software is correctly configured for package "popularity-contest" 0.000
And the package "popularity-contest" is installed after Additional Software has been started 0.000
After features/support/hooks.rb:521 0.044
After features/support/hooks.rb:330 6.103 
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:27:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/01:27:43_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/01:27:43_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/01:27:43_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/01:27:43_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/01:27:43_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/01:27:43_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/01:27:43_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/01:27:43_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/01:27:43_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:100 0.011
Feature: Additional software
Tags: @product @check_tor_leaks @slow
25:20.690
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:513 0.003
Steps
Given a computer 0.181
And I start Tails from USB drive "__internal" and I login with an administration password 3:2.642
And I update APT using apt 11.795
When I install "makepp" using apt 22:6.070
Tor 
Tor operation failed (despite retrying 10 times) with
Timeout::Error: try_for() timeout expired
Last ignored exception was: ExecutionFailedInVM: Command failed: dpkg -s 'makepp' 2>/dev/null | grep -qs '^Status:.*installed$'
error code: 1
stdout: 
stderr: .
<false> is not true.
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/apt.rb:69:in `block in wait_for_package_installation'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/apt.rb:68:in `wait_for_package_installation'
./features/step_definitions/apt.rb:86:in `block (3 levels) in <top (required)>'
./features/step_definitions/apt.rb:82:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:211:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:81:in `block in <top (required)>' (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:81:in `/^I install "(.+)" using apt$/'
features/additional_software_packages.feature:48:in `When I install "makepp" using apt'
Then the Additional Software dpkg hook has been run for package "makepp" and notices the persistence is locked 0.000
And the package "makepp" is installed 0.000
After features/support/hooks.rb:521 0.040
After features/support/hooks.rb:330 5.328 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:53:10)
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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/01:53:10_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/01:53:10_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/01:53:10_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/01:53:10_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/01:53:10_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/01:53:10_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/01:53:10_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/01:53:10_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.010
Feature: Additional software
Tags: @product @check_tor_leaks @slow
10:18.246
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:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:513 0.002
Steps
Given a computer 0.152
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 4:35.613
When I uninstall "popularity-contest" using apt 25.084
And I accept removing "popularity-contest" from Additional Software 2.756
Then "popularity-contest" is not in the list of Additional Software 0.942
When I start Synaptic 16.680
And I update APT using Synaptic 21.864
And I install "cowsay" using Synaptic 4:35.150
Tor 
Tor operation failed (despite retrying 10 times) with
Dogtail::Failure: The Dogtail init script raised: SearchError: child of [application | synaptic]: 'Find' dialog
STDOUT:

STDERR:

 (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:180:in `/^I install "(.+)" using Synaptic$/'
features/additional_software_packages.feature:61:in `And I install "cowsay" using Synaptic'
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:521 0.066
After features/support/hooks.rb:330 6.111 
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 02:03:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:03:34_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
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:03:34_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.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_test-suite-trixie-2/2/artifact/build-artifacts/02:03:34_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:03:34_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:03:34_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:03:34_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:03:34_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:03:34_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:03:34_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:100 0.039
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
3:17.118
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:513 0.003
Steps
Given a computer 0.215
And I start Tails from USB drive "__internal" with network unplugged 1:48.384
And I enable persistence 22.118
And I remove the "cowsay" deb files from the APT cache 0.090
# 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.095
And I log in to a new session 38.302
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 16.714
And I can open the Additional Software log file from the notification 11.196
The 
The Dogtail init script raised: SearchError: descendant of [notification | ]: child with name='Show Log' roleName='button'
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/additional_software_packages.rb:39:in `click_gnome_shell_notification_button'
./features/step_definitions/additional_software_packages.rb:166:in `/^I can open the Additional Software log file from the notification$/'
features/additional_software_packages.feature:130:in `And I can open the Additional Software log file from the notification'
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:521 0.030
After features/support/hooks.rb:330 6.559 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 02:22:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:22:54_I_am_notified_when_Additional_Software_fails_to_install_a_package.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:22:54_I_am_notified_when_Additional_Software_fails_to_install_a_package.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_test-suite-trixie-2/2/artifact/build-artifacts/02:22:54_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:22:54_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.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:22:54_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:22:54_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:22:54_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:22:54_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:22:54_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.008
Feature: Upgrading an old Tails USB installation
Tags: @product
3:16.656
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 40.596
When I start Tails from USB drive "old" with network unplugged 2:34.784
The 
The Dogtail init script raised: SearchError: descendent of [application | gnome-shell]: child with roleName='notification'
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/common_steps.rb:456:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276: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/usb_upgrade.feature:25:in `When I start Tails from USB drive "old" with network unplugged'
Then the boot device has safe access rights 0.000
And Tails is running from USB drive "old" 0.000
And there is no persistence partition on USB drive "old" 0.000
And process "udev-watchdog" is running 0.000
And udev-watchdog is monitoring the correct device 0.000
And I unplug USB drive "old" 0.000
After features/support/hooks.rb:330 5.800 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:26:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:26:17_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:26:17_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:26:17_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:26:17_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product
2:8.552
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 2:8.379
The 
The Dogtail init script raised: SearchError: descendent of [application | gnome-shell]: child with roleName='notification'
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/common_steps.rb:456:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276: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/usb_upgrade.feature:36:in `And I start Tails from USB drive "old" with network unplugged and I login'
Then Tails is running from USB drive "old" 0.000
And I create a persistent partition 0.000
And I take note of which tps features are available 0.000
Then a Tails persistence partition exists on USB drive "old" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
After features/support/hooks.rb:330 6.112 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:28:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:28:31_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:28:31_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:28:31_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:28:31_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.008
Feature: Upgrading an old Tails USB installation
Tags: @product
1:59.588
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.260
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:59.327
The 
The Dogtail init script raised: SearchError: descendent of [application | gnome-shell]: child with roleName='notification'
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/common_steps.rb:456:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276: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/usb_upgrade.feature:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:330 6.144 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:30:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:30:37_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:30:37_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:30:37_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:30:37_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.030
Feature: Upgrading an old Tails USB installation
Tags: @product
2:8.316
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.161
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.155
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:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:283: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/usb_upgrade.feature:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:330 6.248 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:36:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:36:23_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:36:23_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:36:23_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:36:23_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.005
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
22:57.627
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.158
And no SquashFS delta is installed 0.308
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.354
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.368
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.867
When the network is plugged 0.090
And Tor is ready 23.863
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:12.520
Tor 
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderUpgradeTo6.2~testoverlayfs.png", "TailsUpgraderFailure.png"] on the screen (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/usb.rb:1301:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:90:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:330 5.395 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:59:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:59:27_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:59:27_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:59:27_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/02:59:27_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
22:43.018
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.827
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.491
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.167
And the signing key used by the Upgrader is outdated 0.083
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 18.360
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:12.011
Tor 
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderUpgradeTo6.2~testoverlayfs.png", "TailsUpgraderFailure.png"] on the screen (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/usb.rb:1301:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:134:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
After features/support/hooks.rb:330 5.375 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:22:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:22:15_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:22:15_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:22:15_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:22:15_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
0.111
Scenario Getting a DHCP lease with the default NetworkManager connection
Steps
Then the hostname should not have been leaked on the network 0.111
Hostname 
Hostname leak detected (DhcpLeakError)
./features/step_definitions/dhcp.rb:15:in `/^the hostname should not have been leaked on the network$/'
features/dhcp.feature:17:in `Then the hostname should not have been leaked on the network'
After features/support/hooks.rb:330 5.114 
SCENARIO FAILED: 'Getting a DHCP lease with the default NetworkManager connection' (at time 03:32:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:32:46_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.file_content_var_log_boot.log
Network capture: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:32:46_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.pcap
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:32:46_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:32:46_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:32:46_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.051
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
0.900
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.293
And I switch to the "manually-added-con" NetworkManager connection 0.513
Then the hostname should not have been leaked on the network 0.093
Hostname 
Hostname leak detected (DhcpLeakError)
./features/step_definitions/dhcp.rb:15:in `/^the hostname should not have been leaked on the network$/'
features/dhcp.feature:22:in `Then the hostname should not have been leaked on the network'
After features/support/hooks.rb:330 5.012 
SCENARIO FAILED: 'Getting a DHCP lease with a manually configured NetworkManager connection' (at time 03:33:24)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:33:24_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.file_content_var_log_boot.log
Network capture: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:33:24_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.pcap
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:33:24_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:33:24_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:33:24_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.060
Feature: Hardware failures
Tags: @product
2:54.040
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 12.624
And I corrupt the boot device's GPT backup header 0.598
And I power off the computer 0.340
When I start the computer 1.135
Then the computer boots Tails 1:51.817
When I log in to a new session 29.902
And all notifications have disappeared 17.212
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.409
<nil> 
<nil> was expected to not be nil. (Test::Unit::AssertionFailedError)
./features/step_definitions/hardware.rb:84:in `/^I am recommended to migrate to a new USB stick due to partitioning errors$/'
features/hardware_failure.feature:45:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'
features/hardware_failure.feature:41:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'
And Tails detected partitioning error partitioning-corruption 0.000
After features/support/hooks.rb:330 6.353 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 03:51:01)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:51:01_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:51:01_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:51:01_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:51:01_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:100 0.006
Feature: Hardware failures
Tags: @product
2:45.239
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.624
And I corrupt the boot device's GPT backup partition table 0.459
And I power off the computer 0.343
When I start the computer 1.109
Then the computer boots Tails 1:53.328
When I log in to a new session 24.098
And all notifications have disappeared 15.987
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.288
<nil> 
<nil> was expected to not be nil. (Test::Unit::AssertionFailedError)
./features/step_definitions/hardware.rb:84:in `/^I am recommended to migrate to a new USB stick due to partitioning errors$/'
features/hardware_failure.feature:46:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'
features/hardware_failure.feature:41:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'
And Tails detected partitioning error partitioning-corruption 0.000
After features/support/hooks.rb:330 6.536 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 03:53:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:53:52_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:53:52_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:53:52_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:53:52_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:100 0.006
Feature: Hardware failures
Tags: @product
3:47.415
Scenario GPT backup corruption without a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given a computer 0.163
And I set Tails to boot with options "test_gpt_corruption=gpt_backup,gpt_backup_table" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.037
And I plug USB drive "temp" 1.051
And I write the Tails USB image to disk "temp" 31.937
When I start Tails from USB drive "temp" with network unplugged 2:30.542
Then Tails is running from USB drive "temp" 0.396
And the Greeter forbids creating a persistent partition 0.124
When I log in to a new session 24.157
And all notifications have disappeared 18.668
Then I am recommended to reinstall Tails due to partitioning errors 0.336
<"OK"> 
<"OK"> was expected to include
<"Creation of Persistent Storage has been disabled">. (Test::Unit::AssertionFailedError)
./features/step_definitions/hardware.rb:94:in `/^I am recommended to reinstall Tails due to partitioning errors$/'
features/hardware_failure.feature:59:in `Then I am recommended to reinstall Tails due to partitioning errors'
# We are gonna verify the dialog again so we need to clean up the
# first instance.
And I close the "zenity" window 0.000
And I am told that Persistent Storage cannot be created 0.000
And Tails detected partitioning error partitioning-corruption 0.000
After features/support/hooks.rb:330 7.203 
SCENARIO FAILED: 'GPT backup corruption without a persistent partition' (at time 03:57:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:57:46_GPT_backup_corruption_without_a_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:57:46_GPT_backup_corruption_without_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:57:46_GPT_backup_corruption_without_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/03:57:46_GPT_backup_corruption_without_a_persistent_partition.journal
After features/support/hooks.rb:100 0.137
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
9.616
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 9.538
Then the keys trusted by APT are valid for the next 3 months 0.077
Command 
Command failed: apt-key adv --batch --with-colons --fingerprint --list-key
error code: 127
stdout: 
stderr: /bin/sh: 1: apt-key: not found
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/checks.rb:19:in `assert_all_keys_are_valid_for_n_months'
./features/step_definitions/checks.rb:8:in `/^the keys trusted by APT are valid for the next (\d+) months$/'
features/keys.feature:11:in `Then the keys trusted by APT are valid for the next 3 months'
After features/support/hooks.rb:330 5.203 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 04:08:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/04:08:08_The_included_APT_repository_keys_are_up-to-date.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/04:08:08_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/04:08:08_The_included_APT_repository_keys_are_up-to-date.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/04:08:08_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:44.273
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 7.807
When I log in to a new session in Italian (it) 40.719
Then the keyboard layout is set to "it" 0.397
When the network is plugged 0.085
And Tor is ready 26.460
Then I successfully start the Unsafe Browser 1:28.802
cannot 
cannot find UnsafeBrowserStartPage.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/unsafe_browser.rb:63:in `/^the Unsafe Browser shows a warning as its start page$/'
./features/step_definitions/unsafe_browser.rb:71:in `/^the Unsafe Browser has started$/'
./features/step_definitions/browser.rb:104:in `/^I successfully start the Unsafe Browser$/'
features/localization.feature:50:in `Then I successfully start the Unsafe Browser'
features/localization.feature:27:in `Then I successfully start the Unsafe Browser'
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 7.391 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#8)' (at time 04:40:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/04:40:05_Tails_is_localized_for_every_tier-1_language,_Examples___8_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/04:40:05_Tails_is_localized_for_every_tier-1_language,_Examples___8_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/04:40:05_Tails_is_localized_for_every_tier-1_language,_Examples___8_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/04:40:05_Tails_is_localized_for_every_tier-1_language,_Examples___8_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:6.567
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 7.799
When I log in to a new session in Portuguese (pt) 44.913
Then the keyboard layout is set to "pt" 0.297
When the network is plugged 0.077
And Tor is ready 19.240
Then I successfully start the Unsafe Browser 16.041
And I kill the Unsafe Browser 7.799
When I enable the screen keyboard 0.183
Then the screen keyboard works in Tor Browser 30.214
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:1043:in `launch_app'
./features/step_definitions/common_steps.rb:1098:in `launch_tor_browser'
./features/step_definitions/browser.rb:474:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:440:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:52:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 11.593 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#10)' (at time 04:45:32)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/04:45:32_Tails_is_localized_for_every_tier-1_language,_Examples___10_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/04:45:32_Tails_is_localized_for_every_tier-1_language,_Examples___10_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/04:45:32_Tails_is_localized_for_every_tier-1_language,_Examples___10_.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
9.771
Scenario No unexpected error messages in the journal after booting from DVD
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 9.618
Then there are no unexpected messages of priority "err" or higher in the journal 0.152
Unexpected 
Unexpected error messages in the journal: [
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "577",
    "_BOOT_ID": "3fa5b052474d42b094a7034890026f07",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "577",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749227518296784",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "00c72972edc1433884fee279304a3f7f",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=561c139fa1d04cfc8f622f0ce9a14d16;i=365;b=3fa5b052474d42b094a7034890026f07;m=c419bf;t=636e9c4dc032c;x=da1966350398e1af",
    "__MONOTONIC_TIMESTAMP": "12851647",
    "__REALTIME_TIMESTAMP": "1749227518296876",
    "__SEQNUM": "869",
    "__SEQNUM_ID": "561c139fa1d04cfc8f622f0ce9a14d16"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "577",
    "_BOOT_ID": "3fa5b052474d42b094a7034890026f07",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "577",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749227518296810",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "00c72972edc1433884fee279304a3f7f",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=561c139fa1d04cfc8f622f0ce9a14d16;i=367;b=3fa5b052474d42b094a7034890026f07;m=c41a46;t=636e9c4dc03b3;x=2fb43328cc730c8d",
    "__MONOTONIC_TIMESTAMP": "12851782",
    "__REALTIME_TIMESTAMP": "1749227518297011",
    "__SEQNUM": "871",
    "__SEQNUM_ID": "561c139fa1d04cfc8f622f0ce9a14d16"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2315",
    "SYSLOG_TIMESTAMP": "Jun  6 16:32:06 ",
    "_BOOT_ID": "3fa5b052474d42b094a7034890026f07",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2315",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749227526539379",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "27a3b87e71934a039569b2e450b58583",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=561c139fa1d04cfc8f622f0ce9a14d16;i=407;b=3fa5b052474d42b094a7034890026f07;m=141df17;t=636e9c559c883;x=fccb29d69cbf715",
    "__MONOTONIC_TIMESTAMP": "21094167",
    "__REALTIME_TIMESTAMP": "1749227526539395",
    "__SEQNUM": "1031",
    "__SEQNUM_ID": "561c139fa1d04cfc8f622f0ce9a14d16"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "577",
    "_BOOT_ID": "3fa5b052474d42b094a7034890026f07",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "577",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749227702522484",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "00c72972edc1433884fee279304a3f7f",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=561c139fa1d04cfc8f622f0ce9a14d16;i=8b6;b=3fa5b052474d42b094a7034890026f07;m=6276d6b;t=636e9cfd72437;x=3877fac15df27051",
    "__MONOTONIC_TIMESTAMP": "103247211",
    "__REALTIME_TIMESTAMP": "1749227702527031",
    "__SEQNUM": "2230",
    "__SEQNUM_ID": "561c139fa1d04cfc8f622f0ce9a14d16"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "577",
    "_BOOT_ID": "3fa5b052474d42b094a7034890026f07",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "577",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749227702522530",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "00c72972edc1433884fee279304a3f7f",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=561c139fa1d04cfc8f622f0ce9a14d16;i=8b8;b=3fa5b052474d42b094a7034890026f07;m=6277327;t=636e9cfd729f7;x=2ffbef6fa3a905cc",
    "__MONOTONIC_TIMESTAMP": "103248679",
    "__REALTIME_TIMESTAMP": "1749227702528503",
    "__SEQNUM": "2232",
    "__SEQNUM_ID": "561c139fa1d04cfc8f622f0ce9a14d16"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "16992",
    "SYSLOG_TIMESTAMP": "Jun  6 16:35:08 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "3fa5b052474d42b094a7034890026f07",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "/usr/bin/perl -T /usr/sbin/deluser amnesia sudo",
    "_COMM": "deluser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "16992",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749227708494469",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "ab9cf72470c34fbf89092731faef8744",
    "_SYSTEMD_OWNER_UID": "1000",
    "_SYSTEMD_SESSION": "4",
    "_SYSTEMD_SLICE": "user-1000.slice",
    "_SYSTEMD_UNIT": "session-4.scope",
    "_SYSTEMD_USER_SLICE": "-.slice",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=561c139fa1d04cfc8f622f0ce9a14d16;i=11e9;b=3fa5b052474d42b094a7034890026f07;m=6827e0a;t=636e9d03234da;x=ed4d366bbd50cdfb",
    "__MONOTONIC_TIMESTAMP": "109215242",
    "__REALTIME_TIMESTAMP": "1749227708495066",
    "__SEQNUM": "4585",
    "__SEQNUM_ID": "561c139fa1d04cfc8f622f0ce9a14d16"
  }
].
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:237:in `/^there are no unexpected messages of priority "err" or higher in the journal$/'
features/sane_defaults.feature:21:in `Then there are no unexpected messages of priority "err" or higher in the journal'
After features/support/hooks.rb:330 5.240 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from DVD' (at time 06:10:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:10:56_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:10:56_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:10:56_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:10:56_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
29.928
Scenario No unexpected error messages in the journal after booting from USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 29.847
Then there are no unexpected messages of priority "err" or higher in the journal 0.080
Unexpected 
Unexpected error messages in the journal: [
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "705",
    "_BOOT_ID": "7deab829c0ab4a16b8e582c0270905ea",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "705",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749229729009161",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "fed6120c52724a299d99cbad95941c3b",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=22abd1c6bda14a79a66143ce3d036355;i=368;b=7deab829c0ab4a16b8e582c0270905ea;m=def798;t=636ea48a0ce1d;x=4d6092fe2e0dd38e",
    "__MONOTONIC_TIMESTAMP": "14612376",
    "__REALTIME_TIMESTAMP": "1749229729009181",
    "__SEQNUM": "872",
    "__SEQNUM_ID": "22abd1c6bda14a79a66143ce3d036355"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "705",
    "_BOOT_ID": "7deab829c0ab4a16b8e582c0270905ea",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "705",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749229729009370",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "fed6120c52724a299d99cbad95941c3b",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=22abd1c6bda14a79a66143ce3d036355;i=36a;b=7deab829c0ab4a16b8e582c0270905ea;m=def857;t=636ea48a0cede;x=1aead16f0acfd623",
    "__MONOTONIC_TIMESTAMP": "14612567",
    "__REALTIME_TIMESTAMP": "1749229729009374",
    "__SEQNUM": "874",
    "__SEQNUM_ID": "22abd1c6bda14a79a66143ce3d036355"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2465",
    "SYSLOG_TIMESTAMP": "Jun  6 17:08:57 ",
    "_BOOT_ID": "7deab829c0ab4a16b8e582c0270905ea",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2465",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749229737454745",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "e8bc82690f5449d89559cb0c34e5b896",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=22abd1c6bda14a79a66143ce3d036355;i=415;b=7deab829c0ab4a16b8e582c0270905ea;m=15fd624;t=636ea4921acaa;x=a279a500507666a2",
    "__MONOTONIC_TIMESTAMP": "23057956",
    "__REALTIME_TIMESTAMP": "1749229737454762",
    "__SEQNUM": "1045",
    "__SEQNUM_ID": "22abd1c6bda14a79a66143ce3d036355"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "705",
    "_BOOT_ID": "7deab829c0ab4a16b8e582c0270905ea",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "705",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749229875149448",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "fed6120c52724a299d99cbad95941c3b",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=22abd1c6bda14a79a66143ce3d036355;i=e93;b=7deab829c0ab4a16b8e582c0270905ea;m=9633d60;t=636ea5156e476;x=dfb6479c01e1f80a",
    "__MONOTONIC_TIMESTAMP": "157498720",
    "__REALTIME_TIMESTAMP": "1749229875160182",
    "__SEQNUM": "3731",
    "__SEQNUM_ID": "22abd1c6bda14a79a66143ce3d036355"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "705",
    "_BOOT_ID": "7deab829c0ab4a16b8e582c0270905ea",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "705",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749229875149508",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "fed6120c52724a299d99cbad95941c3b",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=22abd1c6bda14a79a66143ce3d036355;i=e95;b=7deab829c0ab4a16b8e582c0270905ea;m=9633f19;t=636ea5156e631;x=9ce241fe2e851489",
    "__MONOTONIC_TIMESTAMP": "157499161",
    "__REALTIME_TIMESTAMP": "1749229875160625",
    "__SEQNUM": "3733",
    "__SEQNUM_ID": "22abd1c6bda14a79a66143ce3d036355"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "22936",
    "SYSLOG_TIMESTAMP": "Jun  6 17:11:22 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "7deab829c0ab4a16b8e582c0270905ea",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "/usr/bin/perl -T /usr/sbin/deluser amnesia sudo",
    "_COMM": "deluser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "22936",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749229882850958",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "5c9875ae191348978d995da4ba21ecbf",
    "_SYSTEMD_OWNER_UID": "1000",
    "_SYSTEMD_SESSION": "4",
    "_SYSTEMD_SLICE": "user-1000.slice",
    "_SYSTEMD_UNIT": "session-4.scope",
    "_SYSTEMD_USER_SLICE": "-.slice",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=22abd1c6bda14a79a66143ce3d036355;i=187a;b=7deab829c0ab4a16b8e582c0270905ea;m=9d89780;t=636ea51cc3e98;x=6c1def5caccd786b",
    "__MONOTONIC_TIMESTAMP": "165189504",
    "__REALTIME_TIMESTAMP": "1749229882850968",
    "__SEQNUM": "6266",
    "__SEQNUM_ID": "22abd1c6bda14a79a66143ce3d036355"
  }
].
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:237:in `/^there are no unexpected messages of priority "err" or higher in the journal$/'
features/sane_defaults.feature:25:in `Then there are no unexpected messages of priority "err" or higher in the journal'
After features/support/hooks.rb:330 4.972 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 06:11:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:11:31_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:11:31_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:11:31_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:11:31_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal
After features/support/hooks.rb:100 0.000
Feature: Shutdown buttons in the system menu
Tags: @product
26.195
Scenario I can shutdown Tails via the system menu
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.359
When I request a shutdown using the system menu 13.835
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/support/helpers/dogtail.rb:371:in `grabFocus'
./features/step_definitions/common_steps.rb:890:in `/^I request a (shutdown|reboot) using the system menu$/'
features/shutdown_applet.feature:6:in `When I request a shutdown using the system menu'
Then Tails eventually shuts down 0.000
After features/support/hooks.rb:330 5.421 
SCENARIO FAILED: 'I can shutdown Tails via the system menu' (at time 06:12:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:12:02_I_can_shutdown_Tails_via_the_system_menu.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:12:02_I_can_shutdown_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:12:02_I_can_shutdown_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:12:02_I_can_shutdown_Tails_via_the_system_menu.journal
After features/support/hooks.rb:100 0.000
Feature: Shutdown buttons in the system menu
Tags: @product @not_release_blocker
26.249
Scenario I can reboot Tails via the system menu
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.380
When I request a reboot using the system menu 13.869
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/support/helpers/dogtail.rb:371:in `grabFocus'
./features/step_definitions/common_steps.rb:890:in `/^I request a (shutdown|reboot) using the system menu$/'
features/shutdown_applet.feature:12:in `When I request a reboot using the system menu'
Then Tails eventually restarts 0.000
After features/support/hooks.rb:330 5.373 
SCENARIO FAILED: 'I can reboot Tails via the system menu' (at time 06:12:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:12:34_I_can_reboot_Tails_via_the_system_menu.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:12:34_I_can_reboot_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:12:34_I_can_reboot_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:12:34_I_can_reboot_Tails_via_the_system_menu.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product @doc
1:4.642
Scenario Starting the Unsafe Browser works as it should
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.198
When I successfully start the Unsafe Browser 18.156
Then the Unsafe Browser runs as the expected user 3.499
And the Unsafe Browser has a red theme 0.605
And the Unsafe Browser shows a warning as its start page 0.569
And the Unsafe Browser has no add-ons installed 10.353
And the Unsafe Browser has no bookmarks 17.812
And the Unsafe Browser uses all expected TBB shared libraries 1.446
The 
The loaded shared libraries for the firefox process are not the way we expect them.
Expected TBB libs that are absent: ["libfreeblpriv3.so", "libgkcodecs.so", "liblgpllibs.so", "libmozgtk.so", "libmozsandbox.so", "libmozsqlite3.so", "libmozwayland.so", "libnspr4.so", "libnss3.so", "libnssckbi.so", "libnssutil3.so", "libplc4.so", "libplds4.so", "libsmime3.so", "libsoftokn3.so", "libssl3.so", "libxul.so"]
Native libs that we don't want: [].
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/browser.rb:277:in `xul_app_shared_lib_check'
./features/step_definitions/browser.rb:291:in `/^the (.*) uses all expected TBB shared libraries$/'
features/unsafe_browser.feature:32:in `And the Unsafe Browser uses all expected TBB shared libraries'
After features/support/hooks.rb:330 6.487 
SCENARIO FAILED: 'Starting the Unsafe Browser works as it should' (at time 06:58:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:58:49_Starting_the_Unsafe_Browser_works_as_it_should.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:58:49_Starting_the_Unsafe_Browser_works_as_it_should.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:58:49_Starting_the_Unsafe_Browser_works_as_it_should.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/2/artifact/build-artifacts/06:58:49_Starting_the_Unsafe_Browser_works_as_it_should.journal
After features/support/hooks.rb:100 0.000