Project Number Date
test_Tails_ISO_test-suite-trixie-2 6 09 Jun 2025, 21:51

Failures Overview

The following summary displays scenarios that failed.

Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
17.785
Scenario Erasure of memory freed by killed userspace processes
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 8.733
And I prepare Tails for memory erasure tests 0.688
When I start a process allocating 128 MiB of memory with a known pattern 2.785
Then patterns cover at least 128 MiB in the guest's memory 5.578
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.528 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:38:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/00:38:42_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/6/artifact/build-artifacts/00:38:42_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/00:38:42_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/00:38:42_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
12:27.559
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.003
Before features/support/hooks.rb:513 0.005
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:47.904
And I update APT using apt 16.802
And I install "popularity-contest" using apt 26.503
Then I am proposed to add the "popularity-contest" package to my Additional Software 13.758
When I create a persistent storage and activate the Additional Software feature 26.349
Then Additional Software is correctly configured for package "popularity-contest" 3.901
When I shutdown Tails and wait for the computer to power off 15.601
And I start Tails from USB drive "__internal" with network unplugged 1:47.108
And I enable persistence 30.289
And I log in to a new session 1:1.852
And the Additional Software installation service has started 34.515
Then I am notified that the installation succeeded 5:2.971
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:612: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.038
After features/support/hooks.rb:330 10.357 
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:31:48)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/01:31:48_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/6/artifact/build-artifacts/01:31:48_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/6/artifact/build-artifacts/01:31:48_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.009
Feature: Additional software
Tags: @product @check_tor_leaks @slow
25:25.718
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.007
Before features/support/hooks.rb:513 0.002
Steps
Given a computer 0.687
And I start Tails from USB drive "__internal" and I login with an administration password 3:7.590
And I update APT using apt 11.879
When I install "makepp" using apt 22:5.560
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.041
After features/support/hooks.rb:330 5.123 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:57:25)
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/6/artifact/build-artifacts/01:57:25_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/6/artifact/build-artifacts/01:57:25_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/6/artifact/build-artifacts/01:57:25_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/6/artifact/build-artifacts/01:57:25_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/6/artifact/build-artifacts/01:57:25_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/6/artifact/build-artifacts/01:57:25_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/6/artifact/build-artifacts/01:57:25_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/6/artifact/build-artifacts/01:57:25_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.009
Feature: Additional software
Tags: @product @check_tor_leaks @slow
10:48.815
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.205
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 5:8.335
When I uninstall "popularity-contest" using apt 25.167
And I accept removing "popularity-contest" from Additional Software 2.748
Then "popularity-contest" is not in the list of Additional Software 0.802
When I start Synaptic 17.452
And I update APT using Synaptic 22.346
And I install "cowsay" using Synaptic 4:31.755
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.032
After features/support/hooks.rb:330 6.482 
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:08:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/02:08:19_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/6/artifact/build-artifacts/02:08:19_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/6/artifact/build-artifacts/02:08:19_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/6/artifact/build-artifacts/02:08:19_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/6/artifact/build-artifacts/02:08:19_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/6/artifact/build-artifacts/02:08:19_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/6/artifact/build-artifacts/02:08:19_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/6/artifact/build-artifacts/02:08:19_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/6/artifact/build-artifacts/02:08:19_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.006
Feature: Upgrading an old Tails USB installation
Tags: @product
3:37.419
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.166
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.083
When I start Tails from USB drive "old" with network unplugged 3:5.061
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:427:in `wait_for_ponytail'
./features/step_definitions/common_steps.rb:465: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.818 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:30:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/02:30:25_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/6/artifact/build-artifacts/02:30:25_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/6/artifact/build-artifacts/02:30:25_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/6/artifact/build-artifacts/02:30:25_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.006
Feature: Upgrading an old Tails USB installation
Tags: @product
2:32.486
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.002
Steps
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 2:32.310
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:427:in `wait_for_ponytail'
./features/step_definitions/common_steps.rb:465: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 5.938 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:33:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/02:33:03_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/6/artifact/build-artifacts/02:33:03_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/6/artifact/build-artifacts/02:33:03_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/6/artifact/build-artifacts/02:33:03_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product
2:27.019
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.003
Steps
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.845
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:427:in `wait_for_ponytail'
./features/step_definitions/common_steps.rb:465: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 5.860 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:35:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/02:35:36_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/6/artifact/build-artifacts/02:35:36_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/6/artifact/build-artifacts/02:35:36_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/6/artifact/build-artifacts/02:35:36_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.012
Feature: Upgrading an old Tails USB installation
Tags: @product
2:7.254
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.007
Steps
Given a computer 0.245
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.008
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 5.515 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:40:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/02:40:49_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/6/artifact/build-artifacts/02:40:49_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/6/artifact/build-artifacts/02:40:49_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/6/artifact/build-artifacts/02:40:49_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
22:56.135
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.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.312
And no SquashFS delta is installed 0.148
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.634
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.345
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.555
When the network is plugged 0.091
And Tor is ready 26.923
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:13.060
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.796 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:03:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/03:03:51_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/6/artifact/build-artifacts/03:03:51_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/03:03:51_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/6/artifact/build-artifacts/03:03:51_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:47.876
Scenario Upgrading a Tails whose signing key is outdated
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 12.714
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.447
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 22.618
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:11.884
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.780 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:26:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/03:26:44_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/6/artifact/build-artifacts/03:26:44_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/03:26:44_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/03:26:44_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000
Feature: Emergency shutdown
Tags: @product @not_release_blocker
2:28.591
Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD without network and logged in 9.209
And I prepare Tails for memory erasure tests 0.676
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 42.969
And I fill the USB drive with a known pattern 1.553
And I read the content of the test FS 0.082
And patterns cover at least 99% of the test FS size in the guest's memory 3.669 
Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)
When I eject the boot medium 0.392
And I wait for Tails to finish wiping the memory 1:30.039
cannot 
cannot find MemoryWipeCompleted.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/erase_memory.rb:232:in `/^I wait for Tails to finish wiping the memory$/'
features/emergency_shutdown.feature:44:in `And I wait for Tails to finish wiping the memory'
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:330 10.545 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 03:31:59)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/03:31:59_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/03:31:59_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/03:31:59_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.001
Feature: Backing up the persistent storage
Tags: @product
1:12.153
Scenario Using Tails' custom backup tool to backup a newly added file
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 14.273
# The volume cannot be in use when GuestFs clones it, which we do below
And I shutdown Tails and wait for the computer to power off 10.747
And I clone USB drive "__internal" to a temporary USB drive "backup" 1.824
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.423
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.145
When I start Tails' custom backup tool 5.379
Then the backup tool displays "Plug in your backup Tails USB stick" 0.304
When I plug USB drive "backup" 2.828
And I give the Persistent Storage on drive "backup" its own UUID 0.167
And I click "Retry" in the backup tool 1.335
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 1.377
When I click "Back Up" in the backup tool 1.174
And I enter my persistent storage passphrase into the polkit prompt 21.173
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:803:in `deal_with_polkit_prompt'
./features/step_definitions/backup.rb:18:in `/^I enter my persistent storage passphrase into the polkit prompt$/'
features/backup.feature:21:in `And I enter my persistent storage passphrase into the polkit prompt'
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 0.000
# The backup tool ejects the drive, so we have to replug it
When I unplug USB drive "backup" 0.000
And I plug USB drive "backup" 0.000
Then the USB drive "backup" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:330 9.401 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 03:37:33)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/03:37:33_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/03:37:33_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/03:37:33_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.158
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 4.881 
SCENARIO FAILED: 'Getting a DHCP lease with the default NetworkManager connection' (at time 03:38:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/03:38:36_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/6/artifact/build-artifacts/03:38:36_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.pcap
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/03:38:36_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/03:38:36_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/6/artifact/build-artifacts/03:38:36_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.044
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
0.901
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.317
And I switch to the "manually-added-con" NetworkManager connection 0.464
Then the hostname should not have been leaked on the network 0.120
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.208 
SCENARIO FAILED: 'Getting a DHCP lease with a manually configured NetworkManager connection' (at time 03:39:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/03:39:15_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/6/artifact/build-artifacts/03:39:15_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/6/artifact/build-artifacts/03:39:15_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/6/artifact/build-artifacts/03:39:15_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/6/artifact/build-artifacts/03:39:15_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.052
Feature: Tails documentation
Tags: @product @doc @not_release_blocker
47.770
Scenario The Tails documentation launcher works when offline
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD without network and logged in 8.472
When I start "Tails Documentation" via GNOME Activities Overview 9.585
Then the Tor Browser has started 29.712
cannot 
cannot find TorBrowserNewTabButton.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/browser.rb:500:in `/^the Tor Browser (?:has started|starts)$/'
features/documentation.feature:7:in `Then the Tor Browser has started'
Then "Tails - Documentation" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 9.625 
SCENARIO FAILED: 'The Tails documentation launcher works when offline' (at time 03:40:08)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/03:40:08_The_Tails_documentation_launcher_works_when_offline.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/03:40:08_The_Tails_documentation_launcher_works_when_offline.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/03:40:08_The_Tails_documentation_launcher_works_when_offline.journal
After features/support/hooks.rb:100 0.000
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
8.790
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.010
Steps
Given I have started Tails from DVD without network and logged in 8.699
Then the keys trusted by APT are valid for the next 3 months 0.091
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.344 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 04:15:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/04:15:16_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/6/artifact/build-artifacts/04:15:16_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/04:15:16_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/6/artifact/build-artifacts/04:15:16_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:23.556
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.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.432
When I log in to a new session in Chinese (zh_CN) 49.476
Then the keyboard layout is set to "cn" 0.156
When the network is plugged 0.070
And Tor is ready 21.437
Then I successfully start the Unsafe Browser 23.816
And I kill the Unsafe Browser 9.587
When I enable the screen keyboard 0.237
Then the screen keyboard works in Tor Browser 30.342
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'Firefox' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:1060:in `new'
./features/step_definitions/common_steps.rb:1060:in `block in launch_app'
./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/common_steps.rb:1059:in `launch_app'
./features/step_definitions/common_steps.rb:1114:in `launch_tor_browser'
./features/step_definitions/browser.rb:477:in `block in <top (required)>'
./features/step_definitions/browser.rb:443:in `block in <top (required)>' (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:1059:in `launch_app'
./features/step_definitions/common_steps.rb:1114:in `launch_tor_browser'
./features/step_definitions/browser.rb:477:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:443:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:44: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 10.868 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#2)' (at time 04:27:58)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/04:27:58_Tails_is_localized_for_every_tier-1_language,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/04:27:58_Tails_is_localized_for_every_tier-1_language,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/04:27:58_Tails_is_localized_for_every_tier-1_language,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:27.262
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.025
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.057
When I log in to a new session in French (fr) 49.752
Then the keyboard layout is set to "fr" 0.328
When the network is plugged 0.067
And Tor is ready 20.480
Then I successfully start the Unsafe Browser 18.215
And I kill the Unsafe Browser 7.714
When I enable the screen keyboard 0.265
Then the screen keyboard works in Tor Browser 42.380
cannot 
cannot find TorBrowserNewTabButton.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/browser.rb:500:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:487:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:443:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:46: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 "fr" 0.000
After features/support/hooks.rb:330 9.137 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#4)' (at time 04:33:54)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/04:33:54_Tails_is_localized_for_every_tier-1_language,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/04:33:54_Tails_is_localized_for_every_tier-1_language,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/04:33:54_Tails_is_localized_for_every_tier-1_language,_Examples___4_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:40.186
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.830
When I log in to a new session in German (de) 52.068
Then the keyboard layout is set to "de" 0.243
When the network is plugged 0.095
And Tor is ready 20.682
Then I successfully start the Unsafe Browser 1:19.265
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:47: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 "de" 0.000
After features/support/hooks.rb:330 6.871 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#5)' (at time 04:36:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/04:36:44_Tails_is_localized_for_every_tier-1_language,_Examples___5_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/04:36:44_Tails_is_localized_for_every_tier-1_language,_Examples___5_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/04:36:44_Tails_is_localized_for_every_tier-1_language,_Examples___5_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/04:36:44_Tails_is_localized_for_every_tier-1_language,_Examples___5_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:7.272
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 8.134
When I log in to a new session in Spanish (es) 49.322
Then the keyboard layout is set to "es" 0.163
When the network is plugged 0.083
And Tor is ready 49.854
Then I successfully start the Unsafe Browser 1:19.714
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:54: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 9.366 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#12)' (at time 04:59:35)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/04:59:35_Tails_is_localized_for_every_tier-1_language,_Examples___12_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/04:59:35_Tails_is_localized_for_every_tier-1_language,_Examples___12_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/04:59:35_Tails_is_localized_for_every_tier-1_language,_Examples___12_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:30.983
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.002
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.139
When I log in to a new session in Turkish (tr) 50.022
Then the keyboard layout is set to "tr" 0.260
When the network is plugged 0.078
And Tor is ready 20.324
Then I successfully start the Unsafe Browser 16.927
And I kill the Unsafe Browser 7.817
When I enable the screen keyboard 0.194
Then the screen keyboard works in Tor Browser 47.218
cannot 
cannot find TorBrowserNewTabButton.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/browser.rb:500:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:487:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:443:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:55: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 8.906 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#13)' (at time 05:02:15)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/05:02:15_Tails_is_localized_for_every_tier-1_language,_Examples___13_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/05:02:15_Tails_is_localized_for_every_tier-1_language,_Examples___13_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/05:02:15_Tails_is_localized_for_every_tier-1_language,_Examples___13_.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
9.774
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.681
Then there are no unexpected messages of priority "err" or higher in the journal 0.092
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": "575",
    "_BOOT_ID": "e5640490acb4409580a15178a5b9356d",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "575",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749479826310390",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "5eea3717480b4b96baf3abe5a503259d",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=2e5369820f2a44c28fd546d9af4f3f48;i=375;b=e5640490acb4409580a15178a5b9356d;m=d67795;t=637248396ccf5;x=e9535684d890b54c",
    "__MONOTONIC_TIMESTAMP": "14055317",
    "__REALTIME_TIMESTAMP": "1749479826312437",
    "__SEQNUM": "885",
    "__SEQNUM_ID": "2e5369820f2a44c28fd546d9af4f3f48"
  },
  {
    "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": "575",
    "_BOOT_ID": "e5640490acb4409580a15178a5b9356d",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "575",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749479826310419",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "5eea3717480b4b96baf3abe5a503259d",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=2e5369820f2a44c28fd546d9af4f3f48;i=377;b=e5640490acb4409580a15178a5b9356d;m=d67907;t=637248396ce67;x=6d95d663d7a63fd1",
    "__MONOTONIC_TIMESTAMP": "14055687",
    "__REALTIME_TIMESTAMP": "1749479826312807",
    "__SEQNUM": "887",
    "__SEQNUM_ID": "2e5369820f2a44c28fd546d9af4f3f48"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2161",
    "SYSLOG_TIMESTAMP": "Jun  9 14:37:14 ",
    "_BOOT_ID": "e5640490acb4409580a15178a5b9356d",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2161",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749479834361619",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "4bf1032dc9a64731b3d1ace925f7b41b",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=2e5369820f2a44c28fd546d9af4f3f48;i=3f7;b=e5640490acb4409580a15178a5b9356d;m=15149c4;t=6372484119f23;x=ca7b850290b015f1",
    "__MONOTONIC_TIMESTAMP": "22104516",
    "__REALTIME_TIMESTAMP": "1749479834361635",
    "__SEQNUM": "1015",
    "__SEQNUM_ID": "2e5369820f2a44c28fd546d9af4f3f48"
  },
  {
    "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": "575",
    "_BOOT_ID": "e5640490acb4409580a15178a5b9356d",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "575",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749480015708249",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "5eea3717480b4b96baf3abe5a503259d",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=2e5369820f2a44c28fd546d9af4f3f48;i=8a3;b=e5640490acb4409580a15178a5b9356d;m=625a56e;t=637248ee0c062;x=44a60f448e02cb50",
    "__MONOTONIC_TIMESTAMP": "103130478",
    "__REALTIME_TIMESTAMP": "1749480015708258",
    "__SEQNUM": "2211",
    "__SEQNUM_ID": "2e5369820f2a44c28fd546d9af4f3f48"
  },
  {
    "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": "575",
    "_BOOT_ID": "e5640490acb4409580a15178a5b9356d",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "575",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749480015708592",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "5eea3717480b4b96baf3abe5a503259d",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=2e5369820f2a44c28fd546d9af4f3f48;i=8a5;b=e5640490acb4409580a15178a5b9356d;m=625a6c0;t=637248ee0c1b4;x=81fb5fee7c4e63d9",
    "__MONOTONIC_TIMESTAMP": "103130816",
    "__REALTIME_TIMESTAMP": "1749480015708596",
    "__SEQNUM": "2213",
    "__SEQNUM_ID": "2e5369820f2a44c28fd546d9af4f3f48"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "7719",
    "SYSLOG_TIMESTAMP": "Jun  9 14:40:21 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "e5640490acb4409580a15178a5b9356d",
    "_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": "7719",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749480021148487",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "c5e13709b64f43d5a3139d8382e818f5",
    "_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=2e5369820f2a44c28fd546d9af4f3f48;i=1235;b=e5640490acb4409580a15178a5b9356d;m=678a873;t=637248f33c365;x=3d122331022f984c",
    "__MONOTONIC_TIMESTAMP": "108570739",
    "__REALTIME_TIMESTAMP": "1749480021148517",
    "__SEQNUM": "4661",
    "__SEQNUM_ID": "2e5369820f2a44c28fd546d9af4f3f48"
  }
].
<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.296 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from DVD' (at time 06:21:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/06:21:23_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/6/artifact/build-artifacts/06:21:23_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/6/artifact/build-artifacts/06:21:23_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/6/artifact/build-artifacts/06:21:23_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
13.507
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.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.839
Then there are no unexpected messages of priority "err" or higher in the journal 0.667
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": "713",
    "_BOOT_ID": "318b8be01e64483cbf479d78a77fb923",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "713",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749482097348652",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "f672437eab8444f9b428236bbe0de8e2",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=6daa5ba8d4664a7693c7f390e6c6b6bf;i=38e;b=318b8be01e64483cbf479d78a77fb923;m=10b75b2;t=637250af4103d;x=76d26458f3be41d7",
    "__MONOTONIC_TIMESTAMP": "17528242",
    "__REALTIME_TIMESTAMP": "1749482097348669",
    "__SEQNUM": "910",
    "__SEQNUM_ID": "6daa5ba8d4664a7693c7f390e6c6b6bf"
  },
  {
    "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": "713",
    "_BOOT_ID": "318b8be01e64483cbf479d78a77fb923",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "713",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749482097349018",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "f672437eab8444f9b428236bbe0de8e2",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=6daa5ba8d4664a7693c7f390e6c6b6bf;i=390;b=318b8be01e64483cbf479d78a77fb923;m=10b7713;t=637250af4119e;x=8047f55e5ae42bd2",
    "__MONOTONIC_TIMESTAMP": "17528595",
    "__REALTIME_TIMESTAMP": "1749482097349022",
    "__SEQNUM": "912",
    "__SEQNUM_ID": "6daa5ba8d4664a7693c7f390e6c6b6bf"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2560",
    "SYSLOG_TIMESTAMP": "Jun  9 15:15:04 ",
    "_BOOT_ID": "318b8be01e64483cbf479d78a77fb923",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2560",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749482104933893",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "67fba5c789ea401882559bc1166f3655",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=6daa5ba8d4664a7693c7f390e6c6b6bf;i=415;b=318b8be01e64483cbf479d78a77fb923;m=17f33a2;t=637250b67ce2d;x=9ed3375bae095885",
    "__MONOTONIC_TIMESTAMP": "25113506",
    "__REALTIME_TIMESTAMP": "1749482104933933",
    "__SEQNUM": "1045",
    "__SEQNUM_ID": "6daa5ba8d4664a7693c7f390e6c6b6bf"
  },
  {
    "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": "713",
    "_BOOT_ID": "318b8be01e64483cbf479d78a77fb923",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "713",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749482246258256",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "f672437eab8444f9b428236bbe0de8e2",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=6daa5ba8d4664a7693c7f390e6c6b6bf;i=e92;b=318b8be01e64483cbf479d78a77fb923;m=9b0337e;t=6372513d43e68;x=801a711b0d66bee9",
    "__MONOTONIC_TIMESTAMP": "162542462",
    "__REALTIME_TIMESTAMP": "1749482246258280",
    "__SEQNUM": "3730",
    "__SEQNUM_ID": "6daa5ba8d4664a7693c7f390e6c6b6bf"
  },
  {
    "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": "713",
    "_BOOT_ID": "318b8be01e64483cbf479d78a77fb923",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "713",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749482246258659",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "f672437eab8444f9b428236bbe0de8e2",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=6daa5ba8d4664a7693c7f390e6c6b6bf;i=e94;b=318b8be01e64483cbf479d78a77fb923;m=9b039f4;t=6372513d444df;x=ce10e843a4b3c2d3",
    "__MONOTONIC_TIMESTAMP": "162544116",
    "__REALTIME_TIMESTAMP": "1749482246259935",
    "__SEQNUM": "3732",
    "__SEQNUM_ID": "6daa5ba8d4664a7693c7f390e6c6b6bf"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "12236",
    "SYSLOG_TIMESTAMP": "Jun  9 15:17:34 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "5",
    "_BOOT_ID": "318b8be01e64483cbf479d78a77fb923",
    "_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": "12236",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749482254335713",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-5.scope",
    "_SYSTEMD_INVOCATION_ID": "e1db8fc3f37143dead1dc8276acaf0f1",
    "_SYSTEMD_OWNER_UID": "1000",
    "_SYSTEMD_SESSION": "5",
    "_SYSTEMD_SLICE": "user-1000.slice",
    "_SYSTEMD_UNIT": "session-5.scope",
    "_SYSTEMD_USER_SLICE": "-.slice",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=6daa5ba8d4664a7693c7f390e6c6b6bf;i=188d;b=318b8be01e64483cbf479d78a77fb923;m=a2b743b;t=63725144f7f26;x=9cda1b664e2879e5",
    "__MONOTONIC_TIMESTAMP": "170619963",
    "__REALTIME_TIMESTAMP": "1749482254335782",
    "__SEQNUM": "6285",
    "__SEQNUM_ID": "6daa5ba8d4664a7693c7f390e6c6b6bf"
  }
].
<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 5.764 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 06:21:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/06:21:42_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/6/artifact/build-artifacts/06:21:42_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/6/artifact/build-artifacts/06:21:42_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/6/artifact/build-artifacts/06:21:42_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:26.673
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD without network and logged in 8.575
Then the live user's Videos directory exists 0.090
And there is a GNOME bookmark for the Videos directory 18.874
Then I start the Tor Browser in offline mode 25.873
And I can save the current page as "index.html" to the Videos GNOME bookmark 33.259
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:8:in `new'
./features/step_definitions/browser.rb:8:in `block in desktop_portal_save_as'
./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/browser.rb:7:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:52:in `browser_save_page_as'
./features/step_definitions/browser.rb:564:in `block in <top (required)>' (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:7:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:52:in `browser_save_page_as'
./features/step_definitions/browser.rb:564:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:131:in `And I can save the current page as "index.html" to the Videos GNOME bookmark'
features/torified_browsing.feature:124:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'
After features/support/hooks.rb:330 8.656 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#5)' (at time 06:58:45)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/06:58:45_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/06:58:45_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/06:58:45_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/06:58:45_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product @not_release_blocker
1:16.068
Scenario Starting a second instance of the Unsafe Browser results in an error message being shown
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 16.319
When I successfully start the Unsafe Browser 19.207
# Wait for whatever facility the GNOME Activities Overview uses to
# learn about which applications are running to "settle". Without
# this sleep, it is confused and it's impossible to start a new
# instance (it will just switch to the one we already started).
And I wait 10 seconds 10.008 
Slept for 10 seconds
And I try to start the Unsafe Browser 0.529
Then I see a warning about another instance already running 30.004
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'zenity' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/unsafe_browser.rb:76:in `new'
./features/step_definitions/unsafe_browser.rb:76:in `block (2 levels) in <top (required)>'
./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/unsafe_browser.rb:75:in `block in <top (required)>' (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/unsafe_browser.rb:75:in `/^I see a warning about another instance already running$/'
features/unsafe_browser.feature:59:in `Then I see a warning about another instance already running'
After features/support/hooks.rb:330 10.252 
SCENARIO FAILED: 'Starting a second instance of the Unsafe Browser results in an error message being shown' (at time 07:12:52)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/07:12:52_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/07:12:52_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-trixie-2/6/artifact/build-artifacts/07:12:52_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.journal
After features/support/hooks.rb:100 0.000