Project Number Date
test_Tails_ISO_feature-trixie 12 03 Jun 2025, 06:57

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
25.769
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 8.252
And I wait until Tor is ready 5.563
When I disconnect the network through GNOME 11.953
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.383 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:36:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/00:36:03_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/12/artifact/build-artifacts/00:36:03_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/00:36:03_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/12/artifact/build-artifacts/00:36:03_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.056
Feature: Using Tor bridges and pluggable transports
Tags: @product
23.679
Scenario Reconnecting from an unblocked network to a blocked network displays an error
Steps
Given I configure a direct connection in the Tor Connection Assistant 7.212
And I wait until Tor is ready 4.424
And I disconnect the network through GNOME 12.041
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.425 
SCENARIO FAILED: 'Reconnecting from an unblocked network to a blocked network displays an error' (at time 00:36:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/00:36:50_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/12/artifact/build-artifacts/00:36:50_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/12/artifact/build-artifacts/00:36:50_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/12/artifact/build-artifacts/00:36:50_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.journal
After features/support/hooks.rb:100 0.050
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
17.231
Scenario Erasure of memory freed by killed userspace processes
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 9.650
And I prepare Tails for memory erasure tests 0.887
When I start a process allocating 128 MiB of memory with a known pattern 2.350
Then patterns cover at least 128 MiB in the guest's memory 4.343
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.654 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:38:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/00:38:10_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/12/artifact/build-artifacts/00:38:10_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/00:38:10_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/00:38:10_Erasure_of_memory_freed_by_killed_userspace_processes.journal
After features/support/hooks.rb:100 0.000
Feature: Additional software
Tags: @product @check_tor_leaks @slow
11:23.493
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.004
Before features/support/hooks.rb:513 0.005
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:14.996
And I update APT using apt 12.169
And I install "popularity-contest" using apt 25.925
Then I am proposed to add the "popularity-contest" package to my Additional Software 8.556
When I create a persistent storage and activate the Additional Software feature 25.035
Then Additional Software is correctly configured for package "popularity-contest" 3.518
When I shutdown Tails and wait for the computer to power off 14.448
And I start Tails from USB drive "__internal" with network unplugged 1:49.455
And I enable persistence 28.672
And I log in to a new session 31.612
And the Additional Software installation service has started 47.226
Then I am notified that the installation succeeded 5:1.873
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.038
After features/support/hooks.rb:330 10.584 
SCENARIO FAILED: 'I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails' (at time 01:34:14)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/01:34:14_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/12/artifact/build-artifacts/01:34:14_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/12/artifact/build-artifacts/01:34:14_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.027
Feature: Additional software
Tags: @product @check_tor_leaks @slow
25:33.638
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.004
Before features/support/hooks.rb:513 0.005
Steps
Given a computer 0.210
And I start Tails from USB drive "__internal" and I login with an administration password 3:16.018
And I update APT using apt 11.766
When I install "makepp" using apt 22:5.643
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.034
After features/support/hooks.rb:330 5.450 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:59:58)
Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/01:59:58_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/12/artifact/build-artifacts/01:59:58_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/12/artifact/build-artifacts/01:59:58_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/12/artifact/build-artifacts/01:59:58_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/12/artifact/build-artifacts/01:59:58_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/12/artifact/build-artifacts/01:59:58_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/12/artifact/build-artifacts/01:59:58_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/12/artifact/build-artifacts/01:59:58_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.026
Feature: Additional software
Tags: @product @check_tor_leaks @slow
5:33.933
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.010
Before features/support/hooks.rb:513 0.007
Steps
Given a computer 0.183
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 4:41.262
When I uninstall "popularity-contest" using apt 25.012
And I accept removing "popularity-contest" from Additional Software 0.668
Then "popularity-contest" is not in the list of Additional Software 1.088
When I start Synaptic 25.718
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.048
After features/support/hooks.rb:330 5.685 
SCENARIO FAILED: 'My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic' (at time 02:05:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:05:38_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/12/artifact/build-artifacts/02:05:38_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/12/artifact/build-artifacts/02:05:38_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/12/artifact/build-artifacts/02:05:38_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/12/artifact/build-artifacts/02:05:38_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/12/artifact/build-artifacts/02:05:38_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/12/artifact/build-artifacts/02:05:38_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/12/artifact/build-artifacts/02:05:38_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/12/artifact/build-artifacts/02:05:38_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.007
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
3:50.732
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:513 0.005
Steps
Given a computer 0.208
And I start Tails from USB drive "__internal" with network unplugged 1:52.020
And I enable persistence 16.336
And I remove the "cowsay" deb files from the APT cache 0.062
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.087
And I log in to a new session 44.777
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 19.787
And I can open the Additional Software log file from the notification 37.453
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Show Log' roleName='button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/additional_software_packages.rb:41:in `click_gnome_shell_notification_button'
./features/step_definitions/additional_software_packages.rb:169:in `/^I can open the Additional Software log file from the notification$/'
features/additional_software_packages.feature:130:in `And I can open the Additional Software log file from the notification'
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:521 0.039
After features/support/hooks.rb:330 6.318 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 02:24:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:24:47_I_am_notified_when_Additional_Software_fails_to_install_a_package.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:24:47_I_am_notified_when_Additional_Software_fails_to_install_a_package.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:24:47_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:24:47_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:24:47_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:24:47_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:24:47_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:24:47_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:24:47_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.008
Feature: Upgrading an old Tails USB installation
Tags: @product
2:26.803
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.829
When I start Tails from USB drive "old" with network unplugged 1:55.676
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 5.877 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:27:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:27:20_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:27:20_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:27:20_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/12/artifact/build-artifacts/02:27:20_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.022
Feature: Upgrading an old Tails USB installation
Tags: @product
1:24.410
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.005
Steps
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:24.209
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.856 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:28:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:28:51_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/12/artifact/build-artifacts/02:28:51_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:28:51_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:28:51_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.009
Feature: Upgrading an old Tails USB installation
Tags: @product
1:22.611
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:22.402
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.704 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:30:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:30:19_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/12/artifact/build-artifacts/02:30:19_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/12/artifact/build-artifacts/02:30:19_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/12/artifact/build-artifacts/02:30:19_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.009
Feature: Upgrading an old Tails USB installation
Tags: @product
2:18.738
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.005
Steps
Given a computer 0.240
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.497
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 7.384 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:35:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:35:36_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/12/artifact/build-artifacts/02:35:36_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/12/artifact/build-artifacts/02:35:36_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/12/artifact/build-artifacts/02:35:36_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.009
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
23:14.401
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.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 37.406
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.113
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.413
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.442
When the network is plugged 0.094
And Tor is ready 22.270
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:13.221
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.863 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:58:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:58:57_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/12/artifact/build-artifacts/02:58:57_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:58:57_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/02:58:57_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
22:46.467
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.964
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
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.085
And Tor is ready 21.163
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:11.787
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.484 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:21:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:21:50_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/12/artifact/build-artifacts/03:21:50_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:21:50_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:21:50_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000
Feature: Emergency shutdown
Tags: @product @not_release_blocker
2:6.803
Scenario Tails erases memory on DVD boot medium removal: overlayfs read-write branch
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD without network and logged in 9.848
And I prepare Tails for memory erasure tests 0.999
And I fill a 128 MiB file with a known pattern on the root filesystem 21.970
And patterns cover at least 128 MiB in the guest's memory 3.448 
Pattern coverage: 100.000% (128 MiB out of 128 MiB reference memory)
When I eject the boot medium 0.522
And I wait for Tails to finish wiping the memory 1:30.013
cannot 
cannot find MemoryWipeCompleted.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/erase_memory.rb:232:in `/^I wait for Tails to finish wiping the memory$/'
features/emergency_shutdown.feature:22:in `And I wait for Tails to finish wiping the memory'
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:330 10.561 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: overlayfs read-write branch' (at time 03:26:33)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:26:33_Tails_erases_memory_on_DVD_boot_medium_removal:_overlayfs_read-write_branch.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:26:33_Tails_erases_memory_on_DVD_boot_medium_removal:_overlayfs_read-write_branch.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:26:33_Tails_erases_memory_on_DVD_boot_medium_removal:_overlayfs_read-write_branch.journal
After features/support/hooks.rb:100 0.000
Feature: Emergency shutdown
Tags: @product @not_release_blocker
1:58.896
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.004
Steps
Given I have started Tails from DVD without network and logged in 9.520
And I prepare Tails for memory erasure tests 0.942
And I plug and mount a 128 MiB USB drive with a vfat filesystem 10.095
And I fill the USB drive with a known pattern 3.370
And I read the content of the test FS 0.070
And patterns cover at least 90% of the test FS size in the guest's memory 4.407 
Pattern coverage: 100.003% (127 MiB out of 127 MiB reference memory)
When I eject the boot medium 0.310
And I wait for Tails to finish wiping the memory 1:30.181
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.707 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: vfat' (at time 03:28:43)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:28:43_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:28:43_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:28:43_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:29.766
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.005
Steps
Given I have started Tails from DVD without network and logged in 9.858
And I prepare Tails for memory erasure tests 0.870
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 44.436
And I fill the USB drive with a known pattern 1.482
And I read the content of the test FS 0.085
And patterns cover at least 99% of the test FS size in the guest's memory 2.497 
Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)
When I eject the boot medium 0.507
And I wait for Tails to finish wiping the memory 1:30.026
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.524 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 03:31:23)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:31:23_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:31:23_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/12/artifact/build-artifacts/03:31:23_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.000
Feature: Backing up the persistent storage
Tags: @product
1:39.519
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.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 41.434
# The volume cannot be in use when GuestFs clones it, which we do below
And I shutdown Tails and wait for the computer to power off 10.513
And I clone USB drive "__internal" to a temporary USB drive "backup" 1.829
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.973
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.053
When I start Tails' custom backup tool 5.782
Then the backup tool displays "Plug in your backup Tails USB stick" 0.367
When I plug USB drive "backup" 2.728
And I give the Persistent Storage on drive "backup" its own UUID 0.187
And I click "Retry" in the backup tool 1.320
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.878
When I click "Back Up" in the backup tool 1.246
And I enter my persistent storage passphrase into the polkit prompt 21.204
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.882 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 03:37:20)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:37:20_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:37:20_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/12/artifact/build-artifacts/03:37:20_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.144
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
0.084
Scenario Getting a DHCP lease with the default NetworkManager connection
Steps
Then the hostname should not have been leaked on the network 0.084
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.413 
SCENARIO FAILED: 'Getting a DHCP lease with the default NetworkManager connection' (at time 03:38:45)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:38:45_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/12/artifact/build-artifacts/03:38:45_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.pcap
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:38:45_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:38:45_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:38:45_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.039
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
0.937
Scenario Getting a DHCP lease with a manually configured NetworkManager connection
Steps
When I add a wired DHCP NetworkManager connection called "manually-added-con" 0.293
And I switch to the "manually-added-con" NetworkManager connection 0.481
Then the hostname should not have been leaked on the network 0.161
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.246 
SCENARIO FAILED: 'Getting a DHCP lease with a manually configured NetworkManager connection' (at time 03:39:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:39:54_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/12/artifact/build-artifacts/03:39:54_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.pcap
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:39:54_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:39:54_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:39:54_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.062
Feature: Hardware failures
Tags: @product
2:54.102
Scenario Outline GPT backup corruption with a persistent partition
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 with a persistent partition and stopped at Tails Greeter's login screen 11.637
And I corrupt the boot device's GPT backup header 0.663
And I power off the computer 0.333
When I start the computer 1.033
Then the computer boots Tails 2:2.750
When I log in to a new session 26.281
And all notifications have disappeared 11.143
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.259
<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.124 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 03:57:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:57:41_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/12/artifact/build-artifacts/03:57:41_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:57:41_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/03:57:41_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:100 0.008
Feature: Hardware failures
Tags: @product
2:56.545
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.369
And I corrupt the boot device's GPT backup partition table 0.427
And I power off the computer 0.336
When I start the computer 1.050
Then the computer boots Tails 2:5.932
When I log in to a new session 20.820
And all notifications have disappeared 18.281
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.327
<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 7.316 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 04:00:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:00:44_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/12/artifact/build-artifacts/04:00:44_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:00:44_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:00:44_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:100 0.043
Feature: Hardware failures
Tags: @product
3:39.936
Scenario GPT backup corruption without a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given a computer 0.177
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.044
And I plug USB drive "temp" 1.048
And I write the Tails USB image to disk "temp" 32.332
When I start Tails from USB drive "temp" with network unplugged 2:27.382
Then Tails is running from USB drive "temp" 0.339
And the Greeter forbids creating a persistent partition 0.086
When I log in to a new session 25.928
And all notifications have disappeared 12.349
Then I am recommended to reinstall Tails due to partitioning errors 0.248
<"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.306 
SCENARIO FAILED: 'GPT backup corruption without a persistent partition' (at time 04:04:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:04:31_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/12/artifact/build-artifacts/04:04:31_GPT_backup_corruption_without_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:04:31_GPT_backup_corruption_without_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:04:31_GPT_backup_corruption_without_a_persistent_partition.journal
After features/support/hooks.rb:100 0.105
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
9.622
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.005
Steps
Given I have started Tails from DVD without network and logged in 9.344
Then the keys trusted by APT are valid for the next 3 months 0.278
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.612 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 04:14:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:14:52_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/12/artifact/build-artifacts/04:14:52_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:14:52_The_included_APT_repository_keys_are_up-to-date.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:14:52_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product
1:39.897
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.005
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 12.917
And I log in to a new session in German (de) 49.101
Then the live user's Documents directory exists 0.117
And there is a GNOME bookmark for the Documents directory 37.760
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Documents' roleName='label'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/common_steps.rb:1225:in `/^there is a GNOME bookmark for the (.*) directory$/'
features/localization.feature:14:in `And there is a GNOME bookmark for the Documents directory'
features/localization.feature:11:in `And there is a GNOME bookmark for the <dir> directory'
After features/support/hooks.rb:330 5.620 
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:16:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:16:37_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/12/artifact/build-artifacts/04:16:37_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/12/artifact/build-artifacts/04:16:37_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/12/artifact/build-artifacts/04:16:37_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:30.342
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.005
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.466
And I log in to a new session in German (de) 43.930
Then the live user's Downloads directory exists 0.081
And there is a GNOME bookmark for the Downloads directory 37.864
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.655 
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:18:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:18:13_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/12/artifact/build-artifacts/04:18:13_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/12/artifact/build-artifacts/04:18:13_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/12/artifact/build-artifacts/04:18:13_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:29.933
Scenario Outline Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255)
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 7.801
And I log in to a new session in German (de) 44.775
Then the live user's Pictures directory exists 0.115
And there is a GNOME bookmark for the Pictures directory 37.241
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.856 
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:21:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:21:02_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/12/artifact/build-artifacts/04:21:02_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/12/artifact/build-artifacts/04:21:02_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/12/artifact/build-artifacts/04:21:02_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 @doc @slow @not_release_blocker
3:28.481
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 7.946
When I log in to a new session in Arabic (ar) 3:20.534
cannot 
cannot find GnomeApplicationsMenuArabic.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:571:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:524:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/localization.feature:44:in `When I log in to a new session in Arabic (ar)'
features/localization.feature:23:in `When I log in to a new session in <language> (<lang_code>)'
Then the keyboard layout is set to "us" 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 6.457 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#1)' (at time 04:25:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:25:32_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/12/artifact/build-artifacts/04:25:32_Tails_is_localized_for_every_tier-1_language,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:25:32_Tails_is_localized_for_every_tier-1_language,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:25:32_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:27.889
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 7.831
When I log in to a new session in Chinese (zh_CN) 3:20.057
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.502 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#2)' (at time 04:29:07)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:29:07_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/12/artifact/build-artifacts/04:29:07_Tails_is_localized_for_every_tier-1_language,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:29:07_Tails_is_localized_for_every_tier-1_language,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:29:07_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:24.578
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 7.879
When I log in to a new session in English (en) 29.576
Then the keyboard layout is set to "us" 0.279
When the network is plugged 0.114
And Tor is ready 21.367
Then I successfully start the Unsafe Browser 16.633
And I kill the Unsafe Browser 8.215
When I enable the screen keyboard 0.199
Then the screen keyboard works in Tor Browser 1:0.310
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.783 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#3)' (at time 04:31:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:31:38_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/12/artifact/build-artifacts/04:31:38_Tails_is_localized_for_every_tier-1_language,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:31:38_Tails_is_localized_for_every_tier-1_language,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:31:38_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
2:11.153
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.003
When I log in to a new session in French (fr) 48.353
Then the keyboard layout is set to "fr" 0.303
When the network is plugged 0.140
And Tor is ready 19.579
Then I successfully start the Unsafe Browser 17.199
And I kill the Unsafe Browser 7.157
When I enable the screen keyboard 0.184
Then the screen keyboard works in Tor Browser 30.231
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:1051:in `launch_app'
./features/step_definitions/common_steps.rb:1106:in `launch_tor_browser'
./features/step_definitions/browser.rb:445:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:411:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature: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 9.127 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#4)' (at time 04:33:57)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:33:57_Tails_is_localized_for_every_tier-1_language,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:33:57_Tails_is_localized_for_every_tier-1_language,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:33:57_Tails_is_localized_for_every_tier-1_language,_Examples___4_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:52.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.005
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 7.966
When I log in to a new session in German (de) 44.322
Then the keyboard layout is set to "de" 0.368
When the network is plugged 0.103
And Tor is ready 23.622
Then I successfully start the Unsafe Browser 24.392
And I kill the Unsafe Browser 8.856
When I enable the screen keyboard 0.189
Then the screen keyboard works in Tor Browser 1:2.789
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 9.563 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#5)' (at time 04:36:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:36:59_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/12/artifact/build-artifacts/04:36:59_Tails_is_localized_for_every_tier-1_language,_Examples___5_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:36:59_Tails_is_localized_for_every_tier-1_language,_Examples___5_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:36:59_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:29.033
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 7.932
When I log in to a new session in Italian (it) 3:21.100
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.254 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#6)' (at time 04:40:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:40:37_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/12/artifact/build-artifacts/04:40:37_Tails_is_localized_for_every_tier-1_language,_Examples___6_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:40:37_Tails_is_localized_for_every_tier-1_language,_Examples___6_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:40:37_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:29.479
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.505
When I log in to a new session in Persian (fa) 3:20.974
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.200 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#7)' (at time 04:44:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:44:13_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/12/artifact/build-artifacts/04:44:13_Tails_is_localized_for_every_tier-1_language,_Examples___7_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:44:13_Tails_is_localized_for_every_tier-1_language,_Examples___7_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:44:13_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:30.011
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 7.886
When I log in to a new session in Portuguese (pt) 45.130
Then the keyboard layout is set to "pt" 0.249
When the network is plugged 0.081
And Tor is ready 17.759
Then I successfully start the Unsafe Browser 16.813
And I kill the Unsafe Browser 7.654
When I enable the screen keyboard 0.159
Then the screen keyboard works in Tor Browser 54.275
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 10.898 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#8)' (at time 04:46:49)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:46:49_Tails_is_localized_for_every_tier-1_language,_Examples___8_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:46:49_Tails_is_localized_for_every_tier-1_language,_Examples___8_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:46:49_Tails_is_localized_for_every_tier-1_language,_Examples___8_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:36.051
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.563
When I log in to a new session in Russian (ru) 47.620
Then the keyboard layout is set to "ru" 0.446
When the network is plugged 0.117
And Tor is ready 23.169
Then I successfully start the Unsafe Browser 16.640
And I kill the Unsafe Browser 7.778
When I enable the screen keyboard 0.142
Then the screen keyboard works in Tor Browser 51.570
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 10.834 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#9)' (at time 04:49:36)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:49:36_Tails_is_localized_for_every_tier-1_language,_Examples___9_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:49:36_Tails_is_localized_for_every_tier-1_language,_Examples___9_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:49:36_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:48.872
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.069
When I log in to a new session in Spanish (es) 44.337
Then the keyboard layout is set to "es" 0.689
When the network is plugged 0.168
And Tor is ready 34.118
Then I successfully start the Unsafe Browser 17.031
And I kill the Unsafe Browser 7.216
When I enable the screen keyboard 0.150
Then the screen keyboard works in Tor Browser 57.089
cannot 
cannot find ScreenKeyboard.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:417:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature: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.001 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#10)' (at time 04:52:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:52:36_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/12/artifact/build-artifacts/04:52:36_Tails_is_localized_for_every_tier-1_language,_Examples___10_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:52:36_Tails_is_localized_for_every_tier-1_language,_Examples___10_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:52:36_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
2:12.356
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.437
When I log in to a new session in Turkish (tr) 45.853
Then the keyboard layout is set to "tr" 0.693
When the network is plugged 0.106
And Tor is ready 21.199
Then I successfully start the Unsafe Browser 17.997
And I kill the Unsafe Browser 7.365
When I enable the screen keyboard 0.168
Then the screen keyboard works in Tor Browser 30.533
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:1051:in `launch_app'
./features/step_definitions/common_steps.rb:1106:in `launch_tor_browser'
./features/step_definitions/browser.rb:445:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:411:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature: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 11.000 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#11)' (at time 04:54:56)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:54:56_Tails_is_localized_for_every_tier-1_language,_Examples___11_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:54:56_Tails_is_localized_for_every_tier-1_language,_Examples___11_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/04:54:56_Tails_is_localized_for_every_tier-1_language,_Examples___11_.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
57.328
Background
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 without a persistent partition and logged in 15.514
And I create a persistent partition with the default settings 24.186
Then the "TorConfiguration" tps feature is not enabled 2.302
When the network is plugged 0.076
And the Tor Connection Assistant autostarts 9.890
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 5.358
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.482 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 06:01:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:01:14_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:01:14_Using_Persistent_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:01:14_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:01:14_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
52.013
Background
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 without a persistent partition and logged in 10.537
And I create a persistent partition with the default settings 24.423
Then the "TorConfiguration" tps feature is not enabled 2.528
When the network is plugged 0.074
And the Tor Connection Assistant autostarts 9.284
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 5.164
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:826:in `click_connect_to_tor'
./features/step_definitions/tor.rb:635:in `block (2 levels) in <top (required)>'
./features/step_definitions/tor.rb:499:in `tca_configure'
./features/step_definitions/tor.rb:626:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/persistent_tor_bridges.feature:13:in `And I configure some persistent obfs4 bridges in the Tor Connection Assistant'
And I wait until Tor is ready 0.000
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 6.023 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 06:02:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:02:12_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:02:12_Disabling_persistence_of_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:02:12_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:02:12_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
52.641
Scenario Chatting with some friend over XMPP
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:513 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 16.039
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.538
Then I see Pidgin's account manager window 4.291
When I create my XMPP account 20.772
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.042
After features/support/hooks.rb:330 5.729 
SCENARIO FAILED: 'Chatting with some friend over XMPP' (at time 06:03:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:03:41_Chatting_with_some_friend_over_XMPP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:03:41_Chatting_with_some_friend_over_XMPP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:03:41_Chatting_with_some_friend_over_XMPP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:03:41_Chatting_with_some_friend_over_XMPP.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
49.686
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.006
Before features/support/hooks.rb:513 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 14.006
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.276
Then I see Pidgin's account manager window 3.688
When I create my XMPP account 20.714
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.042
After features/support/hooks.rb:330 6.843 
SCENARIO FAILED: 'Chatting with some friend over XMPP in a multi-user chat' (at time 06:04:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:04:37_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/12/artifact/build-artifacts/06:04:37_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:04:37_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/12/artifact/build-artifacts/06:04:37_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
53.344
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.005
Before features/support/hooks.rb:513 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 17.105
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.413
Then I see Pidgin's account manager window 3.774
And I create my XMPP account 21.050
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.063
After features/support/hooks.rb:330 5.948 
SCENARIO FAILED: 'Connecting to the tails multi-user chat with my XMPP account' (at time 06:05:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:05:37_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/12/artifact/build-artifacts/06:05:37_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:05:37_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/12/artifact/build-artifacts/06:05:37_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:21.897
Scenario Using a persistent Pidgin configuration
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:513 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.955
And the network is plugged 0.076
And Tor is ready 22.379
And available upgrades have been checked 1.150
And all notifications have disappeared 5.021
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.340
Then I see Pidgin's account manager window 6.982
When I create my XMPP account 20.992
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.034
After features/support/hooks.rb:330 5.662 
SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 06:07:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:07:05_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:07:05_Using_a_persistent_Pidgin_configuration.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:07:05_Using_a_persistent_Pidgin_configuration.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:07:05_Using_a_persistent_Pidgin_configuration.journal
After features/support/hooks.rb:100 0.000
Feature: Random Seed
Tags: @product
3:16.743
Scenario A random seed is read during boot and written during boot and shutdown
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.185
And I temporarily create a 7200 MiB disk named "temp" 0.060
And I plug USB drive "temp" 1.051
And I write the Tails USB image to disk "temp" 30.657
Then there is no random seed on USB drive "temp" 6.065
When I start Tails from USB drive "temp" with network unplugged 2:38.722
cannot 
cannot find TailsGreeter.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:457: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/random_seed.feature:12:in `When I start Tails from USB drive "temp" with network unplugged'
Then the random seed was written multiple times on first boot 0.000
And there is a random seed on USB drive "temp" 0.000
When I log in to a new session 0.000
And I wait for the random seed to be updated 0.000
Then there is a random seed on USB drive "temp" 0.000
And the random seed is different from the previous one 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Then there is a random seed on USB drive "temp" 0.000
And the random seed is different from the previous one 0.000
After features/support/hooks.rb:330 7.988 
SCENARIO FAILED: 'A random seed is read during boot and written during boot and shutdown' (at time 06:10:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:10:27_A_random_seed_is_read_during_boot_and_written_during_boot_and_shutdown.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:10:27_A_random_seed_is_read_during_boot_and_written_during_boot_and_shutdown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:10:27_A_random_seed_is_read_during_boot_and_written_during_boot_and_shutdown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:10:27_A_random_seed_is_read_during_boot_and_written_during_boot_and_shutdown.journal
After features/support/hooks.rb:100 0.124
Feature: Tails has a sane default configuration
Tags: @product
9.729
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.005
Steps
Given I have started Tails from DVD without network and logged in 9.555
Then there are no unexpected messages of priority "err" or higher in the journal 0.173
Unexpected 
Unexpected error messages in the journal: [
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "578",
    "_BOOT_ID": "4a0a0299fc5a4021982d7f844c0027bd",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "578",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748907664503649",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "353e5547a19f4a989149a1d119c0d14c",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=7c394dc843904b12b64425de37f04617;i=37b;b=4a0a0299fc5a4021982d7f844c0027bd;m=d42297;t=6369f4c167371;x=bfc7b99e0fb948ec",
    "__MONOTONIC_TIMESTAMP": "13902487",
    "__REALTIME_TIMESTAMP": "1748907664503665",
    "__SEQNUM": "891",
    "__SEQNUM_ID": "7c394dc843904b12b64425de37f04617"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "578",
    "_BOOT_ID": "4a0a0299fc5a4021982d7f844c0027bd",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "578",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748907664504016",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "353e5547a19f4a989149a1d119c0d14c",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=7c394dc843904b12b64425de37f04617;i=37d;b=4a0a0299fc5a4021982d7f844c0027bd;m=d423fa;t=6369f4c1674d4;x=e94f0c264b8414f4",
    "__MONOTONIC_TIMESTAMP": "13902842",
    "__REALTIME_TIMESTAMP": "1748907664504020",
    "__SEQNUM": "893",
    "__SEQNUM_ID": "7c394dc843904b12b64425de37f04617"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "1646",
    "SYSLOG_TIMESTAMP": "Jun  2 23:41:10 ",
    "_BOOT_ID": "4a0a0299fc5a4021982d7f844c0027bd",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_COMM": "adduser",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "1646",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748907670027728",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "21531bf11433472c96423694d4c658ab",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=7c394dc843904b12b64425de37f04617;i=3f1;b=4a0a0299fc5a4021982d7f844c0027bd;m=128b755;t=6369f4c6b082f;x=75e2f94b24938714",
    "__MONOTONIC_TIMESTAMP": "19445589",
    "__REALTIME_TIMESTAMP": "1748907670046767",
    "__SEQNUM": "1009",
    "__SEQNUM_ID": "7c394dc843904b12b64425de37f04617"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "578",
    "_BOOT_ID": "4a0a0299fc5a4021982d7f844c0027bd",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "578",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748907848663269",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "353e5547a19f4a989149a1d119c0d14c",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=7c394dc843904b12b64425de37f04617;i=8ce;b=4a0a0299fc5a4021982d7f844c0027bd;m=67b7de0;t=6369f57108197;x=c0493715597c6df8",
    "__MONOTONIC_TIMESTAMP": "108756448",
    "__REALTIME_TIMESTAMP": "1748907848663447",
    "__SEQNUM": "2254",
    "__SEQNUM_ID": "7c394dc843904b12b64425de37f04617"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "578",
    "_BOOT_ID": "4a0a0299fc5a4021982d7f844c0027bd",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "578",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748907848663292",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "353e5547a19f4a989149a1d119c0d14c",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=7c394dc843904b12b64425de37f04617;i=8d0;b=4a0a0299fc5a4021982d7f844c0027bd;m=67b7fba;t=6369f57108372;x=d599968af687c1d6",
    "__MONOTONIC_TIMESTAMP": "108756922",
    "__REALTIME_TIMESTAMP": "1748907848663922",
    "__SEQNUM": "2256",
    "__SEQNUM_ID": "7c394dc843904b12b64425de37f04617"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "17960",
    "SYSLOG_TIMESTAMP": "Jun  2 23:44:17 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "4a0a0299fc5a4021982d7f844c0027bd",
    "_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": "17960",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748907857307388",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "046eb40019864b83af30047d16f22139",
    "_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=7c394dc843904b12b64425de37f04617;i=1254;b=4a0a0299fc5a4021982d7f844c0027bd;m=6ff636a;t=6369f57946721;x=c96f1e2a4bd48b4e",
    "__MONOTONIC_TIMESTAMP": "117400426",
    "__REALTIME_TIMESTAMP": "1748907857307425",
    "__SEQNUM": "4692",
    "__SEQNUM_ID": "7c394dc843904b12b64425de37f04617"
  },
  {
    "MESSAGE": "Error receiving data: Connection reset by peer",
    "SYSLOG_IDENTIFIER": "spice-vdagentd",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_TIMESTAMP": "Jun  2 23:44:34 ",
    "_BOOT_ID": "4a0a0299fc5a4021982d7f844c0027bd",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "/usr/sbin/spice-vdagentd",
    "_COMM": "spice-vdagentd",
    "_EXE": "/usr/sbin/spice-vdagentd",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "14947",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748907874926096",
    "_SYSTEMD_CGROUP": "/system.slice/spice-vdagentd.service",
    "_SYSTEMD_INVOCATION_ID": "cc7a08f430f7458b98bc4157b4ddc8f3",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "spice-vdagentd.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=7c394dc843904b12b64425de37f04617;i=139f;b=4a0a0299fc5a4021982d7f844c0027bd;m=80c3a94;t=6369f58a13e4b;x=a2ba9161fa9e79e3",
    "__MONOTONIC_TIMESTAMP": "135019156",
    "__REALTIME_TIMESTAMP": "1748907874926155",
    "__SEQNUM": "5023",
    "__SEQNUM_ID": "7c394dc843904b12b64425de37f04617"
  }
].
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:237:in `/^there are no unexpected messages of priority "err" or higher in the journal$/'
features/sane_defaults.feature:21:in `Then there are no unexpected messages of priority "err" or higher in the journal'
After features/support/hooks.rb:330 5.575 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from DVD' (at time 06:11:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:11:35_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/12/artifact/build-artifacts/06:11:35_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:11:35_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/12/artifact/build-artifacts/06:11:35_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
27.430
Scenario No unexpected error messages in the journal after booting from USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27.320
Then there are no unexpected messages of priority "err" or higher in the journal 0.110
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": "714",
    "_BOOT_ID": "b85a1525805a411faed44f2269d4defe",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "714",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748909854282907",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "bb92d61d67784726b58c86cbc58615b5",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=648c0faf13014431a46ba8ed203ce43e;i=36c;b=b85a1525805a411faed44f2269d4defe;m=10f2792;t=6369fce9bd84e;x=7dd86f7dfd5a262a",
    "__MONOTONIC_TIMESTAMP": "17770386",
    "__REALTIME_TIMESTAMP": "1748909854283854",
    "__SEQNUM": "876",
    "__SEQNUM_ID": "648c0faf13014431a46ba8ed203ce43e"
  },
  {
    "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": "714",
    "_BOOT_ID": "b85a1525805a411faed44f2269d4defe",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "714",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748909854282918",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "bb92d61d67784726b58c86cbc58615b5",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=648c0faf13014431a46ba8ed203ce43e;i=36e;b=b85a1525805a411faed44f2269d4defe;m=10f27eb;t=6369fce9bd8a8;x=fbb7e1b827babf5",
    "__MONOTONIC_TIMESTAMP": "17770475",
    "__REALTIME_TIMESTAMP": "1748909854283944",
    "__SEQNUM": "878",
    "__SEQNUM_ID": "648c0faf13014431a46ba8ed203ce43e"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2356",
    "SYSLOG_TIMESTAMP": "Jun  3 00:17:43 ",
    "_BOOT_ID": "b85a1525805a411faed44f2269d4defe",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2356",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748909863494093",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "eb291c7182f249b3a94b9c9050f6e18e",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=648c0faf13014431a46ba8ed203ce43e;i=418;b=b85a1525805a411faed44f2269d4defe;m=19bbfbc;t=6369fcf287078;x=7150901f79b80dd7",
    "__MONOTONIC_TIMESTAMP": "26984380",
    "__REALTIME_TIMESTAMP": "1748909863497848",
    "__SEQNUM": "1048",
    "__SEQNUM_ID": "648c0faf13014431a46ba8ed203ce43e"
  },
  {
    "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": "714",
    "_BOOT_ID": "b85a1525805a411faed44f2269d4defe",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "714",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748910009210248",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "bb92d61d67784726b58c86cbc58615b5",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=648c0faf13014431a46ba8ed203ce43e;i=e6c;b=b85a1525805a411faed44f2269d4defe;m=a1dc5e8;t=6369fd7d81110;x=7017c98822c9086b",
    "__MONOTONIC_TIMESTAMP": "169723368",
    "__REALTIME_TIMESTAMP": "1748910009225488",
    "__SEQNUM": "3692",
    "__SEQNUM_ID": "648c0faf13014431a46ba8ed203ce43e"
  },
  {
    "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": "714",
    "_BOOT_ID": "b85a1525805a411faed44f2269d4defe",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "714",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748910009210272",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "bb92d61d67784726b58c86cbc58615b5",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=648c0faf13014431a46ba8ed203ce43e;i=e6e;b=b85a1525805a411faed44f2269d4defe;m=a1dc7ba;t=6369fd7d812e3;x=f9d1c82fb989889f",
    "__MONOTONIC_TIMESTAMP": "169723834",
    "__REALTIME_TIMESTAMP": "1748910009225955",
    "__SEQNUM": "3694",
    "__SEQNUM_ID": "648c0faf13014431a46ba8ed203ce43e"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "22449",
    "SYSLOG_TIMESTAMP": "Jun  3 00:20:16 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "b85a1525805a411faed44f2269d4defe",
    "_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": "22449",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1748910016568587",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "6a48529c69094d16835dd12aec248eda",
    "_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=648c0faf13014431a46ba8ed203ce43e;i=1861;b=b85a1525805a411faed44f2269d4defe;m=a8dd1ee;t=6369fd8481d16;x=d70352a35ff5776e",
    "__MONOTONIC_TIMESTAMP": "177066478",
    "__REALTIME_TIMESTAMP": "1748910016568598",
    "__SEQNUM": "6241",
    "__SEQNUM_ID": "648c0faf13014431a46ba8ed203ce43e"
  }
].
<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.593 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 06:12:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:12:08_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/12/artifact/build-artifacts/06:12:08_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/12/artifact/build-artifacts/06:12:08_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/12/artifact/build-artifacts/06:12:08_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
51.087
Scenario I can shutdown 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.673
When I request a shutdown using the system menu 38.414
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 7.746 
SCENARIO FAILED: 'I can shutdown Tails via the system menu' (at time 06:13:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:13:05_I_can_shutdown_Tails_via_the_system_menu.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:13:05_I_can_shutdown_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:13:05_I_can_shutdown_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:13:05_I_can_shutdown_Tails_via_the_system_menu.journal
After features/support/hooks.rb:100 0.000
Feature: Shutdown buttons in the system menu
Tags: @product @not_release_blocker
49.964
Scenario I can reboot Tails via the system menu
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.800
When I request a reboot using the system menu 37.164
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Restart' roleName='label'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/common_steps.rb:898:in `/^I request a (shutdown|reboot) using the system menu$/'
features/shutdown_applet.feature:12:in `When I request a reboot using the system menu'
Then Tails eventually restarts 0.000
After features/support/hooks.rb:330 5.987 
SCENARIO FAILED: 'I can reboot Tails via the system menu' (at time 06:14:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:14:02_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/12/artifact/build-artifacts/06:14:02_I_can_reboot_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:14:02_I_can_reboot_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:14:02_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:50.098
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.303
When I connect to an SFTP server on the Internet 1:49.794
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.048
After features/support/hooks.rb:330 4.919 
SCENARIO FAILED: 'Connecting to an SFTP server on the Internet using the GNOME "Connect to Server" feature' (at time 06:16:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:16:56_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/12/artifact/build-artifacts/06:16:56_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/12/artifact/build-artifacts/06:16:56_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/12/artifact/build-artifacts/06:16:56_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
34.441
Scenario Starting Tor Connection before connecting to Wi-Fi
Steps
When I start "Tor Connection" via GNOME Activities Overview 10.158
Then the Tor Connection Assistant reports that I am not connected to a local network 3.546
When I plug a Wi-Fi adapter 1.911
Then Tor Connection suggests me to connect to Wi-Fi 1.135
And I click on the Wi-Fi settings 1.154
And The Wi-Fi settings are displayed 16.534
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 7.026 
SCENARIO FAILED: 'Starting Tor Connection before connecting to Wi-Fi' (at time 06:20:04)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:20:04_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/12/artifact/build-artifacts/06:20:04_Starting_Tor_Connection_before_connecting_to_Wi-Fi.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:20:04_Starting_Tor_Connection_before_connecting_to_Wi-Fi.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:20:04_Starting_Tor_Connection_before_connecting_to_Wi-Fi.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
50.263
Scenario The Downloads directory is usable in 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.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.646
Then the live user's Downloads directory exists 0.057
And there is a GNOME bookmark for the Downloads directory 37.559
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.035
After features/support/hooks.rb:330 5.525 
SCENARIO FAILED: 'The Downloads directory is usable in Tor Browser' (at time 06:42:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:42: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/12/artifact/build-artifacts/06:42:59_The_Downloads_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:42:59_The_Downloads_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:42: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:13.621
Scenario Downloading files with the Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:513 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.837
When I start the Tor Browser 33.780
Then the Tor Browser loads the startup page 1.474
When I download some file in the Tor Browser to the Downloads directory 25.529
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.032
After features/support/hooks.rb:330 8.277 
SCENARIO FAILED: 'Downloading files with the Tor Browser' (at time 06:44:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:44:18_Downloading_files_with_the_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:44:18_Downloading_files_with_the_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:44:18_Downloading_files_with_the_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:44:18_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
49.144
Scenario The Tor Browser uses TBB's shared libraries
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.179
When I start the Tor Browser 34.246
Then the Tor Browser uses all expected TBB shared libraries 1.718
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 6.181 
SCENARIO FAILED: 'The Tor Browser uses TBB's shared libraries' (at time 06:49:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:49:51_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/12/artifact/build-artifacts/06:49:51_The_Tor_Browser_uses_TBB_s_shared_libraries.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:49:51_The_Tor_Browser_uses_TBB_s_shared_libraries.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:49:51_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:41.054
Scenario The Persistent directory is 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 without network from a USB drive with a persistent partition enabled and logged in 11.654
And the network is plugged 0.148
And I successfully configure Tor 23.730
And available upgrades have been checked 1.163
And all notifications have disappeared 5.186
And there is a GNOME bookmark for the Persistent directory 2.103
When I start the Tor Browser 20.161
And I download some file in the Tor Browser to the Persistent directory 36.905
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 14.932 
SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 06:55:10)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:55:10_The_Persistent_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:55:10_The_Persistent_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:55:10_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
47.937
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD without network and logged in 9.560
Then the live user's Documents directory exists 0.485
And there is a GNOME bookmark for the Documents directory 37.891
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 5.713 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#1)' (at time 06:56:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:56:13_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/12/artifact/build-artifacts/06:56:13_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:56:13_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/12/artifact/build-artifacts/06:56:13_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
47.077
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.009
Steps
Given I have started Tails from DVD without network and logged in 9.860
Then the live user's Downloads directory exists 0.254
And there is a GNOME bookmark for the Downloads directory 36.961
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.739 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#2)' (at time 06:57:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:57:06_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/12/artifact/build-artifacts/06:57:06_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:57:06_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/12/artifact/build-artifacts/06:57:06_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
47.367
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD without network and logged in 9.697
Then the live user's Music directory exists 0.255
And there is a GNOME bookmark for the Music directory 37.414
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.690 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#3)' (at time 06:57:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:57:59_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/12/artifact/build-artifacts/06:57:59_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:57:59_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/12/artifact/build-artifacts/06:57:59_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
47.929
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.772
Then the live user's Pictures directory exists 0.229
And there is a GNOME bookmark for the Pictures directory 37.927
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.958 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#4)' (at time 06:58:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:58:53_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/12/artifact/build-artifacts/06:58:53_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:58:53_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/12/artifact/build-artifacts/06:58:53_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
46.884
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.096
Then the live user's Videos directory exists 0.206
And there is a GNOME bookmark for the Videos directory 36.582
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.714 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#5)' (at time 06:59:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:59:46_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/12/artifact/build-artifacts/06:59:46_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/06:59:46_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/12/artifact/build-artifacts/06:59:46_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
21.493
Scenario Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume
Steps
When I plug a USB drive containing a basic VeraCrypt volume 7.326
And I cancel the GNOME authentication prompt 2.814
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 5.894
And I open this VeraCrypt volume in GNOME Files 4.880
Then I see the expected contents in this VeraCrypt volume 0.497
When I lock the currently opened VeraCrypt volume 0.079
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:18:in `When I lock the currently opened VeraCrypt volume'
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.379 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume' (at time 07:19:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/07:19:43_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/12/artifact/build-artifacts/07:19:43_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/12/artifact/build-artifacts/07:19:43_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/12/artifact/build-artifacts/07:19:43_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.248
Scenario Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume
Steps
When I plug a USB drive containing a hidden VeraCrypt volume 10.531
And I cancel the GNOME authentication prompt 2.915
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 5.379
And I open this VeraCrypt volume in GNOME Files 4.397
Then I see the expected contents in this VeraCrypt volume 0.933
When I lock the currently opened VeraCrypt volume 0.091
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.377 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:20:22)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/07:20:22_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/12/artifact/build-artifacts/07:20:22_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/12/artifact/build-artifacts/07:20:22_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/12/artifact/build-artifacts/07:20:22_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
31.471
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 18.764
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 8.461
And I open this VeraCrypt volume in GNOME Files 3.622
Then I see the expected contents in this VeraCrypt volume 0.468
When I lock the currently opened VeraCrypt file container 0.155
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.401 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM' (at time 07:21:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/07:21:09_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/12/artifact/build-artifacts/07:21:09_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/12/artifact/build-artifacts/07:21:09_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/12/artifact/build-artifacts/07:21:09_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
40.797
Scenario Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 26.675
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 8.676
And I open this VeraCrypt volume in GNOME Files 4.872
Then I see the expected contents in this VeraCrypt volume 0.488
When I lock the currently opened VeraCrypt file container 0.084
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:43:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.428 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container' (at time 07:22:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/07:22: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/12/artifact/build-artifacts/07:22: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/12/artifact/build-artifacts/07:22: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/12/artifact/build-artifacts/07:22:05_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.017
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
28.182
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 8.476
And I cancel the GNOME authentication prompt 3.236
And I unlock and mount this VeraCrypt volume with GNOME Disks 11.494
And I open this VeraCrypt volume in GNOME Files 4.339
Then I see the expected contents in this VeraCrypt volume 0.535
When I lock the currently opened VeraCrypt volume 0.099
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.561 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 07:22:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/07:22:48_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/12/artifact/build-artifacts/07:22:48_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/12/artifact/build-artifacts/07:22:48_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/12/artifact/build-artifacts/07:22:48_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
27.567
Scenario Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume
Steps
When I plug a USB drive containing a hidden VeraCrypt volume 10.795
And I cancel the GNOME authentication prompt 3.754
And I unlock and mount this VeraCrypt volume with GNOME Disks 8.292
And I open this VeraCrypt volume in GNOME Files 4.079
Then I see the expected contents in this VeraCrypt volume 0.507
When I lock the currently opened VeraCrypt volume 0.137
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.383 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:23:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/07:23:31_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/12/artifact/build-artifacts/07:23:31_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/12/artifact/build-artifacts/07:23:31_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/12/artifact/build-artifacts/07:23:31_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
50.778
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 23.515
And I unlock and mount this VeraCrypt file container with GNOME Disks 21.739
And I open this VeraCrypt volume in GNOME Files 4.891
Then I see the expected contents in this VeraCrypt volume 0.505
When I lock the currently opened VeraCrypt file container 0.127
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.430 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 07:24:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/07:24:37_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/12/artifact/build-artifacts/07:24:37_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/12/artifact/build-artifacts/07:24:37_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/12/artifact/build-artifacts/07:24:37_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.018
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
51.472
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 26.770
And I unlock and mount this VeraCrypt file container with GNOME Disks 20.169
And I open this VeraCrypt volume in GNOME Files 3.875
Then I see the expected contents in this VeraCrypt volume 0.532
When I lock the currently opened VeraCrypt file container 0.125
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.384 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 07:25:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/07:25:44_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/12/artifact/build-artifacts/07:25:44_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/07:25:44_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/07:25:44_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.076
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.467
And I unlock and mount this VeraCrypt file container with GNOME Disks 18.960
And I open this VeraCrypt volume in GNOME Files 4.109
Then I see the expected contents in this VeraCrypt volume 0.452
When I lock the currently opened VeraCrypt file container 0.086
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.682 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM' (at time 07:26:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/12/artifact/build-artifacts/07:26:40_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/12/artifact/build-artifacts/07:26:40_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/12/artifact/build-artifacts/07:26:40_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/12/artifact/build-artifacts/07:26:40_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000