Project Number Date
test_Tails_ISO_feature-trixie 14 05 Jun 2025, 07:14

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
42.180
Scenario Using obfs4 pluggable transports from a QR code
Steps
When I configure some obfs4 bridges from a QR code in the Tor Connection Assistant in hide mode 42.180
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:663:in `block (2 levels) in <top (required)>'
./features/step_definitions/tor.rb:499:in `tca_configure'
./features/step_definitions/tor.rb:626:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/tor_bridges.feature:28:in `When I configure some obfs4 bridges from a QR code in the Tor Connection Assistant in hide mode'
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:330 6.518 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:30:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/00:30:55_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/00:30:55_Using_obfs4_pluggable_transports_from_a_QR_code.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/00:30:55_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/00:30:55_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:100 0.072
Feature: Using Tor bridges and pluggable transports
Tags: @product
1:12.503
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 2.317
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 32.332
Then the Tor Connection Assistant reports that it failed to connect 0.140
And tca.conf is empty 0.946
Given I scan a QR code from the error page in Tor Connection Assistant 36.767
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: Error: atspi_error: timeout from dbind (1)
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:205:in `get_field'
./features/support/helpers/dogtail.rb:241:in `text'
./features/step_definitions/tor.rb:738:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/tor.rb:737:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:737:in `/^I scan a QR code from the error page in Tor Connection Assistant$/'
features/tor_bridges.feature:39:in `Given I scan a QR code from the error page in Tor Connection Assistant'
And I retry connecting to Tor 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 7.869 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:32:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/00:32:32_TCA_can_scan_QR_code_after_a_connection_failure.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/00:32:32_TCA_can_scan_QR_code_after_a_connection_failure.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/00:32:32_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/00:32:32_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.037
Feature: Using Tor bridges and pluggable transports
Tags: @product
23.975
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 7.127
And I wait until Tor is ready 4.906
When I disconnect the network through GNOME 11.940
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.414 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:36:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/00:36:14_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/14/artifact/build-artifacts/00:36:14_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/00:36:14_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/14/artifact/build-artifacts/00:36:14_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.039
Feature: Using Tor bridges and pluggable transports
Tags: @product
57.599
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 11.387
And I wait until Tor is ready 34.112
And I disconnect the network through GNOME 12.100
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.537 
SCENARIO FAILED: 'Reconnecting from an unblocked network to a blocked network displays an error' (at time 00:37:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/00:37:33_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/14/artifact/build-artifacts/00:37:33_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/14/artifact/build-artifacts/00:37:33_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/14/artifact/build-artifacts/00:37:33_Reconnecting_from_an_unblocked_network_to_a_blocked_network_displays_an_error.journal
After features/support/hooks.rb:100 0.051
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
14.441
Scenario Erasure of memory freed by killed userspace processes
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.871
And I prepare Tails for memory erasure tests 0.837
When I start a process allocating 128 MiB of memory with a known pattern 1.340
Then patterns cover at least 128 MiB in the guest's memory 3.391
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.708 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:38:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/00:38:48_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/14/artifact/build-artifacts/00:38:48_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/00:38:48_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/00:38:48_Erasure_of_memory_freed_by_killed_userspace_processes.journal
After features/support/hooks.rb:100 0.000
Feature: Additional software
Tags: @product @check_tor_leaks @slow
12:5.560
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.007
Before features/support/hooks.rb:513 0.006
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:20.465
And I update APT using apt 12.073
And I install "popularity-contest" using apt 26.367
Then I am proposed to add the "popularity-contest" package to my Additional Software 14.961
When I create a persistent storage and activate the Additional Software feature 26.964
Then Additional Software is correctly configured for package "popularity-contest" 2.797
When I shutdown Tails and wait for the computer to power off 14.815
And I start Tails from USB drive "__internal" with network unplugged 1:55.372
And I enable persistence 29.624
And I log in to a new session 40.153
And the Additional Software installation service has started 1:0.279
Then I am notified that the installation succeeded 5:1.686
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.046
After features/support/hooks.rb:330 6.534 
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:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/01:34:17_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/01:34:17_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/01:34:17_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/01:34:17_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/01:34:17_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/01:34:17_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/01:34:17_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/14/artifact/build-artifacts/01:34:17_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/14/artifact/build-artifacts/01:34:17_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.015
Feature: Additional software
Tags: @product @check_tor_leaks @slow
25:18.085
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.005
Before features/support/hooks.rb:513 0.007
Steps
Given a computer 0.204
And I start Tails from USB drive "__internal" and I login with an administration password 2:59.830
And I update APT using apt 12.593
When I install "makepp" using apt 22:5.457
Tor 
Tor operation failed (despite retrying 10 times) with
Timeout::Error: try_for() timeout expired
Last ignored exception was: ExecutionFailedInVM: Command failed: dpkg -s 'makepp' 2>/dev/null | grep -qs '^Status:.*installed$'
error code: 1
stdout: 
stderr: .
<false> is not true.
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/apt.rb:69:in `block in wait_for_package_installation'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/apt.rb:68:in `wait_for_package_installation'
./features/step_definitions/apt.rb:86:in `block (3 levels) in <top (required)>'
./features/step_definitions/apt.rb:82:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:211:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:81:in `block in <top (required)>' (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:81:in `/^I install "(.+)" using apt$/'
features/additional_software_packages.feature:48:in `When I install "makepp" using apt'
Then the Additional Software dpkg hook has been run for package "makepp" and notices the persistence is locked 0.000
And the package "makepp" is installed 0.000
After features/support/hooks.rb:521 0.040
After features/support/hooks.rb:330 5.475 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:59:41)
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/14/artifact/build-artifacts/01:59:41_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/14/artifact/build-artifacts/01:59:41_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/14/artifact/build-artifacts/01:59:41_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/14/artifact/build-artifacts/01:59:41_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/14/artifact/build-artifacts/01:59:41_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/14/artifact/build-artifacts/01:59:41_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/14/artifact/build-artifacts/01:59:41_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/14/artifact/build-artifacts/01:59:41_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.012
Feature: Additional software
Tags: @product @check_tor_leaks @slow
6:21.780
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.005
Before features/support/hooks.rb:513 0.003
Steps
Given a computer 0.196
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 6:21.584
TCA 
TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
./features/step_definitions/common_steps.rb:657:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:612:in `/^Tor is ready$/'
./features/step_definitions/common_steps.rb:300: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/additional_software_packages.feature:55:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
When I uninstall "popularity-contest" using apt 0.000
And I accept removing "popularity-contest" from Additional Software 0.000
Then "popularity-contest" is not in the list of Additional Software 0.000
When I start Synaptic 0.000
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.037
After features/support/hooks.rb:330 14.170 
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:06:09)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/02:06:09_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic_chutney-data
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/02:06:09_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/14/artifact/build-artifacts/02:06:09_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/14/artifact/build-artifacts/02:06:09_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.011
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
3:43.974
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:513 0.005
Steps
Given a computer 0.188
And I start Tails from USB drive "__internal" with network unplugged 1:52.403
And I enable persistence 16.483
And I remove the "cowsay" deb files from the APT cache 0.053
# 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.082
And I log in to a new session 38.458
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 18.851
And I can open the Additional Software log file from the notification 37.452
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.036
After features/support/hooks.rb:330 6.486 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 02:28:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/02:28:17_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/14/artifact/build-artifacts/02:28:17_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/14/artifact/build-artifacts/02:28:17_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/14/artifact/build-artifacts/02:28:17_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/14/artifact/build-artifacts/02:28:17_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/14/artifact/build-artifacts/02:28:17_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/14/artifact/build-artifacts/02:28:17_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/02:28:17_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/14/artifact/build-artifacts/02:28:17_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:13.638
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.005
Steps
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.989
When I start Tails from USB drive "old" with network unplugged 1:40.358
The 
The Dogtail init script raised: SearchError: descendent of [application | gnome-shell]: child with roleName='notification'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/common_steps.rb:461:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:25:in `When I start Tails from USB drive "old" with network unplugged'
Then the boot device has safe access rights 0.000
And Tails is running from USB drive "old" 0.000
And there is no persistence partition on USB drive "old" 0.000
And process "udev-watchdog" is running 0.000
And udev-watchdog is monitoring the correct device 0.000
And I unplug USB drive "old" 0.000
After features/support/hooks.rb:330 6.610 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:30:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/02:30:37_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/14/artifact/build-artifacts/02:30:37_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/02:30:37_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/14/artifact/build-artifacts/02:30:37_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.009
Feature: Upgrading an old Tails USB installation
Tags: @product
1:24.289
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.220
And I start Tails from USB drive "old" with network unplugged and I login 1:24.069
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.836 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:32:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/02:32:08_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/14/artifact/build-artifacts/02:32:08_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/02:32:08_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/02:32:08_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:19.188
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.005
Steps
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:18.993
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.996 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:33:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/02:33:33_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/14/artifact/build-artifacts/02:33:33_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/14/artifact/build-artifacts/02:33:33_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/14/artifact/build-artifacts/02:33:33_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:9.347
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.006
Steps
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.147
The 
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:291:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:330 6.043 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:38:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/02:38:41_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/14/artifact/build-artifacts/02:38:41_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/14/artifact/build-artifacts/02:38:41_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/14/artifact/build-artifacts/02:38:41_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.008
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
22:58.335
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.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.002
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.511
When the network is plugged 0.065
And Tor is ready 28.033
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:11.909
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.814 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:01:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:01:46_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/14/artifact/build-artifacts/03:01:46_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:01:46_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:01:46_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
22:47.037
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.359
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 25.145
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:10.952
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.591 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:24:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:24:38_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/14/artifact/build-artifacts/03:24:38_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:24:38_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:24:38_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:5.144
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.004
Steps
Given I have started Tails from DVD without network and logged in 8.962
And I prepare Tails for memory erasure tests 0.669
And I fill a 128 MiB file with a known pattern on the root filesystem 21.628
And patterns cover at least 128 MiB in the guest's memory 3.479 
Pattern coverage: 100.000% (128 MiB out of 128 MiB reference memory)
When I eject the boot medium 0.342
And I wait for Tails to finish wiping the memory 1:30.061
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.538 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: overlayfs read-write branch' (at time 03:27:53)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:27:53_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/14/artifact/build-artifacts/03:27:53_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/14/artifact/build-artifacts/03:27:53_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:57.687
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.006
Steps
Given I have started Tails from DVD without network and logged in 8.836
And I prepare Tails for memory erasure tests 0.621
And I plug and mount a 128 MiB USB drive with a vfat filesystem 10.330
And I fill the USB drive with a known pattern 3.016
And I read the content of the test FS 0.088
And patterns cover at least 90% of the test FS size in the guest's memory 4.092 
Pattern coverage: 100.000% (127 MiB out of 127 MiB reference memory)
When I eject the boot medium 0.333
And I wait for Tails to finish wiping the memory 1:30.367
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.495 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: vfat' (at time 03:30:01)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:30:01_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:30:01_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:30:01_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:26.962
Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD without network and logged in 8.807
And I prepare Tails for memory erasure tests 0.813
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 41.635
And I fill the USB drive with a known pattern 1.408
And I read the content of the test FS 0.082
And patterns cover at least 99% of the test FS size in the guest's memory 2.802 
Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)
When I eject the boot medium 1.104
And I wait for Tails to finish wiping the memory 1:30.307
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.554 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 03:32:39)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:32:39_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:32:39_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/14/artifact/build-artifacts/03:32:39_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.000
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
0.105
Scenario Getting a DHCP lease with the default NetworkManager connection
Steps
Then the hostname should not have been leaked on the network 0.105
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.199 
SCENARIO FAILED: 'Getting a DHCP lease with the default NetworkManager connection' (at time 03:39:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:39:26_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/14/artifact/build-artifacts/03:39:26_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.pcap
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:39:26_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:39:26_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:39:26_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.058
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
0.885
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.312
And I switch to the "manually-added-con" NetworkManager connection 0.457
Then the hostname should not have been leaked on the network 0.115
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.442 
SCENARIO FAILED: 'Getting a DHCP lease with a manually configured NetworkManager connection' (at time 03:40:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:40:36_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/14/artifact/build-artifacts/03:40:36_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.pcap
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:40:36_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:40:36_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:40:36_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.043
Feature: Hardware failures
Tags: @product
3:10.354
Scenario Outline GPT backup corruption with a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 35.032
And I corrupt the boot device's GPT backup header 0.544
And I power off the computer 0.326
When I start the computer 1.027
Then the computer boots Tails 1:57.753
When I log in to a new session 24.788
And all notifications have disappeared 10.486
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.393
<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.402 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 03:58:22)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:58:22_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/14/artifact/build-artifacts/03:58:22_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:58:22_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/03:58:22_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:100 0.009
Feature: Hardware failures
Tags: @product
2:43.134
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 9.759
And I corrupt the boot device's GPT backup partition table 0.375
And I power off the computer 0.332
When I start the computer 1.009
Then the computer boots Tails 1:52.456
When I log in to a new session 28.306
And all notifications have disappeared 10.572
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.321
<nil> 
<nil> was expected to not be nil. (Test::Unit::AssertionFailedError)
./features/step_definitions/hardware.rb:84:in `/^I am recommended to migrate to a new USB stick due to partitioning errors$/'
features/hardware_failure.feature:46:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'
features/hardware_failure.feature:41:in `Then I am recommended to migrate to a new USB stick due to partitioning errors'
And Tails detected partitioning error partitioning-corruption 0.000
After features/support/hooks.rb:330 6.720 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 04:01:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:01:12_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/14/artifact/build-artifacts/04:01:12_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:01:12_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:01:12_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:100 0.032
Feature: Hardware failures
Tags: @product
3:53.978
Scenario GPT backup corruption without a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given a computer 0.205
And I set Tails to boot with options "test_gpt_corruption=gpt_backup,gpt_backup_table" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.046
And I plug USB drive "temp" 1.052
And I write the Tails USB image to disk "temp" 35.247
When I start Tails from USB drive "temp" with network unplugged 2:39.848
Then Tails is running from USB drive "temp" 0.363
And the Greeter forbids creating a persistent partition 0.096
When I log in to a new session 26.827
And all notifications have disappeared 10.014
Then I am recommended to reinstall Tails due to partitioning errors 0.275
<"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.376 
SCENARIO FAILED: 'GPT backup corruption without a persistent partition' (at time 04:05:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:05:13_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/14/artifact/build-artifacts/04:05:13_GPT_backup_corruption_without_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:05:13_GPT_backup_corruption_without_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:05:13_GPT_backup_corruption_without_a_persistent_partition.journal
After features/support/hooks.rb:100 0.108
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
9.122
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.006
Steps
Given I have started Tails from DVD without network and logged in 9.032
Then the keys trusted by APT are valid for the next 3 months 0.090
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.585 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 04:15:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:15:40_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/14/artifact/build-artifacts/04:15:40_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:15:40_The_included_APT_repository_keys_are_up-to-date.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:15:40_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product
1:41.227
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.004
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 11.995
And I log in to a new session in German (de) 49.529
Then the live user's Documents directory exists 0.120
And there is a GNOME bookmark for the Documents directory 39.583
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.741 
SCENARIO FAILED: 'Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255), Examples (#1)' (at time 04:17:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:17:27_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/14/artifact/build-artifacts/04:17:27_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/14/artifact/build-artifacts/04:17:27_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/14/artifact/build-artifacts/04:17:27_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:42.789
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.004
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 9.944
And I log in to a new session in German (de) 52.577
Then the live user's Downloads directory exists 0.244
And there is a GNOME bookmark for the Downloads directory 40.024
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.912 
SCENARIO FAILED: 'Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255), Examples (#2)' (at time 04:19:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:19:15_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/14/artifact/build-artifacts/04:19:15_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/14/artifact/build-artifacts/04:19:15_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/14/artifact/build-artifacts/04:19:15_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:34.909
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.300
And I log in to a new session in German (de) 45.580
Then the live user's Music directory exists 0.229
And there is a GNOME bookmark for the Music directory 40.799
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Music' roleName='label'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/common_steps.rb:1225:in `/^there is a GNOME bookmark for the (.*) directory$/'
features/localization.feature:16:in `And there is a GNOME bookmark for the Music directory'
features/localization.feature:11:in `And there is a GNOME bookmark for the <dir> directory'
After features/support/hooks.rb:330 7.719 
SCENARIO FAILED: 'Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255), Examples (#3)' (at time 04:20:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:20:56_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:20:56_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:20:56_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:20:56_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product
1:38.498
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.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.211
And I log in to a new session in German (de) 47.230
Then the live user's Pictures directory exists 0.308
And there is a GNOME bookmark for the Pictures directory 42.747
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 7.187 
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:22:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:22:42_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/14/artifact/build-artifacts/04:22:42_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/14/artifact/build-artifacts/04:22:42_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/14/artifact/build-artifacts/04:22:42_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:29.222
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.859
When I log in to a new session in Arabic (ar) 3:21.362
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.401 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#1)' (at time 04:27:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:27:23_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/14/artifact/build-artifacts/04:27:23_Tails_is_localized_for_every_tier-1_language,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:27:23_Tails_is_localized_for_every_tier-1_language,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:27:23_Tails_is_localized_for_every_tier-1_language,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:28.096
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.172
When I log in to a new session in Chinese (zh_CN) 3:19.923
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.264 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#2)' (at time 04:30:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:30:58_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/14/artifact/build-artifacts/04:30:58_Tails_is_localized_for_every_tier-1_language,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:30:58_Tails_is_localized_for_every_tier-1_language,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:30:58_Tails_is_localized_for_every_tier-1_language,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:30.279
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.176
When I log in to a new session in English (en) 34.350
Then the keyboard layout is set to "us" 0.473
When the network is plugged 0.137
And Tor is ready 20.078
Then I successfully start the Unsafe Browser 18.577
And I kill the Unsafe Browser 7.644
When I enable the screen keyboard 0.241
Then the screen keyboard works in Tor Browser 1:0.598
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 5.724 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#3)' (at time 04:33:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:33:34_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/14/artifact/build-artifacts/04:33:34_Tails_is_localized_for_every_tier-1_language,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:33:34_Tails_is_localized_for_every_tier-1_language,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:33:34_Tails_is_localized_for_every_tier-1_language,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:0.296
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.008
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.252
When I log in to a new session in French (fr) 53.934
Then the keyboard layout is set to "fr" 0.387
When the network is plugged 0.092
And Tor is ready 21.066
Then I successfully start the Unsafe Browser 18.150
And I kill the Unsafe Browser 8.357
When I enable the screen keyboard 0.160
Then the screen keyboard works in Tor Browser 1:9.895
cannot 
cannot find ScreenKeyboard.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:417:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:47:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "fr" 0.000
After features/support/hooks.rb:330 5.897 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#4)' (at time 04:36:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:36:40_Tails_is_localized_for_every_tier-1_language,_Examples___4_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:36:40_Tails_is_localized_for_every_tier-1_language,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:36:40_Tails_is_localized_for_every_tier-1_language,_Examples___4_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:36:40_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:57.621
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.171
When I log in to a new session in German (de) 45.510
Then the keyboard layout is set to "de" 0.496
When the network is plugged 0.116
And Tor is ready 26.492
Then I successfully start the Unsafe Browser 16.015
And I kill the Unsafe Browser 7.672
When I enable the screen keyboard 0.147
Then the screen keyboard works in Tor Browser 1:12.997
cannot 
cannot find ScreenKeyboard.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:417:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:48:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "de" 0.000
After features/support/hooks.rb:330 5.866 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#5)' (at time 04:39:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:39:44_Tails_is_localized_for_every_tier-1_language,_Examples___5_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:39:44_Tails_is_localized_for_every_tier-1_language,_Examples___5_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:39:44_Tails_is_localized_for_every_tier-1_language,_Examples___5_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:39:44_Tails_is_localized_for_every_tier-1_language,_Examples___5_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:28.082
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.080
When I log in to a new session in Italian (it) 3:20.002
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.502 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#6)' (at time 04:43:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:43:18_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/14/artifact/build-artifacts/04:43:18_Tails_is_localized_for_every_tier-1_language,_Examples___6_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:43:18_Tails_is_localized_for_every_tier-1_language,_Examples___6_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:43:18_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.100
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.007
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 9.099
When I log in to a new session in Persian (fa) 3:20.000
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.424 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#7)' (at time 04:46:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:46:54_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/14/artifact/build-artifacts/04:46:54_Tails_is_localized_for_every_tier-1_language,_Examples___7_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:46:54_Tails_is_localized_for_every_tier-1_language,_Examples___7_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:46:54_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:46.508
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.018
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.144
When I log in to a new session in Portuguese (pt) 51.983
Then the keyboard layout is set to "pt" 0.327
When the network is plugged 0.103
And Tor is ready 21.000
Then I successfully start the Unsafe Browser 16.985
And I kill the Unsafe Browser 7.935
When I enable the screen keyboard 0.199
Then the screen keyboard works in Tor Browser 59.828
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 6.657 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#8)' (at time 04:49:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:49:47_Tails_is_localized_for_every_tier-1_language,_Examples___8_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:49:47_Tails_is_localized_for_every_tier-1_language,_Examples___8_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:49:47_Tails_is_localized_for_every_tier-1_language,_Examples___8_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:49:47_Tails_is_localized_for_every_tier-1_language,_Examples___8_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
3:20.868
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.007
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.972
When I log in to a new session in Russian (ru) 54.013
Then the keyboard layout is set to "ru" 0.373
When the network is plugged 0.160
And Tor is ready 27.007
Then I successfully start the Unsafe Browser 28.843
And I kill the Unsafe Browser 11.242
When I enable the screen keyboard 0.737
Then the screen keyboard works in Tor Browser 1:9.518
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 6.314 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#9)' (at time 04:53:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:53:14_Tails_is_localized_for_every_tier-1_language,_Examples___9_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:53:14_Tails_is_localized_for_every_tier-1_language,_Examples___9_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:53:14_Tails_is_localized_for_every_tier-1_language,_Examples___9_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:53:14_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
3:8.992
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.009
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.934
When I log in to a new session in Spanish (es) 59.600
Then the keyboard layout is set to "es" 0.374
When the network is plugged 0.129
And Tor is ready 19.778
Then I successfully start the Unsafe Browser 26.847
And I kill the Unsafe Browser 7.584
When I enable the screen keyboard 0.205
Then the screen keyboard works in Tor Browser 1:5.537
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 6.277 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#10)' (at time 04:56:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:56:30_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/14/artifact/build-artifacts/04:56:30_Tails_is_localized_for_every_tier-1_language,_Examples___10_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:56:30_Tails_is_localized_for_every_tier-1_language,_Examples___10_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:56:30_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:41.091
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.008
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.390
When I log in to a new session in Turkish (tr) 50.192
Then the keyboard layout is set to "tr" 0.702
When the network is plugged 0.116
And Tor is ready 23.025
Then I successfully start the Unsafe Browser 18.183
And I kill the Unsafe Browser 8.129
When I enable the screen keyboard 0.187
Then the screen keyboard works in Tor Browser 52.164
cannot 
cannot find ScreenKeyboard.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:417:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:57:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 8.430 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#11)' (at time 04:59:17)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:59:17_Tails_is_localized_for_every_tier-1_language,_Examples___11_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:59:17_Tails_is_localized_for_every_tier-1_language,_Examples___11_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/04:59:17_Tails_is_localized_for_every_tier-1_language,_Examples___11_.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
2:19.291
Scenario Filesystem and I/O errors
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.581
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 8.173
And Tails detects disk read failures on the boot device 1.661
When I try to enable persistence 2.279
Then the Welcome Screen tells me that my hardware is probably failing 34.244
When I log in to a new session 41.135
And all notifications have disappeared 23.369
Then the Tor Browser starts 18.845
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
features/persistence.feature:213:in `Then the Tor Browser starts'
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 8.375 
SCENARIO FAILED: 'Filesystem and I/O errors' (at time 06:03:24)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:03:24_Filesystem_and_I_O_errors.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:03:24_Filesystem_and_I_O_errors.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:03:24_Filesystem_and_I_O_errors.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
59.560
Scenario Chatting with some friend over XMPP
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Before features/support/hooks.rb:513 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 21.309
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.398
Then I see Pidgin's account manager window 5.956
When I create my XMPP account 20.896
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.029
After features/support/hooks.rb:330 5.916 
SCENARIO FAILED: 'Chatting with some friend over XMPP' (at time 06:16:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:16:00_Chatting_with_some_friend_over_XMPP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:16:00_Chatting_with_some_friend_over_XMPP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:16:00_Chatting_with_some_friend_over_XMPP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:16:00_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
1:0.033
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.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 23.205
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 10.696
Then I see Pidgin's account manager window 5.365
When I create my XMPP account 20.765
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.029
After features/support/hooks.rb:330 5.984 
SCENARIO FAILED: 'Chatting with some friend over XMPP in a multi-user chat' (at time 06:17:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:17:06_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/14/artifact/build-artifacts/06:17:06_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:17:06_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/14/artifact/build-artifacts/06:17:06_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
52.113
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.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 14.080
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.478
Then I see Pidgin's account manager window 5.643
And I create my XMPP account 20.911
cannot 
cannot find PidginAddAccountWindow.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/pidgin.rb:123:in `/^I create my XMPP account$/'
features/pidgin.feature: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.051
After features/support/hooks.rb:330 5.620 
SCENARIO FAILED: 'Connecting to the tails multi-user chat with my XMPP account' (at time 06:18:04)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:18:04_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/14/artifact/build-artifacts/06:18:04_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:18:04_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/14/artifact/build-artifacts/06:18:04_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:25.063
Scenario Using a persistent Pidgin configuration
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
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 14.232
And the network is plugged 0.343
And Tor is ready 27.396
And available upgrades have been checked 1.128
And all notifications have disappeared 5.108
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 11.338
Then I see Pidgin's account manager window 4.584
When I create my XMPP account 20.930
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.032
After features/support/hooks.rb:330 5.422 
SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 06:19:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:19:35_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:19:35_Using_a_persistent_Pidgin_configuration.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:19:35_Using_a_persistent_Pidgin_configuration.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:19:35_Using_a_persistent_Pidgin_configuration.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
11.814
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.008
Steps
Given I have started Tails from DVD without network and logged in 11.675
Then there are no unexpected messages of priority "err" or higher in the journal 0.139
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": "580",
    "_BOOT_ID": "fb52ad86a97643399f84f32e94e55ba7",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "580",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749080437018378",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "da94997cd19d43c2a340e5d45f23d358",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=8c81baadfa344346a73004426b329024;i=372;b=fb52ad86a97643399f84f32e94e55ba7;m=cee7a3;t=636c78621cf1d;x=8108233be9fb496e",
    "__MONOTONIC_TIMESTAMP": "13559715",
    "__REALTIME_TIMESTAMP": "1749080437018397",
    "__SEQNUM": "882",
    "__SEQNUM_ID": "8c81baadfa344346a73004426b329024"
  },
  {
    "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": "580",
    "_BOOT_ID": "fb52ad86a97643399f84f32e94e55ba7",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "580",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749080437018768",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "da94997cd19d43c2a340e5d45f23d358",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=8c81baadfa344346a73004426b329024;i=374;b=fb52ad86a97643399f84f32e94e55ba7;m=cef08b;t=636c78621d806;x=c9fe4662eb265d2e",
    "__MONOTONIC_TIMESTAMP": "13561995",
    "__REALTIME_TIMESTAMP": "1749080437020678",
    "__SEQNUM": "884",
    "__SEQNUM_ID": "8c81baadfa344346a73004426b329024"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2006",
    "SYSLOG_TIMESTAMP": "Jun  4 23:40:45 ",
    "_BOOT_ID": "fb52ad86a97643399f84f32e94e55ba7",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2006",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749080445061173",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "5c06e973cb854b709a2a2ef786c905e2",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=8c81baadfa344346a73004426b329024;i=403;b=fb52ad86a97643399f84f32e94e55ba7;m=149a0e8;t=636c7869c8863;x=bfc7f0a33f4b2d1",
    "__MONOTONIC_TIMESTAMP": "21602536",
    "__REALTIME_TIMESTAMP": "1749080445061219",
    "__SEQNUM": "1027",
    "__SEQNUM_ID": "8c81baadfa344346a73004426b329024"
  },
  {
    "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": "580",
    "_BOOT_ID": "fb52ad86a97643399f84f32e94e55ba7",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "580",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749080621512436",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "da94997cd19d43c2a340e5d45f23d358",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=8c81baadfa344346a73004426b329024;i=8c3;b=fb52ad86a97643399f84f32e94e55ba7;m=634c9c0;t=636c79120f736;x=73070012792e4feb",
    "__MONOTONIC_TIMESTAMP": "104122816",
    "__REALTIME_TIMESTAMP": "1749080621512502",
    "__SEQNUM": "2243",
    "__SEQNUM_ID": "8c81baadfa344346a73004426b329024"
  },
  {
    "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": "580",
    "_BOOT_ID": "fb52ad86a97643399f84f32e94e55ba7",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "580",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749080621512603",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "da94997cd19d43c2a340e5d45f23d358",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=8c81baadfa344346a73004426b329024;i=8c5;b=fb52ad86a97643399f84f32e94e55ba7;m=634cb63;t=636c79120f8d9;x=38a258fa0aa2453f",
    "__MONOTONIC_TIMESTAMP": "104123235",
    "__REALTIME_TIMESTAMP": "1749080621512921",
    "__SEQNUM": "2245",
    "__SEQNUM_ID": "8c81baadfa344346a73004426b329024"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "17458",
    "SYSLOG_TIMESTAMP": "Jun  4 23:43:48 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "fb52ad86a97643399f84f32e94e55ba7",
    "_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": "17458",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749080628014924",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "7adceb2a1e3541559d78ed58897812c4",
    "_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=8c81baadfa344346a73004426b329024;i=121f;b=fb52ad86a97643399f84f32e94e55ba7;m=6980206;t=636c791842f7d;x=23cec8869820e2ce",
    "__MONOTONIC_TIMESTAMP": "110625286",
    "__REALTIME_TIMESTAMP": "1749080628014973",
    "__SEQNUM": "4639",
    "__SEQNUM_ID": "8c81baadfa344346a73004426b329024"
  }
].
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:237:in `/^there are no unexpected messages of priority "err" or higher in the journal$/'
features/sane_defaults.feature:21:in `Then there are no unexpected messages of priority "err" or higher in the journal'
After features/support/hooks.rb:330 6.764 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from DVD' (at time 06:25:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:25:03_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/14/artifact/build-artifacts/06:25:03_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:25:03_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/14/artifact/build-artifacts/06:25:03_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
12.047
Scenario No unexpected error messages in the journal after booting from USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.956
Then there are no unexpected messages of priority "err" or higher in the journal 0.091
Unexpected 
Unexpected error messages in the journal: [
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "709",
    "_BOOT_ID": "d23b6bedb3b6440b80f3695beed3c75f",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "709",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749082639946297",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "bf363c621cbd4aef8e6b9fd69f4b1ded",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=39dd89c19eaa4353b693481e84fa9c4a;i=375;b=d23b6bedb3b6440b80f3695beed3c75f;m=dd9d3e;t=636c8096fec28;x=95af354856af02da",
    "__MONOTONIC_TIMESTAMP": "14523710",
    "__REALTIME_TIMESTAMP": "1749082639952936",
    "__SEQNUM": "885",
    "__SEQNUM_ID": "39dd89c19eaa4353b693481e84fa9c4a"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "709",
    "_BOOT_ID": "d23b6bedb3b6440b80f3695beed3c75f",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "709",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749082639946320",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "bf363c621cbd4aef8e6b9fd69f4b1ded",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=39dd89c19eaa4353b693481e84fa9c4a;i=377;b=d23b6bedb3b6440b80f3695beed3c75f;m=dd9dfd;t=636c8096fece7;x=61a215ebc9b7d822",
    "__MONOTONIC_TIMESTAMP": "14523901",
    "__REALTIME_TIMESTAMP": "1749082639953127",
    "__SEQNUM": "887",
    "__SEQNUM_ID": "39dd89c19eaa4353b693481e84fa9c4a"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2592",
    "SYSLOG_TIMESTAMP": "Jun  5 00:17:28 ",
    "_BOOT_ID": "d23b6bedb3b6440b80f3695beed3c75f",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2592",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749082648240370",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "4702b7a6e53c4bcebeec665e68036568",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=39dd89c19eaa4353b693481e84fa9c4a;i=419;b=d23b6bedb3b6440b80f3695beed3c75f;m=15c122d;t=636c809ee6117;x=f505eaa248b387d6",
    "__MONOTONIC_TIMESTAMP": "22811181",
    "__REALTIME_TIMESTAMP": "1749082648240407",
    "__SEQNUM": "1049",
    "__SEQNUM_ID": "39dd89c19eaa4353b693481e84fa9c4a"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "709",
    "_BOOT_ID": "d23b6bedb3b6440b80f3695beed3c75f",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "709",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749082787478455",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "bf363c621cbd4aef8e6b9fd69f4b1ded",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=39dd89c19eaa4353b693481e84fa9c4a;i=ea0;b=d23b6bedb3b6440b80f3695beed3c75f;m=97923b2;t=636c8123afe3d;x=a8582e2390e87d17",
    "__MONOTONIC_TIMESTAMP": "158933938",
    "__REALTIME_TIMESTAMP": "1749082787479101",
    "__SEQNUM": "3744",
    "__SEQNUM_ID": "39dd89c19eaa4353b693481e84fa9c4a"
  },
  {
    "MESSAGE": "/usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO=\"alsa_restore_std\" has no matching label, ignoring.",
    "SYSLOG_IDENTIFIER": "systemd-udevd",
    "CODE_FILE": "src/udev/udev-rules.c",
    "CODE_FUNC": "rule_resolve_goto",
    "CODE_LINE": "1376",
    "PRIORITY": "3",
    "SYSLOG_FACILITY": "3",
    "TID": "709",
    "_BOOT_ID": "d23b6bedb3b6440b80f3695beed3c75f",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "709",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749082787478483",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "bf363c621cbd4aef8e6b9fd69f4b1ded",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=39dd89c19eaa4353b693481e84fa9c4a;i=ea2;b=d23b6bedb3b6440b80f3695beed3c75f;m=9792535;t=636c8123affc1;x=2857e5c349972526",
    "__MONOTONIC_TIMESTAMP": "158934325",
    "__REALTIME_TIMESTAMP": "1749082787479489",
    "__SEQNUM": "3746",
    "__SEQNUM_ID": "39dd89c19eaa4353b693481e84fa9c4a"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "22467",
    "SYSLOG_TIMESTAMP": "Jun  5 00:19:54 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "d23b6bedb3b6440b80f3695beed3c75f",
    "_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": "22467",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749082794789080",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "f9702de9cbd44c799b9c73c445f863dc",
    "_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=39dd89c19eaa4353b693481e84fa9c4a;i=187f;b=d23b6bedb3b6440b80f3695beed3c75f;m=9e8ae88;t=636c812aa8913;x=2410570b26d65e54",
    "__MONOTONIC_TIMESTAMP": "166243976",
    "__REALTIME_TIMESTAMP": "1749082794789139",
    "__SEQNUM": "6271",
    "__SEQNUM_ID": "39dd89c19eaa4353b693481e84fa9c4a"
  }
].
<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.454 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 06:25:22)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:25:22_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/14/artifact/build-artifacts/06:25:22_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/14/artifact/build-artifacts/06:25:22_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/14/artifact/build-artifacts/06:25:22_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
54.131
Scenario I can shutdown Tails via the system menu
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 14.486
When I request a shutdown using the system menu 39.645
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-shell]: child with name='Power Off' roleName='label'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/common_steps.rb:898:in `/^I request a (shutdown|reboot) using the system menu$/'
features/shutdown_applet.feature:6:in `When I request a shutdown using the system menu'
Then Tails eventually shuts down 0.000
After features/support/hooks.rb:330 5.569 
SCENARIO FAILED: 'I can shutdown Tails via the system menu' (at time 06:26:22)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:26:22_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/14/artifact/build-artifacts/06:26:22_I_can_shutdown_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:26:22_I_can_shutdown_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:26:22_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
51.584
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 13.123
When I request a reboot using the system menu 38.460
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.817 
SCENARIO FAILED: 'I can reboot Tails via the system menu' (at time 06:27:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:27:19_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/14/artifact/build-artifacts/06:27:19_I_can_reboot_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:27:19_I_can_reboot_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:27:19_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.297
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.283
When I connect to an SFTP server on the Internet 1:50.013
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 5.614 
SCENARIO FAILED: 'Connecting to an SFTP server on the Internet using the GNOME "Connect to Server" feature' (at time 06:30:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:30:14_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/14/artifact/build-artifacts/06:30:14_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/14/artifact/build-artifacts/06:30:14_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/14/artifact/build-artifacts/06:30:14_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: Thunderbird email client
Tags: @product @check_tor_leaks
2:13.961
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 2:13.961
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/thunderbird.rb:106:in `/^I enter my email credentials into the autoconfiguration wizard$/'
features/thunderbird.feature:19:in `When I enter my email credentials into the autoconfiguration wizard'
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.000
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.000
When I accept the autoconfiguration wizard's configuration 0.000
And I send an email to myself 0.000
And I fetch my email 0.000
Then I can find the email I sent to myself in my inbox 0.000
After features/support/hooks.rb:521 0.039
After features/support/hooks.rb:330 6.073 
SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 06:33:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:33:47_I_can_send_emails,_and_receive_emails_over_IMAP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:33:47_I_can_send_emails,_and_receive_emails_over_IMAP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:33:47_I_can_send_emails,_and_receive_emails_over_IMAP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:33:47_I_can_send_emails,_and_receive_emails_over_IMAP.journal
After features/support/hooks.rb:100 0.000
Feature: Tor Connection helps the user in connecting to Tor
Tags: @product
34.261
Scenario Starting Tor Connection before connecting to Wi-Fi
Steps
When I start "Tor Connection" via GNOME Activities Overview 9.256
Then the Tor Connection Assistant reports that I am not connected to a local network 3.932
When I plug a Wi-Fi adapter 1.505
Then Tor Connection suggests me to connect to Wi-Fi 0.522
And I click on the Wi-Fi settings 1.215
And The Wi-Fi settings are displayed 17.829
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.141 
SCENARIO FAILED: 'Starting Tor Connection before connecting to Wi-Fi' (at time 06:34:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:34:37_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/14/artifact/build-artifacts/06:34:37_Starting_Tor_Connection_before_connecting_to_Wi-Fi.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:34:37_Starting_Tor_Connection_before_connecting_to_Wi-Fi.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:34:37_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
1:2.035
Scenario The Downloads directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Before features/support/hooks.rb:513 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.141
Then the live user's Downloads directory exists 0.061
And there is a GNOME bookmark for the Downloads directory 2.259
When I start the Tor Browser 31.250
And the Tor Browser loads the startup page 1.648
Then I can save the current page as "index.html" to the Downloads directory 13.672
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:22:in `save_page_as'
./features/step_definitions/browser.rb:565:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:24:in `Then I can save the current page as "index.html" to the Downloads directory'
And I can print the current page as "output.pdf" to the Downloads directory 0.000
After features/support/hooks.rb:521 0.037
After features/support/hooks.rb:330 8.722 
SCENARIO FAILED: 'The Downloads directory is usable in Tor Browser' (at time 06:57:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:57:40_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/14/artifact/build-artifacts/06:57:40_The_Downloads_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:57:40_The_Downloads_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:57:40_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.819
Scenario Downloading files with the Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Before features/support/hooks.rb:513 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.912
When I start the Tor Browser 33.182
Then the Tor Browser loads the startup page 1.638
When I download some file in the Tor Browser to the Downloads directory 25.086
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.038
After features/support/hooks.rb:330 8.906 
SCENARIO FAILED: 'Downloading files with the Tor Browser' (at time 06:59:03)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:59:03_Downloading_files_with_the_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:59:03_Downloading_files_with_the_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/06:59:03_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
44.628
Scenario The Tor Browser uses TBB's shared libraries
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.135
When I start the Tor Browser 29.882
Then the Tor Browser uses all expected TBB shared libraries 1.610
The 
The loaded shared libraries for the firefox process are not the way we expect them.
Expected TBB libs that are absent: ["libfreeblpriv3.so", "libgkcodecs.so", "liblgpllibs.so", "libmozgtk.so", "libmozsandbox.so", "libmozsqlite3.so", "libmozwayland.so", "libnspr4.so", "libnss3.so", "libnssckbi.so", "libnssutil3.so", "libplc4.so", "libplds4.so", "libsmime3.so", "libsoftokn3.so", "libssl3.so", "libxul.so"]
Native libs that we don't want: [].
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/browser.rb:243:in `xul_app_shared_lib_check'
./features/step_definitions/browser.rb:257:in `/^the (.*) uses all expected TBB shared libraries$/'
features/torified_browsing.feature:76:in `Then the Tor Browser uses all expected TBB shared libraries'
After features/support/hooks.rb:330 5.879 
SCENARIO FAILED: 'The Tor Browser uses TBB's shared libraries' (at time 07:04:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:04:41_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/14/artifact/build-artifacts/07:04:41_The_Tor_Browser_uses_TBB_s_shared_libraries.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:04:41_The_Tor_Browser_uses_TBB_s_shared_libraries.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:04:41_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:44.961
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.874
And the network is plugged 0.090
And I successfully configure Tor 26.773
And available upgrades have been checked 1.142
And all notifications have disappeared 6.282
And there is a GNOME bookmark for the Persistent directory 2.345
When I start the Tor Browser 30.872
And I download some file in the Tor Browser to the Persistent directory 26.579
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 10.500 
SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 07:09:52)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:09:52_The_Persistent_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:09:52_The_Persistent_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:09:52_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
1:1.685
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and logged in 9.562
Then the live user's Documents directory exists 0.069
And there is a GNOME bookmark for the Documents directory 2.703
Then I start the Tor Browser in offline mode 35.415
And I can save the current page as "index.html" to the Documents GNOME bookmark 13.935
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:22:in `save_page_as'
./features/step_definitions/browser.rb:565:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:127:in `And I can save the current page as "index.html" to the Documents GNOME bookmark'
features/torified_browsing.feature:124:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'
After features/support/hooks.rb:330 8.698 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#1)' (at time 07:11:04)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:11:04_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:11:04_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/14/artifact/build-artifacts/07:11:04_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
1:2.799
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 10.023
Then the live user's Downloads directory exists 0.123
And there is a GNOME bookmark for the Downloads directory 3.131
Then I start the Tor Browser in offline mode 35.740
And I can save the current page as "index.html" to the Downloads GNOME bookmark 13.780
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:22:in `save_page_as'
./features/step_definitions/browser.rb:565:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:128:in `And I can save the current page as "index.html" to the Downloads GNOME bookmark'
features/torified_browsing.feature:124:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'
After features/support/hooks.rb:330 7.768 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#2)' (at time 07:12:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:12:16_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/14/artifact/build-artifacts/07:12:16_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:12:16_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/14/artifact/build-artifacts/07:12:16_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
1:2.498
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD without network and logged in 9.471
Then the live user's Music directory exists 0.152
And there is a GNOME bookmark for the Music directory 2.336
Then I start the Tor Browser in offline mode 36.602
And I can save the current page as "index.html" to the Music GNOME bookmark 13.935
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:22:in `save_page_as'
./features/step_definitions/browser.rb:565:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:129:in `And I can save the current page as "index.html" to the Music GNOME bookmark'
features/torified_browsing.feature:124:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'
After features/support/hooks.rb:330 8.124 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#3)' (at time 07:13:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:13:26_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/14/artifact/build-artifacts/07:13:26_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:13:26_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/14/artifact/build-artifacts/07:13:26_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.528
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails from DVD without network and logged in 9.862
Then the live user's Pictures directory exists 0.137
And there is a GNOME bookmark for the Pictures directory 2.937
Then I start the Tor Browser in offline mode 34.591
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:130:in `Then I start the Tor Browser in offline mode'
features/torified_browsing.feature:123:in `Then I start the Tor Browser in offline mode'
And I can save the current page as "index.html" to the Pictures GNOME bookmark 0.000
After features/support/hooks.rb:330 8.875 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#4)' (at time 07:14:22)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:14:22_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:14:22_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/14/artifact/build-artifacts/07:14:22_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
47.414
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.734
Then the live user's Videos directory exists 0.134
And there is a GNOME bookmark for the Videos directory 3.150
Then I start the Tor Browser in offline mode 34.395
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:468:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:131:in `Then I start the Tor Browser in offline mode'
features/torified_browsing.feature:123:in `Then I start the Tor Browser in offline mode'
And I can save the current page as "index.html" to the Videos GNOME bookmark 0.000
After features/support/hooks.rb:330 9.336 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#5)' (at time 07:15:18)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:15:18_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:15:18_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/14/artifact/build-artifacts/07:15:18_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
6:55.076
Scenario Persistent browser bookmarks
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.788
And all tps features are active 2.518
And all persistent filesystems have safe access rights 0.256
And all persistence configuration files have safe access rights 0.489
And all persistent directories have safe access rights 2.842
When I start the Tor Browser in offline mode 38.144
And I add a bookmark to eff.org in the Tor Browser 11.490
And I cold reboot the computer 16.002
And the computer reboots Tails 1:55.471
And I enable persistence 20.707
And I log in to a new session 39.034
And all notifications have disappeared 13.738
And I start the Tor Browser in offline mode 2:23.591
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:469:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:455:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:146:in `And I start the Tor Browser in offline mode'
Then the Tor Browser has a bookmark to eff.org 0.000
After features/support/hooks.rb:330 8.788 
SCENARIO FAILED: 'Persistent browser bookmarks' (at time 07:22:23)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:22:23_Persistent_browser_bookmarks.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:22:23_Persistent_browser_bookmarks.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:22:23_Persistent_browser_bookmarks.journal
After features/support/hooks.rb:100 0.011
Feature: Browsing the web using the Unsafe Browser
Tags: @product @not_release_blocker
1:0.187
Scenario Starting a second instance of the Unsafe Browser results in an error message being shown
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.506
When I successfully start the Unsafe Browser 20.177
# Wait for whatever facility the GNOME Activities Overview uses to
# learn about which applications are running to "settle". Without
# this sleep, it is confused and it's impossible to start a new
# instance (it will just switch to the one we already started).
And I wait 10 seconds 10.007 
Slept for 10 seconds
And I try to start the Unsafe Browser 0.406
Then I see a warning about another instance already running 16.089
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'zenity' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/unsafe_browser.rb:76:in `new'
./features/step_definitions/unsafe_browser.rb:76:in `/^I see a warning about another instance already running$/'
features/unsafe_browser.feature:59:in `Then I see a warning about another instance already running'
After features/support/hooks.rb:330 10.948 
SCENARIO FAILED: 'Starting a second instance of the Unsafe Browser results in an error message being shown' (at time 07:32:16)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:32:16_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:32:16_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:32:16_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
22.812
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 9.402
And I cancel the GNOME authentication prompt 2.608
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 5.736
And I open this VeraCrypt volume in GNOME Files 4.315
Then I see the expected contents in this VeraCrypt volume 0.629
When I lock the currently opened VeraCrypt volume 0.119
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.499 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume' (at time 07:37:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:37:26_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/14/artifact/build-artifacts/07:37:26_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/14/artifact/build-artifacts/07:37:26_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/14/artifact/build-artifacts/07:37:26_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
23.494
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.483
And I cancel the GNOME authentication prompt 2.702
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 5.840
And I open this VeraCrypt volume in GNOME Files 3.930
Then I see the expected contents in this VeraCrypt volume 0.457
When I lock the currently opened VeraCrypt volume 0.080
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 6.321 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:38:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:38:06_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/14/artifact/build-artifacts/07:38:06_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/14/artifact/build-artifacts/07:38:06_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/14/artifact/build-artifacts/07:38:06_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
30.781
Scenario Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 16.333
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 8.975
And I open this VeraCrypt volume in GNOME Files 4.858
Then I see the expected contents in this VeraCrypt volume 0.462
When I lock the currently opened VeraCrypt file container 0.151
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.409 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM' (at time 07:38:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:38:54_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/14/artifact/build-artifacts/07:38:54_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/14/artifact/build-artifacts/07:38:54_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/14/artifact/build-artifacts/07:38:54_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
41.809
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 27.664
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 8.657
And I open this VeraCrypt volume in GNOME Files 4.769
Then I see the expected contents in this VeraCrypt volume 0.589
When I lock the currently opened VeraCrypt file container 0.128
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.474 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container' (at time 07:39:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:39:51_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/14/artifact/build-artifacts/07:39:51_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:39:51_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/14/artifact/build-artifacts/07:39:51_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.026
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
27.883
Scenario Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile
Steps
When I plug a USB drive containing a basic VeraCrypt volume with a keyfile 7.825
And I cancel the GNOME authentication prompt 3.670
And I unlock and mount this VeraCrypt volume with GNOME Disks 10.939
And I open this VeraCrypt volume in GNOME Files 4.838
Then I see the expected contents in this VeraCrypt volume 0.489
When I lock the currently opened VeraCrypt volume 0.118
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.371 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 07:40:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:40:34_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/14/artifact/build-artifacts/07:40:34_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/14/artifact/build-artifacts/07:40:34_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/14/artifact/build-artifacts/07:40:34_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
26.156
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.541
And I cancel the GNOME authentication prompt 2.699
And I unlock and mount this VeraCrypt volume with GNOME Disks 7.240
And I open this VeraCrypt volume in GNOME Files 4.946
Then I see the expected contents in this VeraCrypt volume 0.575
When I lock the currently opened VeraCrypt volume 0.152
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.421 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:41:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:41:15_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/14/artifact/build-artifacts/07:41:15_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/14/artifact/build-artifacts/07:41:15_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/14/artifact/build-artifacts/07:41:15_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
51.559
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.875
And I unlock and mount this VeraCrypt file container with GNOME Disks 22.631
And I open this VeraCrypt volume in GNOME Files 4.432
Then I see the expected contents in this VeraCrypt volume 0.487
When I lock the currently opened VeraCrypt file container 0.133
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.487 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 07:42:22)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:42:22_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/14/artifact/build-artifacts/07:42:22_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/14/artifact/build-artifacts/07:42:22_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/14/artifact/build-artifacts/07:42:22_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.016
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
54.803
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.814
And I unlock and mount this VeraCrypt file container with GNOME Disks 22.943
And I open this VeraCrypt volume in GNOME Files 4.412
Then I see the expected contents in this VeraCrypt volume 0.494
When I lock the currently opened VeraCrypt file container 0.139
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.428 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 07:43:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:43:32_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/14/artifact/build-artifacts/07:43:32_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:43:32_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:43:32_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.018
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
40.350
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.666
And I unlock and mount this VeraCrypt file container with GNOME Disks 18.409
And I open this VeraCrypt volume in GNOME Files 4.637
Then I see the expected contents in this VeraCrypt volume 0.520
When I lock the currently opened VeraCrypt file container 0.116
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.513 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM' (at time 07:44:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/14/artifact/build-artifacts/07:44:28_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/14/artifact/build-artifacts/07:44:28_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/14/artifact/build-artifacts/07:44:28_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/14/artifact/build-artifacts/07:44:28_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000