Project Number Date
test_Tails_ISO_feature-trixie 8 30 May 2025, 06:48

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
22.300
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 6.938
And I wait until Tor is ready 3.477
When I disconnect the network through GNOME 11.883
The 
The Dogtail init script raised: SearchError: descendant of [panel | ]: '' 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:272:in `button'
./features/step_definitions/common_steps.rb:202:in `expand_gnome_shell_menu_section'
./features/step_definitions/common_steps.rb:211:in `/^I (dis)?connect the network through GNOME$/'
features/tor_bridges.feature:85:in `When I disconnect the network through GNOME'
And I connect the network through GNOME 0.000
Then the Tor Connection Assistant autostarts 0.000
And the Tor Connection Assistant connects to Tor 0.000
And I wait until Tor is ready 0.000
And Tor is using the same configuration as before 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 5.342 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:35:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/00:35:34_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/00:35:34_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/00:35:34_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/00:35:34_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.031
Feature: Using Tor bridges and pluggable transports
Tags: @product
51.605
Scenario Reconnecting from an unblocked network to a blocked network displays an error
Steps
Given I configure a direct connection in the Tor Connection Assistant 7.505
And I wait until Tor is ready 32.126
And I disconnect the network through GNOME 11.973
The 
The Dogtail init script raised: SearchError: descendant of [panel | ]: '' 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:272:in `button'
./features/step_definitions/common_steps.rb:202:in `expand_gnome_shell_menu_section'
./features/step_definitions/common_steps.rb:211:in `/^I (dis)?connect the network through GNOME$/'
features/tor_bridges.feature:97:in `And I disconnect the network through GNOME'
And the Tor network and default bridges are blocked 0.000
When I connect the network through GNOME 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
After features/support/hooks.rb:330 5.218 
SCENARIO FAILED: 'Reconnecting from an unblocked network to a blocked network displays an error' (at time 00:36:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/00:36:47_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/00:36:47_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/00:36:47_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/00:36:47_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.journal
After features/support/hooks.rb:100 0.046
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
15.961
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.491
And I prepare Tails for memory erasure tests 0.880
When I start a process allocating 128 MiB of memory with a known pattern 1.249
Then patterns cover at least 128 MiB in the guest's memory 4.340
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.536 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:38:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/00:38:32_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/00:38:32_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/00:38:32_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/00:38:32_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 @not_release_blocker @fragile @doc
6:55.158
Scenario I am warned I can not use Additional Software when I start Tails from a DVD and install 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.005
Steps
Given I have started Tails from DVD and logged in with an administration password and the network is connected 2:31.463
And I update APT using apt 13.021
When I install "popularity-contest" using apt 26.828
Then I am notified I can not use Additional Software for "popularity-contest" 14.389
And I can open the Additional Software documentation from the notification 3:29.455
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/browser.rb:204:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:219:in `/^"([^"]+)" has loaded in the Tor Browser$/'
./features/step_definitions/additional_software_packages.rb:145:in `/^I can open the Additional Software documentation from the notification$/'
features/additional_software_packages.feature:19:in `And I can open the Additional Software documentation from the notification'
After features/support/hooks.rb:521 0.045
After features/support/hooks.rb:330 8.670 
SCENARIO FAILED: 'I am warned I can not use Additional Software when I start Tails from a DVD and install a package' (at time 01:21:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/01:21:52_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_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_feature-trixie/8/artifact/build-artifacts/01:21:52_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_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_feature-trixie/8/artifact/build-artifacts/01:21:52_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_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_feature-trixie/8/artifact/build-artifacts/01:21:52_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_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_feature-trixie/8/artifact/build-artifacts/01:21:52_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/01:21:52_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/01:21:52_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/01:21:52_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/01:21:52_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.journal
After features/support/hooks.rb:100 0.003
Feature: Additional software
Tags: @product @check_tor_leaks @slow
12:7.476
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.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:53.917
And I update APT using apt 11.309
And I install "popularity-contest" using apt 26.789
Then I am proposed to add the "popularity-contest" package to my Additional Software 12.959
When I create a persistent storage and activate the Additional Software feature 25.486
Then Additional Software is correctly configured for package "popularity-contest" 2.698
When I shutdown Tails and wait for the computer to power off 15.520
And I start Tails from USB drive "__internal" with network unplugged 1:52.929
And I enable persistence 25.140
And I log in to a new session 32.819
And the Additional Software installation service has started 45.962
Then I am notified that the installation succeeded 5:1.942
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:604: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.045
After features/support/hooks.rb:330 6.291 
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:34:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/01:34:08_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_feature-trixie/8/artifact/build-artifacts/01:34:08_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_feature-trixie/8/artifact/build-artifacts/01:34:08_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_feature-trixie/8/artifact/build-artifacts/01:34:08_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_feature-trixie/8/artifact/build-artifacts/01:34:08_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_feature-trixie/8/artifact/build-artifacts/01:34:08_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_feature-trixie/8/artifact/build-artifacts/01:34:08_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_feature-trixie/8/artifact/build-artifacts/01:34:08_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_feature-trixie/8/artifact/build-artifacts/01:34:08_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:15.118
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.002
Before features/support/hooks.rb:513 0.002
Steps
Given a computer 0.190
And I start Tails from USB drive "__internal" and I login with an administration password 2:57.901
And I update APT using apt 11.982
When I install "makepp" using apt 22:5.043
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.033
After features/support/hooks.rb:330 5.433 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:59:30)
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_feature-trixie/8/artifact/build-artifacts/01:59:30_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_feature-trixie/8/artifact/build-artifacts/01:59:30_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_feature-trixie/8/artifact/build-artifacts/01:59:30_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_feature-trixie/8/artifact/build-artifacts/01:59:30_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_feature-trixie/8/artifact/build-artifacts/01:59:30_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_feature-trixie/8/artifact/build-artifacts/01:59:30_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_feature-trixie/8/artifact/build-artifacts/01:59:30_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_feature-trixie/8/artifact/build-artifacts/01:59:30_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
5:27.139
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.002
Before features/support/hooks.rb:513 0.003
Steps
Given a computer 0.169
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 4:34.907
When I uninstall "popularity-contest" using apt 25.015
And I accept removing "popularity-contest" from Additional Software 0.795
Then "popularity-contest" is not in the list of Additional Software 1.127
When I start Synaptic 25.123
The 
The Dogtail init script raised: SearchError: child of [application | synaptic]: child with name='Synaptic Package Manager ' roleName='frame'
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/apt.rb:146:in `/^I start Synaptic$/'
features/additional_software_packages.feature:59:in `When I start Synaptic'
And I update APT using Synaptic 0.000
And I install "cowsay" using Synaptic 0.000
And I accept adding "cowsay" to Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I uninstall "cowsay" using apt 0.000
And I refuse removing "cowsay" from Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I remove "cowsay" from the list of Additional Software using Additional Software GUI 0.000
Then "cowsay" is not in the list of Additional Software 0.000
When I install "cowsay" using apt 0.000
And I refuse adding "cowsay" to Additional Software 0.000
Then "cowsay" is not in the list of Additional Software 0.000
After features/support/hooks.rb:521 0.041
After features/support/hooks.rb:330 5.693 
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:05:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:05:03_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_feature-trixie/8/artifact/build-artifacts/02:05:03_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_feature-trixie/8/artifact/build-artifacts/02:05:03_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_feature-trixie/8/artifact/build-artifacts/02:05:03_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_feature-trixie/8/artifact/build-artifacts/02:05:03_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_feature-trixie/8/artifact/build-artifacts/02:05:03_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_feature-trixie/8/artifact/build-artifacts/02:05:03_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_feature-trixie/8/artifact/build-artifacts/02:05:03_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_feature-trixie/8/artifact/build-artifacts/02:05:03_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.022
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
13:38.452
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:513 0.001
Steps
Given a computer 0.159
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 4:1.528
And I configure APT to prefer an old version of cowsay 0.028
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 28.790
And I accept adding "cowsay" to Additional Software 7.809
And Additional Software is correctly configured for package "cowsay" 1.710
And I shutdown Tails and wait for the computer to power off 11.162
And I start Tails from USB drive "__internal" with network unplugged 1:51.922
And I enable persistence 17.749
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.026
# 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.087
And I log in to a new session 39.960
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 46.157
And I revert the APT tweaks that made it prefer an old version of cowsay 0.075
# We remove the newest package after it has been downloaded and before
# it is installed, so that the upgrade process fails
And I prepare the Additional Software upgrade process to fail 0.073
And the network is plugged 0.065
And Tor is ready 25.443
And available upgrades have been checked 0.058
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 2.828
And I can open the Additional Software configuration window from the notification 2.215
And I shutdown Tails and wait for the computer to power off 19.719
And I start Tails from USB drive "__internal" with network unplugged 1:51.342
And I enable persistence 14.562
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.030
And I log in to a new session 58.880
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 1:1.610
And I revert the APT tweaks that made it prefer an old version of cowsay 0.066
And the network is plugged 0.089
And Tor is ready 14.295
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:826:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:658:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:612:in `/^Tor is ready$/'
features/additional_software_packages.feature:114:in `And Tor is ready'
Then the Additional Software upgrade service has started 0.000
And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000
After features/support/hooks.rb:521 0.029
After features/support/hooks.rb:330 5.260 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 02:18:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:18:47_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:18:47_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:18:47_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:18:47_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:18:47_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:18:47_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:18:47_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:18:47_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:18:47_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal
After features/support/hooks.rb:100 0.019
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
3:39.599
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.002
Before features/support/hooks.rb:513 0.002
Steps
Given a computer 0.172
And I start Tails from USB drive "__internal" with network unplugged 1:48.996
And I enable persistence 17.868
And I remove the "cowsay" deb files from the APT cache 0.078
# 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.089
And I log in to a new session 40.244
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 14.785
And I can open the Additional Software log file from the notification 37.363
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: 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:41:in `click_gnome_shell_notification_button'
./features/step_definitions/additional_software_packages.rb:169: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.049
After features/support/hooks.rb:330 6.414 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 02:22:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:22:32_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_feature-trixie/8/artifact/build-artifacts/02:22:32_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_feature-trixie/8/artifact/build-artifacts/02:22:32_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_feature-trixie/8/artifact/build-artifacts/02:22:32_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_feature-trixie/8/artifact/build-artifacts/02:22:32_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_feature-trixie/8/artifact/build-artifacts/02:22:32_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:22:32_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:22:32_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:22:32_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product
2:20.930
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.004
Steps
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 30.356
When I start Tails from USB drive "old" with network unplugged 1:49.263
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:461:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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 6.622 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:24:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:24:59_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_feature-trixie/8/artifact/build-artifacts/02:24:59_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:24:59_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:24:59_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.012
Feature: Upgrading an old Tails USB installation
Tags: @product
1:28.680
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.011
Steps
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:28.497
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:461:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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.922 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:26:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:26:35_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_feature-trixie/8/artifact/build-artifacts/02:26:35_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:26:35_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:26:35_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.006
Feature: Upgrading an old Tails USB installation
Tags: @product
1:19.011
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.002
Steps
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:18.834
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:461:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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.791 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:28:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:28:00_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_feature-trixie/8/artifact/build-artifacts/02:28:00_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_feature-trixie/8/artifact/build-artifacts/02:28:00_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_feature-trixie/8/artifact/build-artifacts/02:28:00_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.006
Feature: Upgrading an old Tails USB installation
Tags: @product
2:5.668
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.003
Steps
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.496
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:291: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.036 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:33:01)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:33:01_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_feature-trixie/8/artifact/build-artifacts/02:33:01_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:33:01_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:33:01_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.006
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
22:48.216
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 13.476
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.753
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.286
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.299
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.780
When the network is plugged 0.067
And Tor is ready 21.001
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:11.434
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.514 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:55:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:55:55_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_feature-trixie/8/artifact/build-artifacts/02:55:55_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:55:55_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/02:55:55_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:41.301
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 10.585
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 17.801
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:12.373
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.948 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:18:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:18:42_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:18:42_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:18:42_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:18:42_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:3.986
Scenario Tails erases memory on DVD boot medium removal: overlayfs read-write branch
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.887
And I prepare Tails for memory erasure tests 0.542
And I fill a 128 MiB file with a known pattern on the root filesystem 20.869
And patterns cover at least 128 MiB in the guest's memory 3.324 
Pattern coverage: 100.000% (128 MiB out of 128 MiB reference memory)
When I eject the boot medium 0.346
And I wait for Tails to finish wiping the memory 1:30.016
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:22: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.549 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: overlayfs read-write branch' (at time 03:21:49)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:21:49_Tails_erases_memory_on_DVD_boot_medium_removal:_overlayfs_read-write_branch.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:21:49_Tails_erases_memory_on_DVD_boot_medium_removal:_overlayfs_read-write_branch.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:21:49_Tails_erases_memory_on_DVD_boot_medium_removal:_overlayfs_read-write_branch.journal
After features/support/hooks.rb:100 0.000
Feature: Emergency shutdown
Tags: @product @not_release_blocker
1:54.808
Scenario Tails erases memory on DVD boot medium removal: vfat
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.720
And I prepare Tails for memory erasure tests 0.594
And I plug and mount a 128 MiB USB drive with a vfat filesystem 10.112
And I fill the USB drive with a known pattern 1.748
And I read the content of the test FS 0.070
And patterns cover at least 90% of the test FS size in the guest's memory 3.104 
Pattern coverage: 100.000% (127 MiB out of 127 MiB reference memory)
When I eject the boot medium 0.330
And I wait for Tails to finish wiping the memory 1:30.126
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:33: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.516 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: vfat' (at time 03:23:54)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:23:54_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:23:54_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:23:54_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.journal
After features/support/hooks.rb:100 0.000
Feature: Emergency shutdown
Tags: @product @not_release_blocker
2:22.146
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.003
Steps
Given I have started Tails from DVD without network and logged in 8.858
And I prepare Tails for memory erasure tests 0.627
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 38.063
And I fill the USB drive with a known pattern 1.618
And I read the content of the test FS 0.160
And patterns cover at least 99% of the test FS size in the guest's memory 2.493 
Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)
When I eject the boot medium 0.311
And I wait for Tails to finish wiping the memory 1:30.014
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.572 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 03:26:27)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:26:27_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:26:27_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:26:27_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.001
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
0.107
Scenario Getting a DHCP lease with the default NetworkManager connection
Steps
Then the hostname should not have been leaked on the network 0.107
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.040 
SCENARIO FAILED: 'Getting a DHCP lease with the default NetworkManager connection' (at time 03:32:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:32:58_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_feature-trixie/8/artifact/build-artifacts/03:32:58_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.pcap
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:32:58_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:32:58_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:32:58_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.038
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
0.829
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.220
And I switch to the "manually-added-con" NetworkManager connection 0.489
Then the hostname should not have been leaked on the network 0.118
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 4.897 
SCENARIO FAILED: 'Getting a DHCP lease with a manually configured NetworkManager connection' (at time 03:33:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:33:35_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_feature-trixie/8/artifact/build-artifacts/03:33:35_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.pcap
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:33:35_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:33:35_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:33:35_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.038
Feature: Tails documentation
Tags: @product @doc @not_release_blocker
52.383
Scenario The Tails documentation launcher works when offline
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.770
When I start "Tails Documentation" via GNOME Activities Overview 10.541
Then the Tor Browser has started 33.072
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:468: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 8.564 
SCENARIO FAILED: 'The Tails documentation launcher works when offline' (at time 03:34:32)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:34:32_The_Tails_documentation_launcher_works_when_offline.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:34:32_The_Tails_documentation_launcher_works_when_offline.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:34:32_The_Tails_documentation_launcher_works_when_offline.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product
3:34.485
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 47.231
And I corrupt the boot device's GPT backup header 0.661
And I power off the computer 0.537
When I start the computer 1.036
Then the computer boots Tails 2:4.820
When I log in to a new session 30.079
And all notifications have disappeared 9.759
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.358
<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.933 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 03:51:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:51:48_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_feature-trixie/8/artifact/build-artifacts/03:51:48_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:51:48_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:51:48_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:100 0.006
Feature: Hardware failures
Tags: @product
3:2.151
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 20.812
And I corrupt the boot device's GPT backup partition table 0.424
And I power off the computer 0.340
When I start the computer 1.077
Then the computer boots Tails 2:1.705
When I log in to a new session 26.406
And all notifications have disappeared 11.101
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.284
<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.181 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 03:54:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:54:57_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_feature-trixie/8/artifact/build-artifacts/03:54:57_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:54:57_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:54:57_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:100 0.006
Feature: Hardware failures
Tags: @product
4:23.146
Scenario GPT backup corruption without a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.215
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.061
And I plug USB drive "temp" 1.058
And I write the Tails USB image to disk "temp" 1:7.672
When I start Tails from USB drive "temp" with network unplugged 2:33.915
Then Tails is running from USB drive "temp" 0.413
And the Greeter forbids creating a persistent partition 0.091
When I log in to a new session 24.799
And all notifications have disappeared 14.581
Then I am recommended to reinstall Tails due to partitioning errors 0.335
<"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.861 
SCENARIO FAILED: 'GPT backup corruption without a persistent partition' (at time 03:59:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:59:27_GPT_backup_corruption_without_a_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:59:27_GPT_backup_corruption_without_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:59:27_GPT_backup_corruption_without_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/03:59:27_GPT_backup_corruption_without_a_persistent_partition.journal
After features/support/hooks.rb:100 0.109
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
9.179
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.023
Steps
Given I have started Tails from DVD without network and logged in 8.960
Then the keys trusted by APT are valid for the next 3 months 0.218
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.490 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 04:10:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:10:26_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_feature-trixie/8/artifact/build-artifacts/04:10:26_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:10:26_The_included_APT_repository_keys_are_up-to-date.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:10:26_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product
1:39.759
Scenario Outline Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255)
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 13.260
And I log in to a new session in German (de) 47.149
Then the live user's Documents directory exists 0.153
And there is a GNOME bookmark for the Documents directory 39.194
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Documents' roleName='label'
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:1225:in `/^there is a GNOME bookmark for the (.*) directory$/'
features/localization.feature:14:in `And there is a GNOME bookmark for the Documents directory'
features/localization.feature:11:in `And there is a GNOME bookmark for the <dir> directory'
After features/support/hooks.rb:330 5.988 
SCENARIO FAILED: 'Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255), Examples (#1)' (at time 04:12:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:12:12_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:12:12_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:12:12_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:12:12_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product
1:34.725
Scenario Outline Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255)
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.950
And I log in to a new session in German (de) 46.551
Then the live user's Downloads directory exists 0.200
And there is a GNOME bookmark for the Downloads directory 40.023
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Downloads' roleName='label'
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:1225:in `/^there is a GNOME bookmark for the (.*) directory$/'
features/localization.feature:15:in `And there is a GNOME bookmark for the Downloads directory'
features/localization.feature:11:in `And there is a GNOME bookmark for the <dir> directory'
After features/support/hooks.rb:330 5.726 
SCENARIO FAILED: 'Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255), Examples (#2)' (at time 04:13:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:13:52_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:13:52_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:13:52_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:13:52_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product
1:32.026
Scenario Outline Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255)
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.671
And I log in to a new session in German (de) 46.164
Then the live user's Pictures directory exists 0.133
And there is a GNOME bookmark for the Pictures directory 38.057
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Pictures' roleName='label'
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:1225:in `/^there is a GNOME bookmark for the (.*) directory$/'
features/localization.feature:17:in `And there is a GNOME bookmark for the Pictures directory'
features/localization.feature:11:in `And there is a GNOME bookmark for the <dir> directory'
After features/support/hooks.rb:330 5.609 
SCENARIO FAILED: 'Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255), Examples (#4)' (at time 04:16:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:16:39_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___4_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:16:39_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:16:39_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:16:39_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___4_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product
1:30.953
Scenario Outline Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255)
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 7.839
And I log in to a new session in German (de) 45.009
Then the live user's Videos directory exists 0.095
And there is a GNOME bookmark for the Videos directory 38.009
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Videos' roleName='label'
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:1225:in `/^there is a GNOME bookmark for the (.*) directory$/'
features/localization.feature:18:in `And there is a GNOME bookmark for the Videos directory'
features/localization.feature:11:in `And there is a GNOME bookmark for the <dir> directory'
After features/support/hooks.rb:330 5.739 
SCENARIO FAILED: 'Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255), Examples (#5)' (at time 04:18:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:18:16_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___5_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:18:16_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___5_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:18:16_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___5_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:18:16_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___5_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:28.113
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.128
When I log in to a new session in Arabic (ar) 3:19.984
cannot 
cannot find GnomeApplicationsMenuArabic.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/common_steps.rb:571:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:524:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/localization.feature:44:in `When I log in to a new session in Arabic (ar)'
features/localization.feature:23:in `When I log in to a new session in <language> (<lang_code>)'
Then the keyboard layout is set to "us" 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I successfully start the Unsafe Browser 0.000
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 6.190 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#1)' (at time 04:21:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:21:50_Tails_is_localized_for_every_tier-1_language,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:21:50_Tails_is_localized_for_every_tier-1_language,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:21:50_Tails_is_localized_for_every_tier-1_language,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:21:50_Tails_is_localized_for_every_tier-1_language,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:28.816
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.750
When I log in to a new session in Chinese (zh_CN) 3:20.065
cannot 
cannot find GnomeApplicationsMenuChinese.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/common_steps.rb:571:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:524:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/localization.feature:45:in `When I log in to a new session in Chinese (zh_CN)'
features/localization.feature:23:in `When I log in to a new session in <language> (<lang_code>)'
Then the keyboard layout is set to "cn" 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I successfully start the Unsafe Browser 0.000
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 6.362 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#2)' (at time 04:25:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:25:25_Tails_is_localized_for_every_tier-1_language,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:25:25_Tails_is_localized_for_every_tier-1_language,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:25:25_Tails_is_localized_for_every_tier-1_language,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:25:25_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:19.067
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.997
When I log in to a new session in English (en) 35.461
Then the keyboard layout is set to "us" 0.464
When the network is plugged 0.105
And Tor is ready 19.582
Then I successfully start the Unsafe Browser 15.806
And I kill the Unsafe Browser 7.702
When I enable the screen keyboard 0.278
Then the screen keyboard works in Tor Browser 51.668
cannot 
cannot find ScreenKeyboard.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:417: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 "us" 0.000
After features/support/hooks.rb:330 6.530 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#3)' (at time 04:27:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:27:50_Tails_is_localized_for_every_tier-1_language,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:27:50_Tails_is_localized_for_every_tier-1_language,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:27:50_Tails_is_localized_for_every_tier-1_language,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:27:50_Tails_is_localized_for_every_tier-1_language,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:0.481
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.749
When I log in to a new session in French (fr) 46.349
Then the keyboard layout is set to "fr" 0.437
When the network is plugged 0.097
And Tor is ready 22.774
Then I successfully start the Unsafe Browser 32.779
And I kill the Unsafe Browser 8.329
When I enable the screen keyboard 0.875
Then the screen keyboard works in Tor Browser 1:1.089
cannot 
cannot find ScreenKeyboard.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:417:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:47: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 5.909 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#4)' (at time 04:30:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:30:57_Tails_is_localized_for_every_tier-1_language,_Examples___4_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:30:57_Tails_is_localized_for_every_tier-1_language,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:30:57_Tails_is_localized_for_every_tier-1_language,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:30:57_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:48.682
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.967
When I log in to a new session in German (de) 46.371
Then the keyboard layout is set to "de" 0.365
When the network is plugged 0.102
And Tor is ready 20.735
Then I successfully start the Unsafe Browser 26.217
And I kill the Unsafe Browser 7.964
When I enable the screen keyboard 0.178
Then the screen keyboard works in Tor Browser 58.779
cannot 
cannot find ScreenKeyboard.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:417:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:48: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 "de" 0.000
After features/support/hooks.rb:330 5.827 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#5)' (at time 04:33:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:33:52_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_feature-trixie/8/artifact/build-artifacts/04:33:52_Tails_is_localized_for_every_tier-1_language,_Examples___5_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:33:52_Tails_is_localized_for_every_tier-1_language,_Examples___5_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:33:52_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:27.533
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.696
When I log in to a new session in Italian (it) 3:19.837
cannot 
cannot find GnomeApplicationsMenuItalian.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/common_steps.rb:571:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:524:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/localization.feature:52:in `When I log in to a new session in Italian (it)'
features/localization.feature:23:in `When I log in to a new session in <language> (<lang_code>)'
Then the keyboard layout is set to "it" 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I successfully start the Unsafe Browser 0.000
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 6.614 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#6)' (at time 04:37:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:37:25_Tails_is_localized_for_every_tier-1_language,_Examples___6_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:37:25_Tails_is_localized_for_every_tier-1_language,_Examples___6_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:37:25_Tails_is_localized_for_every_tier-1_language,_Examples___6_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:37:25_Tails_is_localized_for_every_tier-1_language,_Examples___6_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:27.542
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.773
When I log in to a new session in Persian (fa) 3:19.768
cannot 
cannot find GnomeApplicationsMenuPersian.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/common_steps.rb:571:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:524:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/localization.feature:53:in `When I log in to a new session in Persian (fa)'
features/localization.feature:23:in `When I log in to a new session in <language> (<lang_code>)'
Then the keyboard layout is set to "ir" 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I successfully start the Unsafe Browser 0.000
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 "ir" 0.000
After features/support/hooks.rb:330 6.101 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#7)' (at time 04:41:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:41:00_Tails_is_localized_for_every_tier-1_language,_Examples___7_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:41:00_Tails_is_localized_for_every_tier-1_language,_Examples___7_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:41:00_Tails_is_localized_for_every_tier-1_language,_Examples___7_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:41:00_Tails_is_localized_for_every_tier-1_language,_Examples___7_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:8.286
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.227
When I log in to a new session in Portuguese (pt) 45.271
Then the keyboard layout is set to "pt" 0.315
When the network is plugged 0.119
And Tor is ready 20.471
Then I successfully start the Unsafe Browser 16.318
And I kill the Unsafe Browser 6.967
When I enable the screen keyboard 0.285
Then the screen keyboard works in Tor Browser 30.309
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:1051:in `launch_app'
./features/step_definitions/common_steps.rb:1106:in `launch_tor_browser'
./features/step_definitions/browser.rb:445:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:411:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:54: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.969 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#8)' (at time 04:43:14)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:43:14_Tails_is_localized_for_every_tier-1_language,_Examples___8_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:43:14_Tails_is_localized_for_every_tier-1_language,_Examples___8_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:43:14_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:15.595
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 7.801
When I log in to a new session in Russian (ru) 46.348
Then the keyboard layout is set to "ru" 0.258
When the network is plugged 0.073
And Tor is ready 19.875
Then I successfully start the Unsafe Browser 16.581
And I kill the Unsafe Browser 7.254
When I enable the screen keyboard 0.150
Then the screen keyboard works in Tor Browser 37.250
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:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:411: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 "ru" 0.000
After features/support/hooks.rb:330 8.515 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#9)' (at time 04:45:41)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:45:41_Tails_is_localized_for_every_tier-1_language,_Examples___9_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:45:41_Tails_is_localized_for_every_tier-1_language,_Examples___9_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:45:41_Tails_is_localized_for_every_tier-1_language,_Examples___9_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:52.510
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 20.381
When I log in to a new session in Spanish (es) 50.379
Then the keyboard layout is set to "es" 0.368
When the network is plugged 0.079
And Tor is ready 18.871
Then I successfully start the Unsafe Browser 16.728
And I kill the Unsafe Browser 7.155
When I enable the screen keyboard 0.162
Then the screen keyboard works in Tor Browser 58.384
cannot 
cannot find ScreenKeyboard.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:417:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:56: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 9.237 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#10)' (at time 04:48:42)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:48:42_Tails_is_localized_for_every_tier-1_language,_Examples___10_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:48:42_Tails_is_localized_for_every_tier-1_language,_Examples___10_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:48:42_Tails_is_localized_for_every_tier-1_language,_Examples___10_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:1.183
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.004
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 7.774
When I log in to a new session in Turkish (tr) 48.281
Then the keyboard layout is set to "tr" 0.470
When the network is plugged 0.077
And Tor is ready 28.051
Then I successfully start the Unsafe Browser 27.903
And I kill the Unsafe Browser 7.481
When I enable the screen keyboard 0.250
Then the screen keyboard works in Tor Browser 1:0.892
cannot 
cannot find ScreenKeyboard.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:417:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:57: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 6.259 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#11)' (at time 04:51:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:51:52_Tails_is_localized_for_every_tier-1_language,_Examples___11_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:51:52_Tails_is_localized_for_every_tier-1_language,_Examples___11_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:51:52_Tails_is_localized_for_every_tier-1_language,_Examples___11_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/04:51:52_Tails_is_localized_for_every_tier-1_language,_Examples___11_.journal
After features/support/hooks.rb:100 0.000
Feature: Packages are up-to-date
Tags: @source
11.178
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:538 0.000
Steps
Given I have the build manifest for the image under test 0.000
Then all packages listed in the build manifest are up-to-date 11.177
Command 
Command failed (returned pid 123925 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/tmp/tails-amd64-feature_trixie@d9e4590897+devel@f758ff6c94-20250529T2241Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/tmp/tails-amd64-feature_trixie@d9e4590897+devel@f758ff6c94-20250529T2241Z.build-manifest
INFO: Need to upgrade our own forked package:
  - flatpak (1.16.0-2.0tails2) to Debian trixie (1.16.1-1)
INFO: Need to upgrade to a new APT snapshot:
  - dpkg[dpkg-dev, dpkg] (1.22.18) to Debian trixie (1.22.19)
  - dpkg[libdpkg-perl] (1.22.18) to Debian trixie (1.22.19)
  - glib2.0[gir1.2-glib-2.0] (2.84.1-2) to Debian trixie (2.84.2-1)
  - glib2.0[libglib2.0-bin, libglib2.0-0t64, libglib2.0-data] (2.84.1-2) to Debian trixie (2.84.2-1)
.
<0> expected but was
<#<Process::Status: pid 123925 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_feature-trixie/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:545 0.000
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
4:2.243
Scenario Manual filesystem repair fails
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 8.278
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.110
When I try to enable persistence 0.297
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 37.739
When I repair the filesystem of the Persistent Storage 1.331
Then the Welcome Screen tells me that it failed to repair the Persistent Storage 0.059
When I log in to a new session 34.694
And all notifications have disappeared 32.242
# Now both WhisperBack and Tor Browser has started at the same
# time, so we do not know which window is focused. The steps about
# Tor Browser care about that, but the ones about WhisperBack do
# not, so we first deal with WhisperBack and then kill it to
# ensure that Tor Browser is focused.
Then WhisperBack is prefilled for fsck with summary: "Failed to repair the file system of your Persistent Storage" 1.721
And the file "/var/lib/gdm3/post-greeter-whisperback.json" is empty 2.466
When I close the "whisperback" window 2.005
Then the Tor Browser starts 2:1.294
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/browser.rb:469:in `/^the Tor Browser (?:has started|starts)$/'
features/persistence.feature:201:in `Then the Tor Browser starts'
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 6.253 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 05:55:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/05:55:05_Manual_filesystem_repair_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/05:55:05_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/05:55:05_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/05:55:05_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
2:10.952
Scenario Filesystem and I/O errors
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 8.640
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 12.108
And Tails detects disk read failures on the boot device 1.859
When I try to enable persistence 0.401
Then the Welcome Screen tells me that my hardware is probably failing 26.415
When I log in to a new session 50.093
And all notifications have disappeared 13.407
Then the Tor Browser starts 18.025
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:468:in `/^the Tor Browser (?:has started|starts)$/'
features/persistence.feature:213:in `Then the Tor Browser starts'
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 8.341 
SCENARIO FAILED: 'Filesystem and I/O errors' (at time 05:57:22)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/05:57:22_Filesystem_and_I_O_errors.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/05:57:22_Filesystem_and_I_O_errors.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/05:57:22_Filesystem_and_I_O_errors.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/05:57:22_Filesystem_and_I_O_errors.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
55.909
Background
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 without a persistent partition and logged in 12.139
And I create a persistent partition with the default settings 23.666
Then the "TorConfiguration" tps feature is not enabled 4.264
When the network is plugged 0.135
And the Tor Connection Assistant autostarts 10.820
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 4.882
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:826:in `click_connect_to_tor'
./features/step_definitions/tor.rb:635: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/persistent_tor_bridges.feature:13:in `And I configure some persistent obfs4 bridges in the Tor Connection Assistant'
And I wait until Tor is ready 0.000
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Using Persistent Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 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 5.603 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 05:58:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/05:58:27_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/05:58:27_Using_Persistent_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/05:58:27_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/05:58:27_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
50.489
Background
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 without a persistent partition and logged in 11.621
And I create a persistent partition with the default settings 23.239
Then the "TorConfiguration" tps feature is not enabled 2.596
When the network is plugged 0.084
And the Tor Connection Assistant autostarts 7.957
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 4.989
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:826:in `click_connect_to_tor'
./features/step_definitions/tor.rb:635: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/persistent_tor_bridges.feature:13:in `And I configure some persistent obfs4 bridges in the Tor Connection Assistant'
And I wait until Tor is ready 0.000
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 5.372 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 05:59:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/05:59:23_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/05:59:23_Disabling_persistence_of_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/05:59:23_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/05:59:23_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
51.148
Scenario Chatting with some friend over XMPP
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 I have started Tails from DVD and logged in and the network is connected 15.295
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.347
Then I see Pidgin's account manager window 3.735
When I create my XMPP account 20.770
cannot 
cannot find PidginAddAccountWindow.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/pidgin.rb:123:in `/^I create my XMPP account$/'
features/pidgin.feature:21:in `When I create my XMPP account'
And I close Pidgin's account manager window 0.000
Then Pidgin automatically enables my XMPP account 0.000
Given my XMPP friend goes online 0.000
When I start a conversation with my friend 0.000
And I say something to my friend 0.000
Then I receive a response from my friend 0.000
After features/support/hooks.rb:521 0.038
After features/support/hooks.rb:330 6.148 
SCENARIO FAILED: 'Chatting with some friend over XMPP' (at time 06:00:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:00:48_Chatting_with_some_friend_over_XMPP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:00:48_Chatting_with_some_friend_over_XMPP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:00:48_Chatting_with_some_friend_over_XMPP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:00:48_Chatting_with_some_friend_over_XMPP.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
49.900
Scenario Chatting with some friend over XMPP in a multi-user chat
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:513 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 14.130
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.297
Then I see Pidgin's account manager window 3.518
When I create my XMPP account 20.955
cannot 
cannot find PidginAddAccountWindow.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/pidgin.rb:123:in `/^I create my XMPP account$/'
features/pidgin.feature:34:in `When I create my XMPP account'
And I close Pidgin's account manager window 0.000
Then Pidgin automatically enables my XMPP account 0.000
When I join some empty multi-user chat 0.000
And I clear the multi-user chat's scrollback 0.000
And my XMPP friend goes online and joins the multi-user chat 0.000
Then I can see that my friend joined the multi-user chat 0.000
And I say something to my friend in the multi-user chat 0.000
Then I receive a response from my friend in the multi-user chat 0.000
When I say https://gitlab.tails.boum.org/tails to my friend in the multi-user chat 0.000
Then I see the Tails GitLab URL 0.000
When I wait 10 seconds 0.000
And I click on the Tails GitLab URL 0.000
Then the Tor Browser loads the Tails GitLab 0.000
After features/support/hooks.rb:521 0.044
After features/support/hooks.rb:330 5.465 
SCENARIO FAILED: 'Chatting with some friend over XMPP in a multi-user chat' (at time 06:01:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:01:44_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:01:44_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:01:44_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:01:44_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
47.960
Scenario Connecting to the tails multi-user chat with my XMPP account
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:513 0.001
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.499
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.048
Then I see Pidgin's account manager window 3.596
And I create my XMPP account 20.815
cannot 
cannot find PidginAddAccountWindow.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/pidgin.rb:123:in `/^I create my XMPP account$/'
features/pidgin.feature:54:in `And I create my XMPP account'
And I close Pidgin's account manager window 0.000
Then Pidgin automatically enables my XMPP account 0.000
And I can join the "tails" channel on "chat.disroot.org" 0.000
After features/support/hooks.rb:521 0.045
After features/support/hooks.rb:330 5.511 
SCENARIO FAILED: 'Connecting to the tails multi-user chat with my XMPP account' (at time 06:02:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:02:38_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:02:38_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:02:38_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:02:38_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
1:17.488
Scenario Using a persistent Pidgin configuration
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:513 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.797
And the network is plugged 0.091
And Tor is ready 21.841
And available upgrades have been checked 2.160
And all notifications have disappeared 5.129
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.314
Then I see Pidgin's account manager window 3.440
When I create my XMPP account 20.711
cannot 
cannot find PidginAddAccountWindow.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/pidgin.rb:123:in `/^I create my XMPP account$/'
features/pidgin.feature:68:in `When I create my XMPP account'
And I close Pidgin's account manager window 0.000
Then Pidgin automatically enables my XMPP account 0.000
When I close Pidgin 0.000
And I take note of the configured Pidgin accounts 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Given a computer 0.000
And I start Tails from USB drive "__internal" and I login with persistence enabled 0.000
And Pidgin has the expected persistent accounts configured 0.000
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 0.000
Then Pidgin automatically enables my XMPP account 0.000
And I join some empty multi-user chat 0.000
# Exercise Pidgin AppArmor profile with persistence enabled.
# This should really be in dedicated scenarios, but it would be
# too costly to set up the virtual USB drive with persistence more
# than once in this feature.
Given I start monitoring the AppArmor log of "/usr/bin/pidgin" 0.000
Then I cannot add a certificate from the "/home/amnesia/.gnupg" directory to Pidgin 0.000
And AppArmor has denied "/usr/bin/pidgin" from opening "/home/amnesia/.gnupg/test.crt" 0.000
When I close Pidgin's certificate import failure dialog 0.000
And I close Pidgin's certificate manager 0.000
Given I restart monitoring the AppArmor log of "/usr/bin/pidgin" 0.000
Then I cannot add a certificate from the "/live/persistence/TailsData_unlocked/gnupg" directory to Pidgin 0.000
And AppArmor has denied "/usr/bin/pidgin" from opening "/live/persistence/TailsData_unlocked/gnupg/test.crt" 0.000
When I close Pidgin's certificate import failure dialog 0.000
And I close Pidgin's certificate manager 0.000
Then I can add a certificate from the "/home/amnesia" directory to Pidgin 0.000
After features/support/hooks.rb:521 0.041
After features/support/hooks.rb:330 5.464 
SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 06:04:01)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:04:01_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:04:01_Using_a_persistent_Pidgin_configuration.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:04:01_Using_a_persistent_Pidgin_configuration.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:04:01_Using_a_persistent_Pidgin_configuration.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
10.153
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.792
Then there are no unexpected messages of priority "err" or higher in the journal 0.360
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": "578",
    "_BOOT_ID": "148674629f5746cd8966883dd014a0e9",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "578",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748561840975182",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "26718332572d4dfc9de59108e9d7536d",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=ee2f901b28c8462cba9a2e41999f45b9;i=359;b=148674629f5746cd8966883dd014a0e9;m=bd5ef1;t=6364ec7662d75;x=858a2e7ed65c97bf",
    "__MONOTONIC_TIMESTAMP": "12410609",
    "__REALTIME_TIMESTAMP": "1748561840975221",
    "__SEQNUM": "857",
    "__SEQNUM_ID": "ee2f901b28c8462cba9a2e41999f45b9"
  },
  {
    "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": "578",
    "_BOOT_ID": "148674629f5746cd8966883dd014a0e9",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "578",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748561840975206",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "26718332572d4dfc9de59108e9d7536d",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=ee2f901b28c8462cba9a2e41999f45b9;i=35b;b=148674629f5746cd8966883dd014a0e9;m=bd5f78;t=6364ec7662dfc;x=ab14a8f63313b7d5",
    "__MONOTONIC_TIMESTAMP": "12410744",
    "__REALTIME_TIMESTAMP": "1748561840975356",
    "__SEQNUM": "859",
    "__SEQNUM_ID": "ee2f901b28c8462cba9a2e41999f45b9"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2395",
    "SYSLOG_TIMESTAMP": "May 29 23:37:29 ",
    "_BOOT_ID": "148674629f5746cd8966883dd014a0e9",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2395",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748561849227546",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "585a242f37844f2899e2f93e2c4feadd",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=ee2f901b28c8462cba9a2e41999f45b9;i=407;b=148674629f5746cd8966883dd014a0e9;m=13b4ac5;t=6364ec7e41949;x=a107847520527bd2",
    "__MONOTONIC_TIMESTAMP": "20662981",
    "__REALTIME_TIMESTAMP": "1748561849227593",
    "__SEQNUM": "1031",
    "__SEQNUM_ID": "ee2f901b28c8462cba9a2e41999f45b9"
  },
  {
    "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": "578",
    "_BOOT_ID": "148674629f5746cd8966883dd014a0e9",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "578",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748562026531673",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "26718332572d4dfc9de59108e9d7536d",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=ee2f901b28c8462cba9a2e41999f45b9;i=8d4;b=148674629f5746cd8966883dd014a0e9;m=638e064;t=6364ed2758ba5;x=ab8d10f8ca672fe2",
    "__MONOTONIC_TIMESTAMP": "104390756",
    "__REALTIME_TIMESTAMP": "1748562026531749",
    "__SEQNUM": "2260",
    "__SEQNUM_ID": "ee2f901b28c8462cba9a2e41999f45b9"
  },
  {
    "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": "578",
    "_BOOT_ID": "148674629f5746cd8966883dd014a0e9",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "578",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748562026532301",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "26718332572d4dfc9de59108e9d7536d",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=ee2f901b28c8462cba9a2e41999f45b9;i=8d6;b=148674629f5746cd8966883dd014a0e9;m=638f54b;t=6364ed275a08c;x=57600b5624d1d3b0",
    "__MONOTONIC_TIMESTAMP": "104396107",
    "__REALTIME_TIMESTAMP": "1748562026537100",
    "__SEQNUM": "2262",
    "__SEQNUM_ID": "ee2f901b28c8462cba9a2e41999f45b9"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "17918",
    "SYSLOG_TIMESTAMP": "May 29 23:40:33 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "148674629f5746cd8966883dd014a0e9",
    "_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": "17918",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748562033777535",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "10c5fac326554c97ae8216fbabf91ea6",
    "_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=ee2f901b28c8462cba9a2e41999f45b9;i=1231;b=148674629f5746cd8966883dd014a0e9;m=6a77048;t=6364ed2e41b88;x=e14688cf05c4b668",
    "__MONOTONIC_TIMESTAMP": "111636552",
    "__REALTIME_TIMESTAMP": "1748562033777544",
    "__SEQNUM": "4657",
    "__SEQNUM_ID": "ee2f901b28c8462cba9a2e41999f45b9"
  }
].
<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.542 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from DVD' (at time 06:08:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:08:53_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_feature-trixie/8/artifact/build-artifacts/06:08:53_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:08:53_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:08:53_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
12.091
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 12.020
Then there are no unexpected messages of priority "err" or higher in the journal 0.070
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": "58ee3639911d494c96aa1cfaf8c43a55",
    "_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": "1748564013260442",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "e682e0558ded4aacb95af1d7e1f05cce",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=2f2629a3013d424b9684edfed5652a6e;i=38b;b=58ee3639911d494c96aa1cfaf8c43a55;m=f4f48f;t=6364f48e0afaa;x=c6f4164325532143",
    "__MONOTONIC_TIMESTAMP": "16053391",
    "__REALTIME_TIMESTAMP": "1748564013264810",
    "__SEQNUM": "907",
    "__SEQNUM_ID": "2f2629a3013d424b9684edfed5652a6e"
  },
  {
    "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": "58ee3639911d494c96aa1cfaf8c43a55",
    "_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": "1748564013260472",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "e682e0558ded4aacb95af1d7e1f05cce",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=2f2629a3013d424b9684edfed5652a6e;i=38d;b=58ee3639911d494c96aa1cfaf8c43a55;m=f4f5cc;t=6364f48e0b0e7;x=b5339b7dc49d5c9b",
    "__MONOTONIC_TIMESTAMP": "16053708",
    "__REALTIME_TIMESTAMP": "1748564013265127",
    "__SEQNUM": "909",
    "__SEQNUM_ID": "2f2629a3013d424b9684edfed5652a6e"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2304",
    "SYSLOG_TIMESTAMP": "May 30 00:13:40 ",
    "_BOOT_ID": "58ee3639911d494c96aa1cfaf8c43a55",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2304",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748564020780930",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "d8efc9d8bf6445118b2b4f8d9eaacf18",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=2f2629a3013d424b9684edfed5652a6e;i=407;b=58ee3639911d494c96aa1cfaf8c43a55;m=167a47c;t=6364f49535f97;x=44e7fffc89089a2b",
    "__MONOTONIC_TIMESTAMP": "23569532",
    "__REALTIME_TIMESTAMP": "1748564020780951",
    "__SEQNUM": "1031",
    "__SEQNUM_ID": "2f2629a3013d424b9684edfed5652a6e"
  },
  {
    "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": "58ee3639911d494c96aa1cfaf8c43a55",
    "_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": "1748564161683061",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "e682e0558ded4aacb95af1d7e1f05cce",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=2f2629a3013d424b9684edfed5652a6e;i=e7d;b=58ee3639911d494c96aa1cfaf8c43a55;m=9992819;t=6364f51b95ec1;x=c15f74f5b7e0d3f3",
    "__MONOTONIC_TIMESTAMP": "161032217",
    "__REALTIME_TIMESTAMP": "1748564161683137",
    "__SEQNUM": "3709",
    "__SEQNUM_ID": "2f2629a3013d424b9684edfed5652a6e"
  },
  {
    "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": "58ee3639911d494c96aa1cfaf8c43a55",
    "_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": "1748564161683506",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "e682e0558ded4aacb95af1d7e1f05cce",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=2f2629a3013d424b9684edfed5652a6e;i=e7f;b=58ee3639911d494c96aa1cfaf8c43a55;m=999298e;t=6364f51b96036;x=3bb600777bbf18f7",
    "__MONOTONIC_TIMESTAMP": "161032590",
    "__REALTIME_TIMESTAMP": "1748564161683510",
    "__SEQNUM": "3711",
    "__SEQNUM_ID": "2f2629a3013d424b9684edfed5652a6e"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "22354",
    "SYSLOG_TIMESTAMP": "May 30 00:16:09 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "58ee3639911d494c96aa1cfaf8c43a55",
    "_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": "22354",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748564169562077",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "193cf8e2d8c4458c999f66afb8ef0f18",
    "_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=2f2629a3013d424b9684edfed5652a6e;i=1849;b=58ee3639911d494c96aa1cfaf8c43a55;m=a11615f;t=6364f52319807;x=ae92025c72bf20bd",
    "__MONOTONIC_TIMESTAMP": "168911199",
    "__REALTIME_TIMESTAMP": "1748564169562119",
    "__SEQNUM": "6217",
    "__SEQNUM_ID": "2f2629a3013d424b9684edfed5652a6e"
  }
].
<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.256 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 06:09:11)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:09:11_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_feature-trixie/8/artifact/build-artifacts/06:09:11_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:09:11_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:09:11_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
49.275
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.764
When I request a shutdown using the system menu 36.511
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Power Off' roleName='label'
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:898: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.398 
SCENARIO FAILED: 'I can shutdown Tails via the system menu' (at time 06:10:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:10:05_I_can_shutdown_Tails_via_the_system_menu.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:10:05_I_can_shutdown_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:10:05_I_can_shutdown_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:10:05_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
49.455
Scenario I can reboot 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.350
When I request a reboot using the system menu 37.105
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Restart' roleName='label'
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:898: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.459 
SCENARIO FAILED: 'I can reboot Tails via the system menu' (at time 06:11:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:11:00_I_can_reboot_Tails_via_the_system_menu.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:11:00_I_can_reboot_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:11:00_I_can_reboot_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:11:00_I_can_reboot_Tails_via_the_system_menu.journal
After features/support/hooks.rb:100 0.000
Feature: Logging in via SSH
Tags: @product @check_tor_leaks @not_release_blocker
1:48.052
Scenario Connecting to an SFTP server on the Internet using the GNOME "Connect to Server" feature
Steps
Given I have the SSH key pair for an SFTP server 0.261
When I connect to an SFTP server on the Internet 1:47.790
Tor 
Tor operation failed (despite retrying 10 times) with
FindFailed: cannot find NautilusOtherLocations.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/ssh.rb:141:in `/^I connect to an SFTP server on the Internet$/'
features/ssh.feature:28:in `When I connect to an SFTP server on the Internet'
Then I successfully connect to the SFTP server 0.000
After features/support/hooks.rb:521 0.030
After features/support/hooks.rb:330 4.939 
SCENARIO FAILED: 'Connecting to an SFTP server on the Internet using the GNOME "Connect to Server" feature' (at time 06:13:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:13:50_Connecting_to_an_SFTP_server_on_the_Internet_using_the_GNOME__Connect_to_Server__feature.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:13:50_Connecting_to_an_SFTP_server_on_the_Internet_using_the_GNOME__Connect_to_Server__feature.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:13:50_Connecting_to_an_SFTP_server_on_the_Internet_using_the_GNOME__Connect_to_Server__feature.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:13:50_Connecting_to_an_SFTP_server_on_the_Internet_using_the_GNOME__Connect_to_Server__feature.journal
After features/support/hooks.rb:100 0.000
Feature: Tor Connection helps the user in connecting to Tor
Tags: @product
32.685
Scenario Starting Tor Connection before connecting to Wi-Fi
Steps
When I start "Tor Connection" via GNOME Activities Overview 10.074
Then the Tor Connection Assistant reports that I am not connected to a local network 3.409
When I plug a Wi-Fi adapter 1.346
Then Tor Connection suggests me to connect to Wi-Fi 0.994
And I click on the Wi-Fi settings 1.171
And The Wi-Fi settings are displayed 15.688
The 
The Dogtail init script raised: SearchError: descendant of [list item | Sound]: child with name='Wi-Fi' roleName='label'
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/tor.rb:1116:in `/^The Wi-Fi settings are displayed$/'
features/tor_connection.feature:15:in `And The Wi-Fi settings are displayed'
After features/support/hooks.rb:330 6.513 
SCENARIO FAILED: 'Starting Tor Connection before connecting to Wi-Fi' (at time 06:16:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:16:34_Starting_Tor_Connection_before_connecting_to_Wi-Fi.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:16:34_Starting_Tor_Connection_before_connecting_to_Wi-Fi.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:16:34_Starting_Tor_Connection_before_connecting_to_Wi-Fi.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:16:34_Starting_Tor_Connection_before_connecting_to_Wi-Fi.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
49.176
Scenario The Downloads directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:513 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.356
Then the live user's Downloads directory exists 0.055
And there is a GNOME bookmark for the Downloads directory 36.764
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Downloads' roleName='label'
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:1225:in `/^there is a GNOME bookmark for the (.*) directory$/'
features/torified_browsing.feature:21:in `And there is a GNOME bookmark for the Downloads directory'
When I start the Tor Browser 0.000
And the Tor Browser loads the startup page 0.000
Then I can save the current page as "index.html" to the Downloads directory 0.000
And I can print the current page as "output.pdf" to the Downloads directory 0.000
After features/support/hooks.rb:521 0.041
After features/support/hooks.rb:330 6.224 
SCENARIO FAILED: 'The Downloads directory is usable in Tor Browser' (at time 06:39:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:39:08_The_Downloads_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:39:08_The_Downloads_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:39:08_The_Downloads_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:39:08_The_Downloads_directory_is_usable_in_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
1:8.516
Scenario Downloading files with the Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:513 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 11.979
When I start the Tor Browser 28.782
Then the Tor Browser loads the startup page 2.225
When I download some file in the Tor Browser to the Downloads directory 25.528
The 
The Dogtail init script raised: SearchError: descendant of [application | xdg-desktop-portal-gtk]: child with roleName='file chooser'
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/browser.rb:10:in `desktop_portal_save_as_dialog'
./features/step_definitions/browser.rb:294:in `/^I download some file in the Tor Browser to the (.*) directory$/'
features/torified_browsing.feature:32:in `When I download some file in the Tor Browser to the Downloads directory'
Then the file is saved to the Downloads directory 0.000
After features/support/hooks.rb:521 0.051
After features/support/hooks.rb:330 7.833 
SCENARIO FAILED: 'Downloading files with the Tor Browser' (at time 06:40:22)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:40:22_Downloading_files_with_the_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:40:22_Downloading_files_with_the_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:40:22_Downloading_files_with_the_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:40:22_Downloading_files_with_the_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
38.734
Scenario The Tor Browser uses TBB's shared libraries
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.149
When I start the Tor Browser 23.958
Then the Tor Browser uses all expected TBB shared libraries 2.626
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:243:in `xul_app_shared_lib_check'
./features/step_definitions/browser.rb:257:in `/^the (.*) uses all expected TBB shared libraries$/'
features/torified_browsing.feature:76:in `Then the Tor Browser uses all expected TBB shared libraries'
After features/support/hooks.rb:330 5.109 
SCENARIO FAILED: 'The Tor Browser uses TBB's shared libraries' (at time 06:45:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:45:37_The_Tor_Browser_uses_TBB_s_shared_libraries.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:45:37_The_Tor_Browser_uses_TBB_s_shared_libraries.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:45:37_The_Tor_Browser_uses_TBB_s_shared_libraries.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:45:37_The_Tor_Browser_uses_TBB_s_shared_libraries.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:58.503
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.839
And the network is plugged 0.079
And I successfully configure Tor 47.035
And available upgrades have been checked 0.065
And all notifications have disappeared 5.185
And there is a GNOME bookmark for the Persistent directory 2.037
When I start the Tor Browser 23.370
And I download some file in the Tor Browser to the Persistent directory 28.890
The 
The Dogtail init script raised: SearchError: descendant of [application | xdg-desktop-portal-gtk]: child with roleName='file chooser'
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/browser.rb:10:in `desktop_portal_save_as_dialog'
./features/step_definitions/browser.rb:294:in `/^I download some file in the Tor Browser to the (.*) directory$/'
features/torified_browsing.feature:113:in `And I download some file in the Tor Browser to the Persistent directory'
Then the file is saved to the Persistent directory 0.000
When I open the address "https://tails.net/about" in the Tor Browser 0.000
Then "Tails - How Tails works" has loaded in the Tor Browser 0.000
And I can print the current page as "output.pdf" to the Persistent directory 0.000
After features/support/hooks.rb:330 8.805 
SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 06:51:06)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:51:06_The_Persistent_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:51:06_The_Persistent_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:51:06_The_Persistent_directory_is_usable_in_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
45.004
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.004
Steps
Given I have started Tails from DVD without network and logged in 9.110
Then the live user's Documents directory exists 0.100
And there is a GNOME bookmark for the Documents directory 35.794
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Documents' roleName='label'
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:1225:in `/^there is a GNOME bookmark for the (.*) directory$/'
features/torified_browsing.feature:127:in `And there is a GNOME bookmark for the Documents directory'
features/torified_browsing.feature:122:in `And there is a GNOME bookmark for the <dir> directory'
Then I start the Tor Browser in offline mode 0.000
And I can save the current page as "index.html" to the Documents GNOME bookmark 0.000
After features/support/hooks.rb:330 6.023 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#1)' (at time 06:51:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:51:59_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:51:59_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:51:59_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:51:59_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
45.252
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.006
Steps
Given I have started Tails from DVD without network and logged in 8.839
Then the live user's Downloads directory exists 0.090
And there is a GNOME bookmark for the Downloads directory 36.321
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Downloads' roleName='label'
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:1225:in `/^there is a GNOME bookmark for the (.*) directory$/'
features/torified_browsing.feature:128:in `And there is a GNOME bookmark for the Downloads directory'
features/torified_browsing.feature:122:in `And there is a GNOME bookmark for the <dir> directory'
Then I start the Tor Browser in offline mode 0.000
And I can save the current page as "index.html" to the Downloads GNOME bookmark 0.000
After features/support/hooks.rb:330 5.752 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#2)' (at time 06:52:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:52:51_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:52:51_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:52:51_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:52:51_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
44.914
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.006
Steps
Given I have started Tails from DVD without network and logged in 8.889
Then the live user's Music directory exists 0.149
And there is a GNOME bookmark for the Music directory 35.875
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Music' roleName='label'
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:1225:in `/^there is a GNOME bookmark for the (.*) directory$/'
features/torified_browsing.feature:129:in `And there is a GNOME bookmark for the Music directory'
features/torified_browsing.feature:122:in `And there is a GNOME bookmark for the <dir> directory'
Then I start the Tor Browser in offline mode 0.000
And I can save the current page as "index.html" to the Music GNOME bookmark 0.000
After features/support/hooks.rb:330 6.069 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#3)' (at time 06:53:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:53:41_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:53:41_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:53:41_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:53:41_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
59.299
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.006
Steps
Given I have started Tails from DVD without network and logged in 22.416
Then the live user's Pictures directory exists 0.113
And there is a GNOME bookmark for the Pictures directory 36.770
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Pictures' roleName='label'
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:1225:in `/^there is a GNOME bookmark for the (.*) directory$/'
features/torified_browsing.feature:130:in `And there is a GNOME bookmark for the Pictures directory'
features/torified_browsing.feature:122:in `And there is a GNOME bookmark for the <dir> directory'
Then I start the Tor Browser in offline mode 0.000
And I can save the current page as "index.html" to the Pictures GNOME bookmark 0.000
After features/support/hooks.rb:330 5.807 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#4)' (at time 06:54:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:54:47_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:54:47_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:54:47_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:54:47_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
45.498
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.006
Steps
Given I have started Tails from DVD without network and logged in 9.077
Then the live user's Videos directory exists 0.072
And there is a GNOME bookmark for the Videos directory 36.348
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Videos' roleName='label'
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:1225:in `/^there is a GNOME bookmark for the (.*) directory$/'
features/torified_browsing.feature:131:in `And there is a GNOME bookmark for the Videos directory'
features/torified_browsing.feature:122:in `And there is a GNOME bookmark for the <dir> directory'
Then I start the Tor Browser in offline mode 0.000
And I can save the current page as "index.html" to the Videos GNOME bookmark 0.000
After features/support/hooks.rb:330 5.720 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#5)' (at time 06:55:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:55:38_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_feature-trixie/8/artifact/build-artifacts/06:55:38_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:55:38_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/06:55:38_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
53.431
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.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.909
When I successfully start the Unsafe Browser 18.967
# 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.010 
Slept for 10 seconds
And I try to start the Unsafe Browser 0.381
Then I see a warning about another instance already running 11.163
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'zenity' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./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 `/^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.680 
SCENARIO FAILED: 'Starting a second instance of the Unsafe Browser results in an error message being shown' (at time 07:09:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:09:44_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:09:44_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_feature-trixie/8/artifact/build-artifacts/07:09:44_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_feature-trixie/8/artifact/build-artifacts/07:09:44_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
19.664
Scenario Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume
Steps
When I plug a USB drive containing a basic VeraCrypt volume 7.034
And I cancel the GNOME authentication prompt 2.530
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 5.633
And I open this VeraCrypt volume in GNOME Files 3.789
Then I see the expected contents in this VeraCrypt volume 0.596
When I lock the currently opened VeraCrypt volume 0.079
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<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/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:18:in `When I lock the currently opened VeraCrypt volume'
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.322 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume' (at time 07:14:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:14:17_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:14:17_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:14:17_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:14:17_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
23.551
Scenario Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume
Steps
When I plug a USB drive containing a hidden VeraCrypt volume 10.347
And I cancel the GNOME authentication prompt 2.586
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 6.112
And I open this VeraCrypt volume in GNOME Files 3.953
Then I see the expected contents in this VeraCrypt volume 0.465
When I lock the currently opened VeraCrypt volume 0.085
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<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/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:27:in `When I lock the currently opened VeraCrypt volume'
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.320 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:14:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:14:56_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:14:56_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:14:56_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:14:56_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
28.790
Scenario Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 15.954
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 8.776
And I open this VeraCrypt volume in GNOME Files 3.514
Then I see the expected contents in this VeraCrypt volume 0.467
When I lock the currently opened VeraCrypt file container 0.076
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<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/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:35:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.308 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM' (at time 07:15:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:15:39_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:15:39_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:15:39_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:15:39_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
39.330
Scenario Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 26.376
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 8.603
And I open this VeraCrypt volume in GNOME Files 3.853
Then I see the expected contents in this VeraCrypt volume 0.424
When I lock the currently opened VeraCrypt file container 0.072
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<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/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:43:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.374 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container' (at time 07:16:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:16:33_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:16:33_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:16:33_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:16:33_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.016
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
25.480
Scenario Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile
Steps
When I plug a USB drive containing a basic VeraCrypt volume with a keyfile 6.990
And I cancel the GNOME authentication prompt 2.852
And I unlock and mount this VeraCrypt volume with GNOME Disks 11.403
And I open this VeraCrypt volume in GNOME Files 3.730
Then I see the expected contents in this VeraCrypt volume 0.420
When I lock the currently opened VeraCrypt volume 0.082
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<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/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:54:in `When I lock the currently opened VeraCrypt volume'
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.412 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 07:17:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:17:13_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:17:13_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:17:13_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:17:13_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
25.839
Scenario Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume
Steps
When I plug a USB drive containing a hidden VeraCrypt volume 10.329
And I cancel the GNOME authentication prompt 2.551
And I unlock and mount this VeraCrypt volume with GNOME Disks 8.668
And I open this VeraCrypt volume in GNOME Files 3.778
Then I see the expected contents in this VeraCrypt volume 0.433
When I lock the currently opened VeraCrypt volume 0.077
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<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/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:63:in `When I lock the currently opened VeraCrypt volume'
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.278 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:17:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:17:53_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:17:53_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:17:53_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:17:53_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
49.287
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a keyfile 22.901
And I unlock and mount this VeraCrypt file container with GNOME Disks 21.983
And I open this VeraCrypt volume in GNOME Files 3.882
Then I see the expected contents in this VeraCrypt volume 0.431
When I lock the currently opened VeraCrypt file container 0.089
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<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/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:71:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.342 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 07:18:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:18:57_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:18:57_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:18:57_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:18:57_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.014
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
49.593
Scenario Use GNOME Disks to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 25.980
And I unlock and mount this VeraCrypt file container with GNOME Disks 19.286
And I open this VeraCrypt volume in GNOME Files 3.807
Then I see the expected contents in this VeraCrypt volume 0.434
When I lock the currently opened VeraCrypt file container 0.083
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<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/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:79:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.286 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 07:20:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:20:00_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:20:00_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:20:00_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:20:00_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.014
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
39.643
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 16.507
And I unlock and mount this VeraCrypt file container with GNOME Disks 18.753
And I open this VeraCrypt volume in GNOME Files 4.076
Then I see the expected contents in this VeraCrypt volume 0.221
When I lock the currently opened VeraCrypt file container 0.084
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<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/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:87:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.312 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM' (at time 07:20:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:20:54_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:20:54_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:20:54_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/8/artifact/build-artifacts/07:20:54_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000