Project Number Date
test_Tails_ISO_feature-trixie 5 27 May 2025, 18:51

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
24.353
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 7.047
And I wait until Tor is ready 5.279
When I disconnect the network through GNOME 12.025
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.319 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:36:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/00:36:50_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/5/artifact/build-artifacts/00:36:50_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/00:36:50_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/5/artifact/build-artifacts/00:36:50_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.028
Feature: Using Tor bridges and pluggable transports
Tags: @product
24.091
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 6.873
And I wait until Tor is ready 5.147
And I disconnect the network through GNOME 12.070
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.474 
SCENARIO FAILED: 'Reconnecting from an unblocked network to a blocked network displays an error' (at time 00:37:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/00:37:36_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/5/artifact/build-artifacts/00:37:36_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/5/artifact/build-artifacts/00:37:36_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/5/artifact/build-artifacts/00:37:36_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.journal
After features/support/hooks.rb:100 0.041
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
16.703
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.430
And I prepare Tails for memory erasure tests 0.545
When I start a process allocating 128 MiB of memory with a known pattern 2.455
Then patterns cover at least 128 MiB in the guest's memory 4.271
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.706 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:38:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/00:38:57_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/5/artifact/build-artifacts/00:38:57_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/00:38:57_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/00:38:57_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:23.662
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.002
Before features/support/hooks.rb:513 0.013
Steps
Given I have started Tails from DVD and logged in with an administration password and the network is connected 2:0.769
And I update APT using apt 14.184
When I install "popularity-contest" using apt 27.549
Then I am notified I can not use Additional Software for "popularity-contest" 12.204
And I can open the Additional Software documentation from the notification 3:28.955
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.035
After features/support/hooks.rb:330 8.674 
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:24:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/01:24:10_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/5/artifact/build-artifacts/01:24:10_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/5/artifact/build-artifacts/01:24:10_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/5/artifact/build-artifacts/01:24:10_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/5/artifact/build-artifacts/01:24:10_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/5/artifact/build-artifacts/01:24:10_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/5/artifact/build-artifacts/01:24:10_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/5/artifact/build-artifacts/01:24:10_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/5/artifact/build-artifacts/01:24:10_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:24.442
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.002
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:37.047
And I update APT using apt 12.265
And I install "popularity-contest" using apt 28.132
Then I am proposed to add the "popularity-contest" package to my Additional Software 18.056
When I create a persistent storage and activate the Additional Software feature 30.614
Then Additional Software is correctly configured for package "popularity-contest" 3.280
When I shutdown Tails and wait for the computer to power off 10.435
And I start Tails from USB drive "__internal" with network unplugged 1:57.612
And I enable persistence 27.435
And I log in to a new session 38.273
And the Additional Software installation service has started 59.636
Then I am notified that the installation succeeded 5:1.652
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.049
After features/support/hooks.rb:330 10.897 
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:36:43)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/01:36:43_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/01:36:43_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/01:36:43_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.journal
After features/support/hooks.rb:100 0.011
Feature: Additional software
Tags: @product @check_tor_leaks @slow
25:48.264
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:513 0.003
Steps
Given a computer 0.193
And I start Tails from USB drive "__internal" and I login with an administration password 3:31.054
And I update APT using apt 11.650
When I install "makepp" using apt 22:5.366
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.030
After features/support/hooks.rb:330 5.521 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 02:02:42)
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/5/artifact/build-artifacts/02:02:42_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/5/artifact/build-artifacts/02:02:42_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/5/artifact/build-artifacts/02:02:42_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/5/artifact/build-artifacts/02:02:42_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/5/artifact/build-artifacts/02:02:42_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/5/artifact/build-artifacts/02:02:42_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/5/artifact/build-artifacts/02:02:42_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/5/artifact/build-artifacts/02:02:42_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:40.760
Scenario My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:513 0.003
Steps
Given a computer 0.173
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 4:46.523
When I uninstall "popularity-contest" using apt 25.326
And I accept removing "popularity-contest" from Additional Software 0.696
Then "popularity-contest" is not in the list of Additional Software 1.157
When I start Synaptic 26.883
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 6.001 
SCENARIO FAILED: 'My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic' (at time 02:08:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/02:08:29_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/5/artifact/build-artifacts/02:08:29_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/5/artifact/build-artifacts/02:08:29_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/5/artifact/build-artifacts/02:08:29_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/5/artifact/build-artifacts/02:08:29_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/5/artifact/build-artifacts/02:08:29_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/5/artifact/build-artifacts/02:08:29_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/5/artifact/build-artifacts/02:08:29_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/5/artifact/build-artifacts/02:08:29_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.008
Feature: Upgrading an old Tails USB installation
Tags: @product
2:49.465
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.168
And I create a 7200 MiB disk named "old" 0.073
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 34.036
When I start Tails from USB drive "old" with network unplugged 2:14.139
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 8.095 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:31:02)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/02:31:02_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/02:31:02_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/5/artifact/build-artifacts/02:31:02_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product
1:24.488
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:24.284
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.956 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:32:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/02:32: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/5/artifact/build-artifacts/02:32:35_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/02:32: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/5/artifact/build-artifacts/02:32:35_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product
1:23.682
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:23.500
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.978 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:34:04)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/02:34:04_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/5/artifact/build-artifacts/02:34:04_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/5/artifact/build-artifacts/02:34:04_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/5/artifact/build-artifacts/02:34:04_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product
2:9.872
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.002
Steps
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.686
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.123 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:39:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/02:39:12_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/5/artifact/build-artifacts/02:39:12_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/5/artifact/build-artifacts/02:39:12_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/5/artifact/build-artifacts/02:39:12_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
22:52.308
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.013
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.734
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.364
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.220
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.337
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.488
When the network is plugged 0.072
And Tor is ready 23.168
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:10.814
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.601 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:02:11)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:02:11_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/5/artifact/build-artifacts/03:02:11_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:02:11_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:02:11_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
23:15.667
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.014
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.342
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 51.301
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:11.756
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.648 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:25:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:25:32_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/5/artifact/build-artifacts/03:25:32_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:25:32_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:25:32_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
1:58.035
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 9.065
And I prepare Tails for memory erasure tests 0.447
And I plug and mount a 128 MiB USB drive with a vfat filesystem 10.353
And I fill the USB drive with a known pattern 3.094
And I read the content of the test FS 0.074
And patterns cover at least 90% of the test FS size in the guest's memory 4.390 
Pattern coverage: 100.000% (127 MiB out of 127 MiB reference memory)
When I eject the boot medium 0.321
And I wait for Tails to finish wiping the memory 1:30.287
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.552 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: vfat' (at time 03:30:05)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:30:05_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:30:05_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:30:05_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:27.255
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.002
Steps
Given I have started Tails from DVD without network and logged in 9.340
And I prepare Tails for memory erasure tests 0.499
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 41.045
And I fill the USB drive with a known pattern 1.619
And I read the content of the test FS 0.166
And patterns cover at least 99% of the test FS size in the guest's memory 3.821 
Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)
When I eject the boot medium 0.382
And I wait for Tails to finish wiping the memory 1:30.380
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.832 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 03:32:43)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:32:43_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:32:43_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/5/artifact/build-artifacts/03:32:43_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.000
Feature: Emergency shutdown
Tags: @product @not_release_blocker
35.294
Scenario Tails erases memory and shuts down on USB boot medium removal: persistent data
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 11.190
And I prepare Tails for memory erasure tests 0.628
And I fill a 128 MiB file with a known pattern on the persistent filesystem 19.733
And patterns cover at least 100 MiB in the guest's memory 3.742
98.984% 
98.984% of the expected size (100 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/emergency_shutdown.feature:51:in `And patterns cover at least 100 MiB in the guest's memory'
Output 1 
Pattern coverage: 98.984% (98 MiB out of 100 MiB reference memory)
When I eject the boot medium 0.000
And I wait for Tails to finish wiping the memory 0.000
Then I find very few patterns in the guest's memory 0.000
And Tails eventually shuts down 0.000
After features/support/hooks.rb:330 5.548 
SCENARIO FAILED: 'Tails erases memory and shuts down on USB boot medium removal: persistent data' (at time 03:33:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:33:29_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:33:29_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:33:29_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:33:29_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.journal
After features/support/hooks.rb:100 0.000
Feature: Backing up the persistent storage
Tags: @product
1:18.199
Scenario Using Tails' custom backup tool to backup a newly added file
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.513
# The volume cannot be in use when GuestFs clones it, which we do below
And I shutdown Tails and wait for the computer to power off 11.038
And I clone USB drive "__internal" to a temporary USB drive "backup" 1.919
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.312
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.022
When I start Tails' custom backup tool 6.462
Then the backup tool displays "Plug in your backup Tails USB stick" 0.419
When I plug USB drive "backup" 2.773
And I give the Persistent Storage on drive "backup" its own UUID 0.312
And I click "Retry" in the backup tool 1.355
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.871
When I click "Back Up" in the backup tool 1.211
And I enter my persistent storage passphrase into the polkit prompt 20.987
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:796:in `deal_with_polkit_prompt'
./features/step_definitions/backup.rb:18:in `/^I enter my persistent storage passphrase into the polkit prompt$/'
features/backup.feature:21:in `And I enter my persistent storage passphrase into the polkit prompt'
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 0.000
# The backup tool ejects the drive, so we have to replug it
When I unplug USB drive "backup" 0.000
And I plug USB drive "backup" 0.000
Then the USB drive "backup" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:330 10.729 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 03:36:45)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:36:45_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:36:45_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:36:45_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.163
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
0.079
Scenario Getting a DHCP lease with the default NetworkManager connection
Steps
Then the hostname should not have been leaked on the network 0.079
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.124 
SCENARIO FAILED: 'Getting a DHCP lease with the default NetworkManager connection' (at time 03:37:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:37:42_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/5/artifact/build-artifacts/03:37:42_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.pcap
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:37:42_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:37:42_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:37:42_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.060
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
0.782
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.200
And I switch to the "manually-added-con" NetworkManager connection 0.477
Then the hostname should not have been leaked on the network 0.104
Hostname 
Hostname leak detected (DhcpLeakError)
./features/step_definitions/dhcp.rb:15:in `/^the hostname should not have been leaked on the network$/'
features/dhcp.feature:22:in `Then the hostname should not have been leaked on the network'
After features/support/hooks.rb:330 5.474 
SCENARIO FAILED: 'Getting a DHCP lease with a manually configured NetworkManager connection' (at time 03:38:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:38:23_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/5/artifact/build-artifacts/03:38:23_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.pcap
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:38:23_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:38:23_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:38:23_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.051
Feature: Hardware failures
Tags: @product
3:22.916
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 17.372
And I corrupt the boot device's GPT backup header 0.544
And I power off the computer 0.331
When I start the computer 1.085
Then the computer boots Tails 2:14.429
When I log in to a new session 35.986
And all notifications have disappeared 12.806
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.359
<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.382 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 03:57:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:57:03_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/5/artifact/build-artifacts/03:57:03_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:57:03_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/03:57:03_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:100 0.021
Feature: Hardware failures
Tags: @product
3:9.182
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.937
And I corrupt the boot device's GPT backup partition table 0.445
And I power off the computer 0.351
When I start the computer 1.041
Then the computer boots Tails 2:11.876
When I log in to a new session 31.767
And all notifications have disappeared 13.501
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.262
<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.355 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 04:00:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:00:18_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/5/artifact/build-artifacts/04:00:18_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:00:18_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:00:18_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:100 0.007
Feature: Hardware failures
Tags: @product
4:3.698
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.180
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.046
And I plug USB drive "temp" 1.050
And I write the Tails USB image to disk "temp" 33.692
When I start Tails from USB drive "temp" with network unplugged 2:47.314
Then Tails is running from USB drive "temp" 0.368
And the Greeter forbids creating a persistent partition 0.110
When I log in to a new session 30.963
And all notifications have disappeared 9.663
Then I am recommended to reinstall Tails due to partitioning errors 0.308
<"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 6.251 
SCENARIO FAILED: 'GPT backup corruption without a persistent partition' (at time 04:04:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:04:28_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/5/artifact/build-artifacts/04:04:28_GPT_backup_corruption_without_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:04:28_GPT_backup_corruption_without_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:04:28_GPT_backup_corruption_without_a_persistent_partition.journal
After features/support/hooks.rb:100 0.107
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
9.533
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 9.454
Then the keys trusted by APT are valid for the next 3 months 0.078
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.570 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 04:15:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:15:47_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/5/artifact/build-artifacts/04:15:47_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:15:47_The_included_APT_repository_keys_are_up-to-date.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:15:47_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product
1:43.823
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 12.997
And I log in to a new session in German (de) 49.966
Then the live user's Documents directory exists 0.089
And there is a GNOME bookmark for the Documents directory 40.769
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 6.035 
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:17:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:17:36_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/5/artifact/build-artifacts/04:17:36_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/5/artifact/build-artifacts/04:17:36_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/5/artifact/build-artifacts/04:17:36_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:37.721
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 8.443
And I log in to a new session in German (de) 48.582
Then the live user's Downloads directory exists 0.096
And there is a GNOME bookmark for the Downloads directory 40.598
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.903 
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:19:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:19:20_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/5/artifact/build-artifacts/04:19:20_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/5/artifact/build-artifacts/04:19:20_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/5/artifact/build-artifacts/04:19:20_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:51.811
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 21.062
And I log in to a new session in German (de) 49.448
Then the live user's Music directory exists 0.116
And there is a GNOME bookmark for the Music directory 41.184
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/localization.feature:16:in `And there is a GNOME bookmark for the Music directory'
features/localization.feature:11:in `And there is a GNOME bookmark for the <dir> directory'
After features/support/hooks.rb:330 6.007 
SCENARIO FAILED: 'Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255), Examples (#3)' (at time 04:21:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:21:18_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:21:18_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:21:18_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:21:18_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product
1:39.532
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 8.274
And I log in to a new session in German (de) 50.744
Then the live user's Pictures directory exists 0.094
And there is a GNOME bookmark for the Pictures directory 40.418
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.928 
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:23:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:23:03_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/5/artifact/build-artifacts/04:23:03_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/5/artifact/build-artifacts/04:23:03_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/5/artifact/build-artifacts/04:23:03_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:36.134
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 8.588
And I log in to a new session in German (de) 48.621
Then the live user's Videos directory exists 0.113
And there is a GNOME bookmark for the Videos directory 38.810
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.741 
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:24:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:24:46_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/5/artifact/build-artifacts/04:24:46_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/5/artifact/build-artifacts/04:24:46_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/5/artifact/build-artifacts/04:24:46_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.227
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.112
When I log in to a new session in Arabic (ar) 3:20.115
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 7.423 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#1)' (at time 04:28:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:28:20_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/5/artifact/build-artifacts/04:28:20_Tails_is_localized_for_every_tier-1_language,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:28:20_Tails_is_localized_for_every_tier-1_language,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:28:20_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.169
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.046
When I log in to a new session in Chinese (zh_CN) 3:20.122
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.401 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#2)' (at time 04:31:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:31:55_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/5/artifact/build-artifacts/04:31:55_Tails_is_localized_for_every_tier-1_language,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:31:55_Tails_is_localized_for_every_tier-1_language,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:31:55_Tails_is_localized_for_every_tier-1_language,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:27.229
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 8.436
When I log in to a new session in English (en) 37.409
Then the keyboard layout is set to "us" 0.428
When the network is plugged 0.099
And Tor is ready 21.248
Then I successfully start the Unsafe Browser 19.301
And I kill the Unsafe Browser 8.189
When I enable the screen keyboard 0.214
Then the screen keyboard works in Tor Browser 51.899
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 7.595 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#3)' (at time 04:34:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:34:29_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/5/artifact/build-artifacts/04:34:29_Tails_is_localized_for_every_tier-1_language,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:34:29_Tails_is_localized_for_every_tier-1_language,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:34:29_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:2.611
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.190
When I log in to a new session in French (fr) 51.160
Then the keyboard layout is set to "fr" 0.303
When the network is plugged 0.089
And Tor is ready 19.954
Then I successfully start the Unsafe Browser 21.255
And I kill the Unsafe Browser 7.583
When I enable the screen keyboard 0.240
Then the screen keyboard works in Tor Browser 1:13.833
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 6.423 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#4)' (at time 04:37:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:37:39_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/5/artifact/build-artifacts/04:37:39_Tails_is_localized_for_every_tier-1_language,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:37:39_Tails_is_localized_for_every_tier-1_language,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:37:39_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
3:8.073
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 21.597
When I log in to a new session in German (de) 45.123
Then the keyboard layout is set to "de" 0.673
When the network is plugged 0.207
And Tor is ready 22.452
Then I successfully start the Unsafe Browser 18.889
And I kill the Unsafe Browser 8.920
When I enable the screen keyboard 0.190
Then the screen keyboard works in Tor Browser 1:10.016
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 7.028 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#5)' (at time 04:40:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:40:54_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/5/artifact/build-artifacts/04:40:54_Tails_is_localized_for_every_tier-1_language,_Examples___5_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:40:54_Tails_is_localized_for_every_tier-1_language,_Examples___5_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:40:54_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:28.774
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.005
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.424
When I log in to a new session in Italian (it) 3:20.349
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.306 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#6)' (at time 04:44:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:44:29_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/5/artifact/build-artifacts/04:44:29_Tails_is_localized_for_every_tier-1_language,_Examples___6_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:44:29_Tails_is_localized_for_every_tier-1_language,_Examples___6_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:44:29_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:28.134
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.002
When I log in to a new session in Persian (fa) 3:20.131
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.345 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#7)' (at time 04:48:04)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:48:04_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/5/artifact/build-artifacts/04:48:04_Tails_is_localized_for_every_tier-1_language,_Examples___7_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:48:04_Tails_is_localized_for_every_tier-1_language,_Examples___7_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:48:04_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:48.862
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.975
When I log in to a new session in Portuguese (pt) 47.960
Then the keyboard layout is set to "pt" 0.388
When the network is plugged 0.101
And Tor is ready 18.095
Then I successfully start the Unsafe Browser 17.011
And I kill the Unsafe Browser 8.599
When I enable the screen keyboard 1.164
Then the screen keyboard works in Tor Browser 1:7.565
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: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 8.106 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#8)' (at time 04:50:59)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:50:59_Tails_is_localized_for_every_tier-1_language,_Examples___8_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:50:59_Tails_is_localized_for_every_tier-1_language,_Examples___8_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:50:59_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
3:2.717
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.142
When I log in to a new session in Russian (ru) 50.808
Then the keyboard layout is set to "ru" 0.335
When the network is plugged 0.110
And Tor is ready 19.682
Then I successfully start the Unsafe Browser 29.131
And I kill the Unsafe Browser 7.690
When I enable the screen keyboard 0.255
Then the screen keyboard works in Tor Browser 1:6.559
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: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 5.788 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#9)' (at time 04:54:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:54:10_Tails_is_localized_for_every_tier-1_language,_Examples___9_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:54:10_Tails_is_localized_for_every_tier-1_language,_Examples___9_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:54:10_Tails_is_localized_for_every_tier-1_language,_Examples___9_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:54:10_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:43.175
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.908
When I log in to a new session in Spanish (es) 49.733
Then the keyboard layout is set to "es" 0.241
When the network is plugged 0.104
And Tor is ready 21.770
Then I successfully start the Unsafe Browser 20.069
And I kill the Unsafe Browser 7.083
When I enable the screen keyboard 0.195
Then the screen keyboard works in Tor Browser 56.069
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 7.426 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#10)' (at time 04:56:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:56:59_Tails_is_localized_for_every_tier-1_language,_Examples___10_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:56:59_Tails_is_localized_for_every_tier-1_language,_Examples___10_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:56:59_Tails_is_localized_for_every_tier-1_language,_Examples___10_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/04:56:59_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:2.123
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 8.610
When I log in to a new session in Turkish (tr) 51.246
Then the keyboard layout is set to "tr" 0.337
When the network is plugged 0.112
And Tor is ready 21.343
Then I successfully start the Unsafe Browser 30.947
And I kill the Unsafe Browser 7.752
When I enable the screen keyboard 0.246
Then the screen keyboard works in Tor Browser 1:1.526
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.991 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#11)' (at time 05:00:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/05:00:09_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/5/artifact/build-artifacts/05:00:09_Tails_is_localized_for_every_tier-1_language,_Examples___11_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/05:00:09_Tails_is_localized_for_every_tier-1_language,_Examples___11_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/05:00:09_Tails_is_localized_for_every_tier-1_language,_Examples___11_.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
4:12.102
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 9.447
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.119
When I try to enable persistence 0.448
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 44.935
When I repair the filesystem of the Persistent Storage 1.335
Then the Welcome Screen tells me that it failed to repair the Persistent Storage 0.062
When I log in to a new session 37.253
And all notifications have disappeared 25.893
# 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.540
And the file "/var/lib/gdm3/post-greeter-whisperback.json" is empty 5.733
When I close the "whisperback" window 3.959
Then the Tor Browser starts 2:1.372
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 9.227 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 06:10:06)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:10:06_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:10:06_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:10:06_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
2:46.484
Scenario Filesystem and I/O errors
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 and stopped at Tails Greeter's login screen 8.893
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 17.670
And Tails detects disk read failures on the boot device 2.117
When I try to enable persistence 0.986
Then the Welcome Screen tells me that my hardware is probably failing 31.205
When I log in to a new session 1:3.031
And all notifications have disappeared 19.451
Then the Tor Browser starts 23.128
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 10.685 
SCENARIO FAILED: 'Filesystem and I/O errors' (at time 06:13:02)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:13:02_Filesystem_and_I_O_errors.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:13:02_Filesystem_and_I_O_errors.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:13:02_Filesystem_and_I_O_errors.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
1:1.975
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 15.225
And I create a persistent partition with the default settings 27.360
Then the "TorConfiguration" tps feature is not enabled 2.995
When the network is plugged 0.111
And the Tor Connection Assistant autostarts 11.380
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 4.902
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.810 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 06:14:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:14:15_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:14:15_Using_Persistent_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:14:15_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:14:15_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
1:24.836
Scenario Chatting with some friend over XMPP
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Before features/support/hooks.rb:513 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 47.352
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.558
Then I see Pidgin's account manager window 5.062
When I create my XMPP account 20.862
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.058
After features/support/hooks.rb:330 5.783 
SCENARIO FAILED: 'Chatting with some friend over XMPP' (at time 06:22:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:22:14_Chatting_with_some_friend_over_XMPP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:22:14_Chatting_with_some_friend_over_XMPP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:22:14_Chatting_with_some_friend_over_XMPP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:22:14_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
55.137
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.009
Before features/support/hooks.rb:513 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 15.654
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.566
Then I see Pidgin's account manager window 7.003
When I create my XMPP account 20.911
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.039
After features/support/hooks.rb:330 6.642 
SCENARIO FAILED: 'Chatting with some friend over XMPP in a multi-user chat' (at time 06:23:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:23:15_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/5/artifact/build-artifacts/06:23:15_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:23:15_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/5/artifact/build-artifacts/06:23:15_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
51.583
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.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 13.415
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.112
Then I see Pidgin's account manager window 6.206
And I create my XMPP account 20.849
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.059
After features/support/hooks.rb:330 5.532 
SCENARIO FAILED: 'Connecting to the tails multi-user chat with my XMPP account' (at time 06:24:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:24:13_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/5/artifact/build-artifacts/06:24:13_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:24:13_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/5/artifact/build-artifacts/06:24:13_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:55.946
Scenario Using a persistent Pidgin configuration
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 have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.812
And the network is plugged 0.349
And Tor is ready 49.647
And available upgrades have been checked 0.060
And all notifications have disappeared 5.935
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.538
Then I see Pidgin's account manager window 6.546
When I create my XMPP account 21.056
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.040
After features/support/hooks.rb:330 6.073 
SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 06:26:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:26:15_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:26:15_Using_a_persistent_Pidgin_configuration.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:26:15_Using_a_persistent_Pidgin_configuration.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:26:15_Using_a_persistent_Pidgin_configuration.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
9.501
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.002
Steps
Given I have started Tails from DVD without network and logged in 9.416
Then there are no unexpected messages of priority "err" or higher in the journal 0.085
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": "579",
    "_BOOT_ID": "0a2e7a1bc2554056b423d1a2d6c698e5",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "579",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748344404824117",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "777a930ef10449b4bad0ffed5b8eeaec",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=a42e7f47fcc04090ab17a7d02e1bb533;i=351;b=0a2e7a1bc2554056b423d1a2d6c698e5;m=bd35d0;t=6361c27322f69;x=3a2a535941b807f2",
    "__MONOTONIC_TIMESTAMP": "12400080",
    "__REALTIME_TIMESTAMP": "1748344404848489",
    "__SEQNUM": "849",
    "__SEQNUM_ID": "a42e7f47fcc04090ab17a7d02e1bb533"
  },
  {
    "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": "579",
    "_BOOT_ID": "0a2e7a1bc2554056b423d1a2d6c698e5",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "579",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748344404824148",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "777a930ef10449b4bad0ffed5b8eeaec",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=a42e7f47fcc04090ab17a7d02e1bb533;i=353;b=0a2e7a1bc2554056b423d1a2d6c698e5;m=bd3695;t=6361c2732302e;x=b9f02313a011b1a8",
    "__MONOTONIC_TIMESTAMP": "12400277",
    "__REALTIME_TIMESTAMP": "1748344404848686",
    "__SEQNUM": "851",
    "__SEQNUM_ID": "a42e7f47fcc04090ab17a7d02e1bb533"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2244",
    "SYSLOG_TIMESTAMP": "May 27 11:13:33 ",
    "_BOOT_ID": "0a2e7a1bc2554056b423d1a2d6c698e5",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2244",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748344413386057",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "ed411da7e4ea48a7a60bba37f1b7cf88",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=a42e7f47fcc04090ab17a7d02e1bb533;i=403;b=0a2e7a1bc2554056b423d1a2d6c698e5;m=13f7bfa;t=6361c27b47593;x=d67cf83d7c14f363",
    "__MONOTONIC_TIMESTAMP": "20937722",
    "__REALTIME_TIMESTAMP": "1748344413386131",
    "__SEQNUM": "1027",
    "__SEQNUM_ID": "a42e7f47fcc04090ab17a7d02e1bb533"
  },
  {
    "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": "579",
    "_BOOT_ID": "0a2e7a1bc2554056b423d1a2d6c698e5",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "579",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748344603481899",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "777a930ef10449b4bad0ffed5b8eeaec",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=a42e7f47fcc04090ab17a7d02e1bb533;i=8db;b=0a2e7a1bc2554056b423d1a2d6c698e5;m=6897fe2;t=6361c33091757;x=f29c758e9da08815",
    "__MONOTONIC_TIMESTAMP": "109674466",
    "__REALTIME_TIMESTAMP": "1748344603481943",
    "__SEQNUM": "2267",
    "__SEQNUM_ID": "a42e7f47fcc04090ab17a7d02e1bb533"
  },
  {
    "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": "579",
    "_BOOT_ID": "0a2e7a1bc2554056b423d1a2d6c698e5",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "579",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748344603481924",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "777a930ef10449b4bad0ffed5b8eeaec",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=a42e7f47fcc04090ab17a7d02e1bb533;i=8dd;b=0a2e7a1bc2554056b423d1a2d6c698e5;m=6898177;t=6361c330918ed;x=265f66147e40156b",
    "__MONOTONIC_TIMESTAMP": "109674871",
    "__REALTIME_TIMESTAMP": "1748344603482349",
    "__SEQNUM": "2269",
    "__SEQNUM_ID": "a42e7f47fcc04090ab17a7d02e1bb533"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "17829",
    "SYSLOG_TIMESTAMP": "May 27 11:16:50 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "0a2e7a1bc2554056b423d1a2d6c698e5",
    "_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": "17829",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748344610103097",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "fcec7993706549719b26415a7acea307",
    "_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=a42e7f47fcc04090ab17a7d02e1bb533;i=1227;b=0a2e7a1bc2554056b423d1a2d6c698e5;m=6ee87d1;t=6361c336e1f46;x=157dbd99749bec20",
    "__MONOTONIC_TIMESTAMP": "116295633",
    "__REALTIME_TIMESTAMP": "1748344610103110",
    "__SEQNUM": "4647",
    "__SEQNUM_ID": "a42e7f47fcc04090ab17a7d02e1bb533"
  }
].
<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 6.049 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from DVD' (at time 06:31:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:31:46_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/5/artifact/build-artifacts/06:31:46_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:31:46_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/5/artifact/build-artifacts/06:31:46_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
15.819
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.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.700
Then there are no unexpected messages of priority "err" or higher in the journal 0.118
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": "709",
    "_BOOT_ID": "adfa39e874034f09a31bceb1163d644a",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "709",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748346603447240",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "234dda1e793a4ffdab13bb0f2be0b3c5",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=5d22e3e30b3d4b4ab6f44705f7882736;i=380;b=adfa39e874034f09a31bceb1163d644a;m=e792d4;t=6361caa3e23dd;x=584ebf4ab8a9375",
    "__MONOTONIC_TIMESTAMP": "15176404",
    "__REALTIME_TIMESTAMP": "1748346603447261",
    "__SEQNUM": "896",
    "__SEQNUM_ID": "5d22e3e30b3d4b4ab6f44705f7882736"
  },
  {
    "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": "709",
    "_BOOT_ID": "adfa39e874034f09a31bceb1163d644a",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "709",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748346603447638",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "234dda1e793a4ffdab13bb0f2be0b3c5",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=5d22e3e30b3d4b4ab6f44705f7882736;i=382;b=adfa39e874034f09a31bceb1163d644a;m=e79450;t=6361caa3e255a;x=212d5d18707cca4",
    "__MONOTONIC_TIMESTAMP": "15176784",
    "__REALTIME_TIMESTAMP": "1748346603447642",
    "__SEQNUM": "898",
    "__SEQNUM_ID": "5d22e3e30b3d4b4ab6f44705f7882736"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2485",
    "SYSLOG_TIMESTAMP": "May 27 11:50:11 ",
    "_BOOT_ID": "adfa39e874034f09a31bceb1163d644a",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2485",
    "_RUNTIME_SCOPE": "system",
    "_SOURCE_REALTIME_TIMESTAMP": "1748346611908853",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=5d22e3e30b3d4b4ab6f44705f7882736;i=40c;b=adfa39e874034f09a31bceb1163d644a;m=168c2c6;t=6361caabf53d0;x=ca256dbf451c2f1b",
    "__MONOTONIC_TIMESTAMP": "23642822",
    "__REALTIME_TIMESTAMP": "1748346611913680",
    "__SEQNUM": "1036",
    "__SEQNUM_ID": "5d22e3e30b3d4b4ab6f44705f7882736"
  },
  {
    "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": "709",
    "_BOOT_ID": "adfa39e874034f09a31bceb1163d644a",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "709",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748346762517426",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "234dda1e793a4ffdab13bb0f2be0b3c5",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=5d22e3e30b3d4b4ab6f44705f7882736;i=e7d;b=adfa39e874034f09a31bceb1163d644a;m=a03c1ef;t=6361cb3b95c42;x=1441c9eebdbf6ff9",
    "__MONOTONIC_TIMESTAMP": "168018415",
    "__REALTIME_TIMESTAMP": "1748346762517570",
    "__SEQNUM": "3709",
    "__SEQNUM_ID": "5d22e3e30b3d4b4ab6f44705f7882736"
  },
  {
    "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": "709",
    "_BOOT_ID": "adfa39e874034f09a31bceb1163d644a",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "709",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748346762517457",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "234dda1e793a4ffdab13bb0f2be0b3c5",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=5d22e3e30b3d4b4ab6f44705f7882736;i=e7f;b=adfa39e874034f09a31bceb1163d644a;m=a03c31d;t=6361cb3b95d70;x=8375e3c31ca965d5",
    "__MONOTONIC_TIMESTAMP": "168018717",
    "__REALTIME_TIMESTAMP": "1748346762517872",
    "__SEQNUM": "3711",
    "__SEQNUM_ID": "5d22e3e30b3d4b4ab6f44705f7882736"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "22495",
    "SYSLOG_TIMESTAMP": "May 27 11:52:50 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "adfa39e874034f09a31bceb1163d644a",
    "_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": "22495",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748346770271919",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "872d336c2e3a4a0f8f34fde09ce0cf57",
    "_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=5d22e3e30b3d4b4ab6f44705f7882736;i=1875;b=adfa39e874034f09a31bceb1163d644a;m=a7a1484;t=6361cb42faed7;x=ef7f250b705dae2e",
    "__MONOTONIC_TIMESTAMP": "175772804",
    "__REALTIME_TIMESTAMP": "1748346770271959",
    "__SEQNUM": "6261",
    "__SEQNUM_ID": "5d22e3e30b3d4b4ab6f44705f7882736"
  }
].
<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:32:07)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:32:07_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/5/artifact/build-artifacts/06:32:07_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/5/artifact/build-artifacts/06:32:07_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/5/artifact/build-artifacts/06:32:07_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
50.626
Scenario I can shutdown Tails via the system menu
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.929
When I request a shutdown using the system menu 37.696
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.481 
SCENARIO FAILED: 'I can shutdown Tails via the system menu' (at time 06:33:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:33:03_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/5/artifact/build-artifacts/06:33:03_I_can_shutdown_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:33:03_I_can_shutdown_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:33:03_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
50.436
Scenario I can reboot Tails via the system menu
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.696
When I request a reboot using the system menu 37.739
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 6.152 
SCENARIO FAILED: 'I can reboot Tails via the system menu' (at time 06:33:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:33:59_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/5/artifact/build-artifacts/06:33:59_I_can_reboot_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:33:59_I_can_reboot_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:33:59_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:52.210
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.294
When I connect to an SFTP server on the Internet 1:51.916
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.037
After features/support/hooks.rb:330 5.072 
SCENARIO FAILED: 'Connecting to an SFTP server on the Internet using the GNOME "Connect to Server" feature' (at time 06:36:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:36:57_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/5/artifact/build-artifacts/06:36:57_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/5/artifact/build-artifacts/06:36:57_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/5/artifact/build-artifacts/06:36:57_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
33.548
Scenario Starting Tor Connection before connecting to Wi-Fi
Steps
When I start "Tor Connection" via GNOME Activities Overview 10.150
Then the Tor Connection Assistant reports that I am not connected to a local network 3.518
When I plug a Wi-Fi adapter 1.476
Then Tor Connection suggests me to connect to Wi-Fi 1.079
And I click on the Wi-Fi settings 1.170
And The Wi-Fi settings are displayed 16.152
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.738 
SCENARIO FAILED: 'Starting Tor Connection before connecting to Wi-Fi' (at time 06:39:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:39:53_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/5/artifact/build-artifacts/06:39:53_Starting_Tor_Connection_before_connecting_to_Wi-Fi.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:39:53_Starting_Tor_Connection_before_connecting_to_Wi-Fi.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:39:53_Starting_Tor_Connection_before_connecting_to_Wi-Fi.journal
After features/support/hooks.rb:100 0.000
Feature: Tor Connection helps the user in connecting to Tor
Tags: @product
1:33.334
Scenario I can use a network with captive portal
Steps
Given the Tor network and default bridges are blocked 2.404
And the network is plugged 0.062
And I make sure time sync before Tor connects indicates a captive portal 1.284
And the Tor Connection Assistant autostarts 5.987
When I choose to connect to Tor automatically 1.677
And I click "Connect to Tor" 1.254
Then the Tor Connection Assistant fails to connect to Tor 27.918
And the Tor Connection Assistant knows that it's not the time sync that failed 10.774
And the Tor Connection Assistant knows that there might be a captive portal 0.161
When I open the Unsafe Browser from Tor Connection 19.379
And I log-in to the Captive Portal 16.162
And I close the Unsafe Browser 0.121
And the Tor network and default bridges are unblocked 2.890
And I allow time sync before Tor connects to work again 0.252
And I click "Connect to Tor" 3.000
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:838:in `/^(?:I click "Connect to Tor"|I retry connecting to Tor)$/'
features/tor_connection.feature:65:in `And I click "Connect to Tor"'
Then I wait until Tor is ready 0.000
After features/support/hooks.rb:330 5.742 
SCENARIO FAILED: 'I can use a network with captive portal' (at time 06:54:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:54:31_I_can_use_a_network_with_captive_portal.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:54:31_I_can_use_a_network_with_captive_portal.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:54:31_I_can_use_a_network_with_captive_portal.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/06:54:31_I_can_use_a_network_with_captive_portal.journal
After features/support/hooks.rb:100 0.001
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
53.404
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.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 14.759
Then the live user's Downloads directory exists 0.061
And there is a GNOME bookmark for the Downloads directory 38.583
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.047
After features/support/hooks.rb:330 5.751 
SCENARIO FAILED: 'The Downloads directory is usable in Tor Browser' (at time 07:02:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:02:59_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/5/artifact/build-artifacts/07:02:59_The_Downloads_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:02:59_The_Downloads_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:02:59_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:16.450
Scenario Downloading files with the Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:513 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.197
When I start the Tor Browser 33.370
Then the Tor Browser loads the startup page 2.249
When I download some file in the Tor Browser to the Downloads directory 27.633
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.048
After features/support/hooks.rb:330 8.950 
SCENARIO FAILED: 'Downloading files with the Tor Browser' (at time 07:04:21)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:04:21_Downloading_files_with_the_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:04:21_Downloading_files_with_the_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:04:21_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
46.158
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 13.248
When I start the Tor Browser 30.323
Then the Tor Browser uses all expected TBB shared libraries 2.586
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.416 
SCENARIO FAILED: 'The Tor Browser uses TBB's shared libraries' (at time 07:10:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:10:35_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/5/artifact/build-artifacts/07:10:35_The_Tor_Browser_uses_TBB_s_shared_libraries.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:10:35_The_Tor_Browser_uses_TBB_s_shared_libraries.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:10:35_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:36.506
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.299
And the network is plugged 0.095
And I successfully configure Tor 23.596
And available upgrades have been checked 2.316
And all notifications have disappeared 6.536
And there is a GNOME bookmark for the Persistent directory 2.242
When I start the Tor Browser 25.578
And I download some file in the Tor Browser to the Persistent directory 20.840
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 11.914 
SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 07:15:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:15:58_The_Persistent_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:15:58_The_Persistent_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:15:58_The_Persistent_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:15:58_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
48.297
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.007
Steps
Given I have started Tails from DVD without network and logged in 9.609
Then the live user's Documents directory exists 0.088
And there is a GNOME bookmark for the Documents directory 38.599
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 7.102 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#1)' (at time 07:16:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:16:58_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/5/artifact/build-artifacts/07:16:58_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:16:58_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/5/artifact/build-artifacts/07:16:58_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
49.394
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.015
Steps
Given I have started Tails from DVD without network and logged in 11.534
Then the live user's Downloads directory exists 0.093
And there is a GNOME bookmark for the Downloads directory 37.766
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.844 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#2)' (at time 07:17:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:17:55_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/5/artifact/build-artifacts/07:17:55_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:17:55_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/5/artifact/build-artifacts/07:17:55_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
46.669
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.008
Steps
Given I have started Tails from DVD without network and logged in 9.314
Then the live user's Music directory exists 0.069
And there is a GNOME bookmark for the Music directory 37.285
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 5.764 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#3)' (at time 07:18:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:18:47_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/5/artifact/build-artifacts/07:18:47_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:18:47_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/5/artifact/build-artifacts/07:18:47_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
48.360
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.390
Then the live user's Pictures directory exists 0.088
And there is a GNOME bookmark for the Pictures directory 38.881
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.968 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#4)' (at time 07:19:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:19:41_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/5/artifact/build-artifacts/07:19:41_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:19:41_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/5/artifact/build-artifacts/07:19:41_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
49.080
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 10.407
Then the live user's Videos directory exists 0.085
And there is a GNOME bookmark for the Videos directory 38.587
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.715 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#5)' (at time 07:20:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:20:37_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/5/artifact/build-artifacts/07:20:37_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:20:37_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/5/artifact/build-artifacts/07:20:37_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 Tor Browser
Tags: @product
5:50.782
Scenario Persistent browser bookmarks
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.616
And all tps features are active 2.731
And all persistent filesystems have safe access rights 0.270
And all persistence configuration files have safe access rights 0.554
And all persistent directories have safe access rights 3.362
When I start the Tor Browser in offline mode 35.395
And I add a bookmark to eff.org in the Tor Browser 13.571
And I cold reboot the computer 16.355
And the computer reboots Tails 2:5.148
And I enable persistence 22.784
And I log in to a new session 1:1.467
And all notifications have disappeared 9.873
And I start the Tor Browser in offline mode 37.433
Then the Tor Browser has a bookmark to eff.org 10.217
cannot 
cannot find TorBrowserEFFBookmark.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:515:in `/^the Tor Browser has a bookmark to eff.org$/'
features/torified_browsing.feature:147:in `Then the Tor Browser has a bookmark to eff.org'
After features/support/hooks.rb:330 9.135 
SCENARIO FAILED: 'Persistent browser bookmarks' (at time 07:26:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:26:33_Persistent_browser_bookmarks.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:26:33_Persistent_browser_bookmarks.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:26:33_Persistent_browser_bookmarks.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:26:33_Persistent_browser_bookmarks.journal
After features/support/hooks.rb:100 0.012
Feature: Browsing the web using the Unsafe Browser
Tags: @product @not_release_blocker
1:0.120
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.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.172
When I successfully start the Unsafe Browser 25.904
# 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.005 
Slept for 10 seconds
And I try to start the Unsafe Browser 0.383
Then I see a warning about another instance already running 10.655
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 8.331 
SCENARIO FAILED: 'Starting a second instance of the Unsafe Browser results in an error message being shown' (at time 07:36:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:36:31_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/5/artifact/build-artifacts/07:36:31_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/5/artifact/build-artifacts/07:36:31_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/5/artifact/build-artifacts/07:36:31_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
22.611
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 8.301
And I cancel the GNOME authentication prompt 2.880
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 5.399
And I open this VeraCrypt volume in GNOME Files 5.641
Then I see the expected contents in this VeraCrypt volume 0.296
When I lock the currently opened VeraCrypt volume 0.092
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.567 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume' (at time 07:41:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:41:41_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/5/artifact/build-artifacts/07:41:41_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/5/artifact/build-artifacts/07:41:41_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/5/artifact/build-artifacts/07:41:41_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
24.284
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 11.440
And I cancel the GNOME authentication prompt 2.443
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 5.465
And I open this VeraCrypt volume in GNOME Files 4.592
Then I see the expected contents in this VeraCrypt volume 0.220
When I lock the currently opened VeraCrypt volume 0.123
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.744 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:42:21)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:42:21_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/5/artifact/build-artifacts/07:42:21_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/5/artifact/build-artifacts/07:42:21_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/5/artifact/build-artifacts/07:42:21_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
30.773
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 16.605
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 8.667
And I open this VeraCrypt volume in GNOME Files 4.948
Then I see the expected contents in this VeraCrypt volume 0.473
When I lock the currently opened VeraCrypt file container 0.078
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.477 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM' (at time 07:43:07)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:43:07_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/5/artifact/build-artifacts/07:43:07_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/5/artifact/build-artifacts/07:43:07_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/5/artifact/build-artifacts/07:43:07_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
43.225
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 28.941
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 8.867
And I open this VeraCrypt volume in GNOME Files 4.844
Then I see the expected contents in this VeraCrypt volume 0.483
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: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 8.065 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container' (at time 07:44:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:44:05_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/5/artifact/build-artifacts/07:44:05_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:44:05_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/5/artifact/build-artifacts/07:44:05_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.018
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
25.663
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 7.189
And I cancel the GNOME authentication prompt 2.710
And I unlock and mount this VeraCrypt volume with GNOME Disks 10.562
And I open this VeraCrypt volume in GNOME Files 4.630
Then I see the expected contents in this VeraCrypt volume 0.489
When I lock the currently opened VeraCrypt volume 0.081
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.732 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 07:44:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:44:51_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/5/artifact/build-artifacts/07:44:51_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/5/artifact/build-artifacts/07:44:51_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/5/artifact/build-artifacts/07:44:51_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
28.397
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 11.645
And I cancel the GNOME authentication prompt 2.208
And I unlock and mount this VeraCrypt volume with GNOME Disks 9.165
And I open this VeraCrypt volume in GNOME Files 4.815
Then I see the expected contents in this VeraCrypt volume 0.465
When I lock the currently opened VeraCrypt volume 0.096
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.395 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:45:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:45:35_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/5/artifact/build-artifacts/07:45:35_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/5/artifact/build-artifacts/07:45:35_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/5/artifact/build-artifacts/07:45:35_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
51.538
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 24.485
And I unlock and mount this VeraCrypt file container with GNOME Disks 22.336
And I open this VeraCrypt volume in GNOME Files 4.116
Then I see the expected contents in this VeraCrypt volume 0.506
When I lock the currently opened VeraCrypt file container 0.093
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.414 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 07:46:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:46:42_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/5/artifact/build-artifacts/07:46:42_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/5/artifact/build-artifacts/07:46:42_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/5/artifact/build-artifacts/07:46:42_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.016
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
52.750
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 27.492
And I unlock and mount this VeraCrypt file container with GNOME Disks 20.610
And I open this VeraCrypt volume in GNOME Files 4.016
Then I see the expected contents in this VeraCrypt volume 0.517
When I lock the currently opened VeraCrypt file container 0.113
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.441 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 07:47:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:47:51_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/5/artifact/build-artifacts/07:47:51_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:47:51_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:47:51_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.015
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
40.119
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.996
And I unlock and mount this VeraCrypt file container with GNOME Disks 18.551
And I open this VeraCrypt volume in GNOME Files 4.032
Then I see the expected contents in this VeraCrypt volume 0.460
When I lock the currently opened VeraCrypt file container 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: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.447 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM' (at time 07:48:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/5/artifact/build-artifacts/07:48:46_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/5/artifact/build-artifacts/07:48:46_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/5/artifact/build-artifacts/07:48:46_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/5/artifact/build-artifacts/07:48:46_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000