Project Number Date
test_Tails_ISO_feature-trixie 24 09 Jun 2025, 06:52

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
41.449
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 41.449
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:666:in `block (4 levels) in <top (required)>'
./features/step_definitions/tor.rb:665:in `each'
./features/step_definitions/tor.rb:665:in `find'
./features/step_definitions/tor.rb:665:in `block (3 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:663:in `block (2 levels) in <top (required)>'
./features/step_definitions/tor.rb:499:in `tca_configure'
./features/step_definitions/tor.rb:626: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: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 7.110 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:29:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/00:29:26_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/24/artifact/build-artifacts/00:29:26_Using_obfs4_pluggable_transports_from_a_QR_code.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/00:29:26_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/00:29:26_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:100 0.046
Feature: Using Tor bridges and pluggable transports
Tags: @product
1:11.459
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 1.785
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 31.890
Then the Tor Connection Assistant reports that it failed to connect 0.174
And tca.conf is empty 0.662
Given I scan a QR code from the error page in Tor Connection Assistant 36.947
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: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 9.657 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:30:59)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/00:30:59_TCA_can_scan_QR_code_after_a_connection_failure.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/00:30:59_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/00:30:59_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.045
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:42.584
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 9.535
And I wait until Tor is ready 3.533
When I disconnect the network through GNOME 12.099
And I connect the network through GNOME 12.105
Then the Tor Connection Assistant autostarts 0.136
And the Tor Connection Assistant connects to Tor 4.620
And I wait until Tor is ready 5:0.553
Time 
Time syncing failed (HtpdateError)
./features/step_definitions/common_steps.rb:707:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:705:in `/^the time has synced$/'
./features/step_definitions/common_steps.rb:658:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:89:in `And I wait until Tor is ready'
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.260 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:39:51)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/00:39:51_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/00:39:51_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log
Htpdate logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/00:39:51_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/00:39:51_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/00:39:51_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/00:39:51_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/24/artifact/build-artifacts/00:39:51_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.035
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
15.669
Scenario Erasure of memory freed by killed userspace processes
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 8.641
And I prepare Tails for memory erasure tests 0.466
When I start a process allocating 128 MiB of memory with a known pattern 2.834
Then patterns cover at least 128 MiB in the guest's memory 3.726
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.632 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:42:24)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/00:42:24_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/24/artifact/build-artifacts/00:42:24_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/00:42:24_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/00:42:24_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:15.645
Scenario I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:513 0.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:53.454
And I update APT using apt 12.133
And I install "popularity-contest" using apt 24.442
Then I am proposed to add the "popularity-contest" package to my Additional Software 14.258
When I create a persistent storage and activate the Additional Software feature 27.460
Then Additional Software is correctly configured for package "popularity-contest" 3.114
When I shutdown Tails and wait for the computer to power off 15.260
And I start Tails from USB drive "__internal" with network unplugged 1:51.091
And I enable persistence 28.722
And I log in to a new session 31.842
And the Additional Software installation service has started 50.895
Then I am notified that the installation succeeded 5:2.969
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:595:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
./features/step_definitions/additional_software_packages.rb:28:in `/^I am notified that the installation succeeded$/'
features/additional_software_packages.feature:39:in `Then I am notified that the installation succeeded'
And Additional Software is correctly configured for package "popularity-contest" 0.000
And the package "popularity-contest" is installed after Additional Software has been started 0.000
After features/support/hooks.rb:521 0.038
After features/support/hooks.rb:330 7.046 
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:35:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/01:35:44_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/24/artifact/build-artifacts/01:35:44_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/24/artifact/build-artifacts/01:35:44_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/24/artifact/build-artifacts/01:35:44_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/24/artifact/build-artifacts/01:35:44_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/24/artifact/build-artifacts/01:35:44_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/24/artifact/build-artifacts/01:35:44_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/24/artifact/build-artifacts/01:35:44_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/24/artifact/build-artifacts/01:35:44_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.012
Feature: Additional software
Tags: @product @check_tor_leaks @slow
25:10.463
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.006
Before features/support/hooks.rb:513 0.005
Steps
Given a computer 0.188
And I start Tails from USB drive "__internal" and I login with an administration password 2:53.424
And I update APT using apt 11.901
When I install "makepp" using apt 22:4.948
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.039
After features/support/hooks.rb:330 5.193 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 02:01:02)
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/24/artifact/build-artifacts/02:01:02_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/24/artifact/build-artifacts/02:01:02_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/24/artifact/build-artifacts/02:01:02_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/24/artifact/build-artifacts/02:01:02_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/24/artifact/build-artifacts/02:01:02_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/24/artifact/build-artifacts/02:01:02_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/24/artifact/build-artifacts/02:01:02_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/24/artifact/build-artifacts/02:01:02_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.013
Feature: Additional software
Tags: @product @check_tor_leaks @slow
10:42.238
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.007
Before features/support/hooks.rb:513 0.005
Steps
Given a computer 0.212
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 5:5.156
When I uninstall "popularity-contest" using apt 24.999
And I accept removing "popularity-contest" from Additional Software 2.740
Then "popularity-contest" is not in the list of Additional Software 0.789
When I start Synaptic 15.451
And I update APT using Synaptic 22.049
And I install "cowsay" using Synaptic 4:30.838
Tor 
Tor operation failed (despite retrying 10 times) with
Dogtail::Failure: The Dogtail init script raised: SearchError: child of [application | synaptic]: 'Find' dialog
STDOUT:

STDERR:

 (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:180:in `/^I install "(.+)" using Synaptic$/'
features/additional_software_packages.feature:61:in `And I install "cowsay" using Synaptic'
And I accept adding "cowsay" to Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I uninstall "cowsay" using apt 0.000
And I refuse removing "cowsay" from Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I remove "cowsay" from the list of Additional Software using Additional Software GUI 0.000
Then "cowsay" is not in the list of Additional Software 0.000
When I install "cowsay" using apt 0.000
And I refuse adding "cowsay" to Additional Software 0.000
Then "cowsay" is not in the list of Additional Software 0.000
After features/support/hooks.rb:521 0.035
After features/support/hooks.rb:330 5.682 
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:11:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/02:11:50_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/02:11:50_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/02:11:50_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/02:11:50_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/02:11:50_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/02:11:50_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/02:11:50_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/24/artifact/build-artifacts/02:11:50_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/24/artifact/build-artifacts/02:11:50_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.009
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
3:9.589
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.006
Before features/support/hooks.rb:513 0.006
Steps
Given a computer 0.257
And I start Tails from USB drive "__internal" with network unplugged 1:47.963
And I enable persistence 15.799
And I remove the "cowsay" deb files from the APT cache 0.069
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.089
And I log in to a new session 34.592
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 19.369
And I can open the Additional Software log file from the notification 11.447
The 
The Dogtail init script raised: SearchError: descendant of [notification | ]: 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:39:in `click_gnome_shell_notification_button'
./features/step_definitions/additional_software_packages.rb:166: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.041
After features/support/hooks.rb:330 6.763 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 02:28:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/02:28:08_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/24/artifact/build-artifacts/02:28:08_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/24/artifact/build-artifacts/02:28:08_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/24/artifact/build-artifacts/02:28:08_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/24/artifact/build-artifacts/02:28:08_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/24/artifact/build-artifacts/02:28:08_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/24/artifact/build-artifacts/02:28:08_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/02:28:08_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/24/artifact/build-artifacts/02:28:08_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.009
Feature: Upgrading an old Tails USB installation
Tags: @product
2:20.265
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.127
When I start Tails from USB drive "old" with network unplugged 1:46.827
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:453:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:25:in `When I start Tails from USB drive "old" with network unplugged'
Then the boot device has safe access rights 0.000
And Tails is running from USB drive "old" 0.000
And there is no persistence partition on USB drive "old" 0.000
And process "udev-watchdog" is running 0.000
And udev-watchdog is monitoring the correct device 0.000
And I unplug USB drive "old" 0.000
After features/support/hooks.rb:330 5.892 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:30:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/02:30:35_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/24/artifact/build-artifacts/02:30:35_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/02:30:35_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/24/artifact/build-artifacts/02:30:35_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:19.388
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.006
Steps
Given a computer 0.305
And I start Tails from USB drive "old" with network unplugged and I login 1:19.082
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:453:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:36:in `And I start Tails from USB drive "old" with network unplugged and I login'
Then Tails is running from USB drive "old" 0.000
And I create a persistent partition 0.000
And I take note of which tps features are available 0.000
Then a Tails persistence partition exists on USB drive "old" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
After features/support/hooks.rb:330 5.833 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:32:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/02:32:00_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/24/artifact/build-artifacts/02:32:00_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/02:32:00_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/02:32:00_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.637
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.006
Steps
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:19.430
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:453:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:276:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:330 5.739 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:33:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/02:33:26_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/24/artifact/build-artifacts/02:33:26_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/24/artifact/build-artifacts/02:33:26_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/24/artifact/build-artifacts/02:33:26_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.008
Feature: Upgrading an old Tails USB installation
Tags: @product
2:2.399
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given a computer 0.273
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.126
The 
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:283:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:330 5.858 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:38:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/02:38:25_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/24/artifact/build-artifacts/02:38:25_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/24/artifact/build-artifacts/02:38:25_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/24/artifact/build-artifacts/02:38:25_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.010
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
22:58.184
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.493
And no SquashFS delta is installed 0.138
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.451
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.296
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.516
When the network is plugged 0.142
And Tor is ready 28.217
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:13.833
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.552 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:01:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:01:29_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/24/artifact/build-artifacts/03:01:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:01:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:01:29_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:48.539
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.972
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.357
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 25.321
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:11.654
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.672 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:24:24)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:24:24_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/24/artifact/build-artifacts/03:24:24_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:24:24_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:24:24_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
0.100
Scenario Getting a DHCP lease with the default NetworkManager connection
Steps
Then the hostname should not have been leaked on the network 0.100
Hostname 
Hostname leak detected (DhcpLeakError)
./features/step_definitions/dhcp.rb:15:in `/^the hostname should not have been leaked on the network$/'
features/dhcp.feature:17:in `Then the hostname should not have been leaked on the network'
After features/support/hooks.rb:330 4.919 
SCENARIO FAILED: 'Getting a DHCP lease with the default NetworkManager connection' (at time 03:34:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:34:31_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/24/artifact/build-artifacts/03:34:31_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.pcap
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:34:31_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:34:31_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:34:31_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.048
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
2.037
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.964
And I switch to the "manually-added-con" NetworkManager connection 0.967
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:22:in `Then the hostname should not have been leaked on the network'
After features/support/hooks.rb:330 4.904 
SCENARIO FAILED: 'Getting a DHCP lease with a manually configured NetworkManager connection' (at time 03:35:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:35:08_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/24/artifact/build-artifacts/03:35:08_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.pcap
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:35:08_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:35:08_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:35:08_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.082
Feature: Hardware failures
Tags: @product
3:10.554
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 30.687
And I corrupt the boot device's GPT backup header 0.574
And I power off the computer 0.331
When I start the computer 1.047
Then the computer boots Tails 1:49.484
When I log in to a new session 29.194
And all notifications have disappeared 18.850
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.383
<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.629 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#1)' (at time 03:52:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:52:18_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/24/artifact/build-artifacts/03:52:18_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:52:18_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:52:18_GPT_backup_corruption_with_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:100 0.012
Feature: Hardware failures
Tags: @product
2:47.283
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 9.507
And I corrupt the boot device's GPT backup partition table 0.427
And I power off the computer 0.347
When I start the computer 1.143
Then the computer boots Tails 1:47.568
When I log in to a new session 35.091
And all notifications have disappeared 12.907
Then I am recommended to migrate to a new USB stick due to partitioning errors 0.289
<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.110 
SCENARIO FAILED: 'GPT backup corruption with a persistent partition, Examples (#2)' (at time 03:55:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:55: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/24/artifact/build-artifacts/03:55:12_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:55:12_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:55:12_GPT_backup_corruption_with_a_persistent_partition,_Examples___2_.journal
After features/support/hooks.rb:100 0.011
Feature: Hardware failures
Tags: @product
4:7.081
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.219
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.053
And I plug USB drive "temp" 1.061
And I write the Tails USB image to disk "temp" 34.375
When I start Tails from USB drive "temp" with network unplugged 2:47.844
Then Tails is running from USB drive "temp" 0.429
And the Greeter forbids creating a persistent partition 0.102
When I log in to a new session 30.582
And all notifications have disappeared 12.188
Then I am recommended to reinstall Tails due to partitioning errors 0.222
<"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.553 
SCENARIO FAILED: 'GPT backup corruption without a persistent partition' (at time 03:59:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:59:26_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/24/artifact/build-artifacts/03:59:26_GPT_backup_corruption_without_a_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:59:26_GPT_backup_corruption_without_a_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/03:59:26_GPT_backup_corruption_without_a_persistent_partition.journal
After features/support/hooks.rb:100 0.105
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
8.871
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 8.700
Then the keys trusted by APT are valid for the next 3 months 0.171
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.238 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 04:09:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/04:09:46_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/24/artifact/build-artifacts/04:09:46_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/04:09:46_The_included_APT_repository_keys_are_up-to-date.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/04:09:46_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:7.356
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 7.907
When I log in to a new session in German (de) 44.832
Then the keyboard layout is set to "de" 0.301
When the network is plugged 0.111
And Tor is ready 19.909
Then I successfully start the Unsafe Browser 15.973
And I kill the Unsafe Browser 7.520
When I enable the screen keyboard 0.241
Then the screen keyboard works in Tor Browser 30.559
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:1040:in `launch_app'
./features/step_definitions/common_steps.rb:1095:in `launch_tor_browser'
./features/step_definitions/browser.rb:456:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:422: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 "de" 0.000
After features/support/hooks.rb:330 10.010 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#5)' (at time 04:31:04)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/04:31:04_Tails_is_localized_for_every_tier-1_language,_Examples___5_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/04:31:04_Tails_is_localized_for_every_tier-1_language,_Examples___5_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/04:31:04_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
2:12.837
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.034
When I log in to a new session in Hindi (hi) 43.237
Then the keyboard layout is set to "in" 0.399
When the network is plugged 0.079
And Tor is ready 25.341
Then I successfully start the Unsafe Browser 17.481
And I kill the Unsafe Browser 7.590
When I enable the screen keyboard 0.220
Then the screen keyboard works in Tor Browser 30.452
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:1040:in `launch_app'
./features/step_definitions/common_steps.rb:1095:in `launch_tor_browser'
./features/step_definitions/browser.rb:456:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:422: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 "us" 0.000
After features/support/hooks.rb:330 10.579 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#6)' (at time 04:33:27)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/04:33:27_Tails_is_localized_for_every_tier-1_language,_Examples___6_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/04:33:27_Tails_is_localized_for_every_tier-1_language,_Examples___6_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/04:33:27_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
2:15.322
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.760
When I log in to a new session in Portuguese (pt) 46.399
Then the keyboard layout is set to "pt" 0.532
When the network is plugged 0.131
And Tor is ready 24.043
Then I successfully start the Unsafe Browser 16.888
And I kill the Unsafe Browser 7.970
When I enable the screen keyboard 0.220
Then the screen keyboard works in Tor Browser 30.375
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:1040:in `launch_app'
./features/step_definitions/common_steps.rb:1095:in `launch_tor_browser'
./features/step_definitions/browser.rb:456:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:422:in `/^the screen keyboard works in Tor Browser$/'
features/localization.feature:52:in `Then the screen keyboard works in Tor Browser'
features/localization.feature:30:in `Then the screen keyboard works in Tor Browser'
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:330 10.897 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#10)' (at time 04:45:56)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/04:45:56_Tails_is_localized_for_every_tier-1_language,_Examples___10_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/04:45:56_Tails_is_localized_for_every_tier-1_language,_Examples___10_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/04:45:56_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:13.305
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.200
When I log in to a new session in Spanish (es) 44.964
Then the keyboard layout is set to "es" 0.485
When the network is plugged 0.114
And Tor is ready 21.593
Then I successfully start the Unsafe Browser 19.227
And I kill the Unsafe Browser 7.983
When I enable the screen keyboard 0.199
Then the screen keyboard works in Tor Browser 30.535
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:1040:in `launch_app'
./features/step_definitions/common_steps.rb:1095:in `launch_tor_browser'
./features/step_definitions/browser.rb:456:in `/^I start the Tor Browser( in offline mode)?$/'
./features/step_definitions/browser.rb:422: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 11.897 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#12)' (at time 04:51:36)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/04:51:36_Tails_is_localized_for_every_tier-1_language,_Examples___12_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/04:51:36_Tails_is_localized_for_every_tier-1_language,_Examples___12_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/04:51:36_Tails_is_localized_for_every_tier-1_language,_Examples___12_.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
51.302
Scenario Chatting with some friend over XMPP
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:513 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 15.494
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 10.882
Then I see Pidgin's account manager window 3.974
When I create my XMPP account 20.952
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.057
After features/support/hooks.rb:330 6.222 
SCENARIO FAILED: 'Chatting with some friend over XMPP' (at time 06:13:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:13:51_Chatting_with_some_friend_over_XMPP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:13:51_Chatting_with_some_friend_over_XMPP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:13:51_Chatting_with_some_friend_over_XMPP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:13:51_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
51.134
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.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 14.997
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 10.915
Then I see Pidgin's account manager window 4.180
When I create my XMPP account 21.041
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.033
After features/support/hooks.rb:330 5.735 
SCENARIO FAILED: 'Chatting with some friend over XMPP in a multi-user chat' (at time 06:14:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:14:49_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/24/artifact/build-artifacts/06:14:49_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:14:49_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/24/artifact/build-artifacts/06:14:49_Chatting_with_some_friend_over_XMPP_in_a_multi-user_chat.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
47.821
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.006
Before features/support/hooks.rb:513 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.149
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 10.907
Then I see Pidgin's account manager window 3.886
And I create my XMPP account 20.878
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.047
After features/support/hooks.rb:330 5.859 
SCENARIO FAILED: 'Connecting to the tails multi-user chat with my XMPP account' (at time 06:15:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:15:42_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/24/artifact/build-artifacts/06:15:42_Connecting_to_the_tails_multi-user_chat_with_my_XMPP_account.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:15:42_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/24/artifact/build-artifacts/06:15:42_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:26.609
Scenario Using a persistent Pidgin configuration
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:513 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.998
And the network is plugged 0.110
And Tor is ready 27.979
And available upgrades have been checked 1.172
And all notifications have disappeared 5.562
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 10.920
Then I see Pidgin's account manager window 4.109
When I create my XMPP account 20.756
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.055
After features/support/hooks.rb:330 5.596 
SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 06:17:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:17:15_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:17:15_Using_a_persistent_Pidgin_configuration.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:17:15_Using_a_persistent_Pidgin_configuration.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:17:15_Using_a_persistent_Pidgin_configuration.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
24.022
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.011
Steps
Given I have started Tails from DVD without network and logged in 23.922
Then there are no unexpected messages of priority "err" or higher in the journal 0.100
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": "581",
    "_BOOT_ID": "7db78220a0fd4bd0bfb332881f202042",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "581",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749424987751097",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "71fcd037ed52436bbd74a91fe85832ba",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=4bcf264dc9c24d29bbf99604b1713f92;i=35a;b=7db78220a0fd4bd0bfb332881f202042;m=b7d397;t=63717bef4dafb;x=15c74b052446e95f",
    "__MONOTONIC_TIMESTAMP": "12047255",
    "__REALTIME_TIMESTAMP": "1749424987757307",
    "__SEQNUM": "858",
    "__SEQNUM_ID": "4bcf264dc9c24d29bbf99604b1713f92"
  },
  {
    "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": "581",
    "_BOOT_ID": "7db78220a0fd4bd0bfb332881f202042",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "581",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749424987751123",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "71fcd037ed52436bbd74a91fe85832ba",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=4bcf264dc9c24d29bbf99604b1713f92;i=35c;b=7db78220a0fd4bd0bfb332881f202042;m=b7d448;t=63717bef4dbad;x=624e8b02cd97de36",
    "__MONOTONIC_TIMESTAMP": "12047432",
    "__REALTIME_TIMESTAMP": "1749424987757485",
    "__SEQNUM": "860",
    "__SEQNUM_ID": "4bcf264dc9c24d29bbf99604b1713f92"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2332",
    "SYSLOG_TIMESTAMP": "Jun  8 23:23:15 ",
    "_BOOT_ID": "7db78220a0fd4bd0bfb332881f202042",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2332",
    "_RUNTIME_SCOPE": "system",
    "_SOURCE_REALTIME_TIMESTAMP": "1749424995484088",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=4bcf264dc9c24d29bbf99604b1713f92;i=408;b=7db78220a0fd4bd0bfb332881f202042;m=12ddbd5;t=63717bf6ae33a;x=3cecb91bcd9eedae",
    "__MONOTONIC_TIMESTAMP": "19782613",
    "__REALTIME_TIMESTAMP": "1749424995492666",
    "__SEQNUM": "1032",
    "__SEQNUM_ID": "4bcf264dc9c24d29bbf99604b1713f92"
  },
  {
    "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": "581",
    "_BOOT_ID": "7db78220a0fd4bd0bfb332881f202042",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "581",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749425167870270",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "71fcd037ed52436bbd74a91fe85832ba",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=4bcf264dc9c24d29bbf99604b1713f92;i=8d1;b=7db78220a0fd4bd0bfb332881f202042;m=5f0f439;t=63717c9b1296e;x=dce70af8d347fac3",
    "__MONOTONIC_TIMESTAMP": "99677241",
    "__REALTIME_TIMESTAMP": "1749425167870318",
    "__SEQNUM": "2257",
    "__SEQNUM_ID": "4bcf264dc9c24d29bbf99604b1713f92"
  },
  {
    "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": "581",
    "_BOOT_ID": "7db78220a0fd4bd0bfb332881f202042",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "581",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749425167870316",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "71fcd037ed52436bbd74a91fe85832ba",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=4bcf264dc9c24d29bbf99604b1713f92;i=8d3;b=7db78220a0fd4bd0bfb332881f202042;m=5f0f5ea;t=63717c9b12b20;x=c62f127039afbcd8",
    "__MONOTONIC_TIMESTAMP": "99677674",
    "__REALTIME_TIMESTAMP": "1749425167870752",
    "__SEQNUM": "2259",
    "__SEQNUM_ID": "4bcf264dc9c24d29bbf99604b1713f92"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "7285",
    "SYSLOG_TIMESTAMP": "Jun  8 23:26:13 ",
    "_BOOT_ID": "7db78220a0fd4bd0bfb332881f202042",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "7285",
    "_RUNTIME_SCOPE": "system",
    "_SOURCE_REALTIME_TIMESTAMP": "1749425173042201",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=4bcf264dc9c24d29bbf99604b1713f92;i=1253;b=7db78220a0fd4bd0bfb332881f202042;m=63fec32;t=63717ca002168;x=d1c32b9c85d70908",
    "__MONOTONIC_TIMESTAMP": "104852530",
    "__REALTIME_TIMESTAMP": "1749425173045608",
    "__SEQNUM": "4691",
    "__SEQNUM_ID": "4bcf264dc9c24d29bbf99604b1713f92"
  }
].
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:237:in `/^there are no unexpected messages of priority "err" or higher in the journal$/'
features/sane_defaults.feature:21:in `Then there are no unexpected messages of priority "err" or higher in the journal'
After features/support/hooks.rb:330 5.535 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from DVD' (at time 06:22:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:22:52_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/24/artifact/build-artifacts/06:22:52_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:22:52_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/24/artifact/build-artifacts/06:22:52_No_unexpected_error_messages_in_the_journal_after_booting_from_DVD.journal
After features/support/hooks.rb:100 0.000
Feature: Tails has a sane default configuration
Tags: @product
15.202
Scenario No unexpected error messages in the journal after booting from USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.090
Then there are no unexpected messages of priority "err" or higher in the journal 0.111
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": "710",
    "_BOOT_ID": "3d093a8996914beba3aefb269bb7e8c9",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "710",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749427400330352",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "609a98b897c04b95addf9ed1563e0dff",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=df68648638f043688c9e789bb3aa7c26;i=379;b=3d093a8996914beba3aefb269bb7e8c9;m=e1f2ad;t=637184ec1cc7c;x=b6e8754d9584282f",
    "__MONOTONIC_TIMESTAMP": "14807725",
    "__REALTIME_TIMESTAMP": "1749427400330364",
    "__SEQNUM": "889",
    "__SEQNUM_ID": "df68648638f043688c9e789bb3aa7c26"
  },
  {
    "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": "710",
    "_BOOT_ID": "3d093a8996914beba3aefb269bb7e8c9",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "710",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749427400330510",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "609a98b897c04b95addf9ed1563e0dff",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=df68648638f043688c9e789bb3aa7c26;i=37b;b=3d093a8996914beba3aefb269bb7e8c9;m=e1f343;t=637184ec1cd12;x=8c849d29a4e7da73",
    "__MONOTONIC_TIMESTAMP": "14807875",
    "__REALTIME_TIMESTAMP": "1749427400330514",
    "__SEQNUM": "891",
    "__SEQNUM_ID": "df68648638f043688c9e789bb3aa7c26"
  },
  {
    "MESSAGE": "The group `powerdev' does not exist.",
    "SYSLOG_IDENTIFIER": "adduser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "2522",
    "SYSLOG_TIMESTAMP": "Jun  9 00:03:28 ",
    "_BOOT_ID": "3d093a8996914beba3aefb269bb7e8c9",
    "_CAP_EFFECTIVE": "1ffffffffff",
    "_CMDLINE": "adduser",
    "_COMM": "adduser",
    "_EXE": "/usr/bin/perl",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "2522",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749427408477368",
    "_SYSTEMD_CGROUP": "/system.slice/live-config.service",
    "_SYSTEMD_INVOCATION_ID": "d12eee5de5e94815ac710265cba90a24",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "live-config.service",
    "_TRANSPORT": "syslog",
    "_UID": "0",
    "__CURSOR": "s=df68648638f043688c9e789bb3aa7c26;i=40d;b=3d093a8996914beba3aefb269bb7e8c9;m=15e42fb;t=637184f3e1cc9;x=57a39ae490f21b40",
    "__MONOTONIC_TIMESTAMP": "22954747",
    "__REALTIME_TIMESTAMP": "1749427408477385",
    "__SEQNUM": "1037",
    "__SEQNUM_ID": "df68648638f043688c9e789bb3aa7c26"
  },
  {
    "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": "710",
    "_BOOT_ID": "3d093a8996914beba3aefb269bb7e8c9",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "710",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749427542453765",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "609a98b897c04b95addf9ed1563e0dff",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=df68648638f043688c9e789bb3aa7c26;i=e54;b=3d093a8996914beba3aefb269bb7e8c9;m=925209b;t=63718573a8a7c;x=23dab38fe9ba6913",
    "__MONOTONIC_TIMESTAMP": "153428123",
    "__REALTIME_TIMESTAMP": "1749427542461052",
    "__SEQNUM": "3668",
    "__SEQNUM_ID": "df68648638f043688c9e789bb3aa7c26"
  },
  {
    "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": "710",
    "_BOOT_ID": "3d093a8996914beba3aefb269bb7e8c9",
    "_CAP_EFFECTIVE": "1f7fdffffff",
    "_CMDLINE": "/usr/lib/systemd/systemd-udevd",
    "_COMM": "systemd-udevd",
    "_EXE": "/usr/bin/udevadm",
    "_GID": "0",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_PID": "710",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749427542453795",
    "_SYSTEMD_CGROUP": "/system.slice/systemd-udevd.service/udev",
    "_SYSTEMD_INVOCATION_ID": "609a98b897c04b95addf9ed1563e0dff",
    "_SYSTEMD_SLICE": "system.slice",
    "_SYSTEMD_UNIT": "systemd-udevd.service",
    "_TRANSPORT": "journal",
    "_UID": "0",
    "__CURSOR": "s=df68648638f043688c9e789bb3aa7c26;i=e56;b=3d093a8996914beba3aefb269bb7e8c9;m=925223f;t=63718573a8c1f;x=626c8f897c29a6c6",
    "__MONOTONIC_TIMESTAMP": "153428543",
    "__REALTIME_TIMESTAMP": "1749427542461471",
    "__SEQNUM": "3670",
    "__SEQNUM_ID": "df68648638f043688c9e789bb3aa7c26"
  },
  {
    "MESSAGE": "The user `amnesia' is not a member of group `sudo'.",
    "SYSLOG_IDENTIFIER": "deluser",
    "PRIORITY": "2",
    "SYSLOG_FACILITY": "1",
    "SYSLOG_PID": "12166",
    "SYSLOG_TIMESTAMP": "Jun  9 00:05:49 ",
    "_AUDIT_LOGINUID": "1000",
    "_AUDIT_SESSION": "4",
    "_BOOT_ID": "3d093a8996914beba3aefb269bb7e8c9",
    "_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": "12166",
    "_RUNTIME_SCOPE": "system",
    "_SELINUX_CONTEXT": "unconfined\n",
    "_SOURCE_REALTIME_TIMESTAMP": "1749427549118288",
    "_SYSTEMD_CGROUP": "/user.slice/user-1000.slice/session-4.scope",
    "_SYSTEMD_INVOCATION_ID": "eb1d800e619e4747b843138a37832d70",
    "_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=df68648638f043688c9e789bb3aa7c26;i=1849;b=3d093a8996914beba3aefb269bb7e8c9;m=98ab579;t=6371857a01f5a;x=c45da6739f08574b",
    "__MONOTONIC_TIMESTAMP": "160085369",
    "__REALTIME_TIMESTAMP": "1749427549118298",
    "__SEQNUM": "6217",
    "__SEQNUM_ID": "df68648638f043688c9e789bb3aa7c26"
  }
].
<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.317 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 06:23:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:23:13_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/24/artifact/build-artifacts/06:23:13_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/24/artifact/build-artifacts/06:23:13_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/24/artifact/build-artifacts/06:23:13_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
27.057
Scenario I can shutdown Tails via the system menu
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.022
When I request a shutdown using the system menu 14.035
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/support/helpers/dogtail.rb:371:in `grabFocus'
./features/step_definitions/common_steps.rb:887: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.695 
SCENARIO FAILED: 'I can shutdown Tails via the system menu' (at time 06:23:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:23:46_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/24/artifact/build-artifacts/06:23:46_I_can_shutdown_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:23:46_I_can_shutdown_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:23:46_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
37.291
Scenario I can reboot Tails via the system menu
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 23.237
When I request a reboot using the system menu 14.054
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/support/helpers/dogtail.rb:371:in `grabFocus'
./features/step_definitions/common_steps.rb:887:in `/^I request a (shutdown|reboot) using the system menu$/'
features/shutdown_applet.feature:12:in `When I request a reboot using the system menu'
Then Tails eventually restarts 0.000
After features/support/hooks.rb:330 6.167 
SCENARIO FAILED: 'I can reboot Tails via the system menu' (at time 06:24:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:24:29_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/24/artifact/build-artifacts/06:24:29_I_can_reboot_Tails_via_the_system_menu.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:24:29_I_can_reboot_Tails_via_the_system_menu.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:24:29_I_can_reboot_Tails_via_the_system_menu.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
1:42.630
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.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 11.964
Then the live user's Downloads directory exists 0.054
And there is a GNOME bookmark for the Downloads directory 20.312
When I start the Tor Browser 29.624
And the Tor Browser loads the startup page 2.059
Then I can save the current page as "index.html" to the Downloads directory 38.615
The 
The page was not saved to /home/amnesia/Downloads/index.html (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:546: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.032
After features/support/hooks.rb:330 6.477 
SCENARIO FAILED: 'The Downloads directory is usable in Tor Browser' (at time 06:52:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:52:03_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/24/artifact/build-artifacts/06:52:03_The_Downloads_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:52:03_The_Downloads_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:52:03_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:18.200
Scenario Downloading files with the Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:513 0.005
Steps
Given I have started Tails from DVD and logged in and the network is connected 11.998
When I start the Tor Browser 27.831
Then the Tor Browser loads the startup page 1.688
When I download some file in the Tor Browser to the Downloads directory 36.682
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:6:in `new'
./features/step_definitions/browser.rb:6:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:310: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.039
After features/support/hooks.rb:330 10.142 
SCENARIO FAILED: 'Downloading files with the Tor Browser' (at time 06:53:28)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:53:28_Downloading_files_with_the_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:53:28_Downloading_files_with_the_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:53:28_Downloading_files_with_the_Tor_Browser.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
46.758
Scenario The Tor Browser uses TBB's shared libraries
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.338
When I start the Tor Browser 28.912
Then the Tor Browser uses all expected TBB shared libraries 5.507
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:259:in `xul_app_shared_lib_check'
./features/step_definitions/browser.rb:273: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.743 
SCENARIO FAILED: 'The Tor Browser uses TBB's shared libraries' (at time 06:59:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:59:12_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/24/artifact/build-artifacts/06:59:12_The_Tor_Browser_uses_TBB_s_shared_libraries.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:59:12_The_Tor_Browser_uses_TBB_s_shared_libraries.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/06:59:12_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:57.045
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.273
And the network is plugged 0.359
And I successfully configure Tor 24.828
And available upgrades have been checked 1.153
And all notifications have disappeared 5.139
And there is a GNOME bookmark for the Persistent directory 20.405
When I start the Tor Browser 25.829
And I download some file in the Tor Browser to the Persistent directory 28.057
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:6:in `new'
./features/step_definitions/browser.rb:6:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:310: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.682 
SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 07:04:47)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:04:47_The_Persistent_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:04:47_The_Persistent_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:04:47_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:19.049
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD without network and logged in 8.715
Then the live user's Documents directory exists 0.111
And there is a GNOME bookmark for the Documents directory 17.982
Then I start the Tor Browser in offline mode 22.801
And I can save the current page as "index.html" to the Documents GNOME bookmark 29.439
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:6:in `new'
./features/step_definitions/browser.rb:6:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:38:in `browser_save_page_as'
./features/step_definitions/browser.rb:543: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 9.002 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#1)' (at time 07:06:17)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:06:17_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:06:17_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/24/artifact/build-artifacts/07:06:17_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:17.270
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD without network and logged in 9.353
Then the live user's Downloads directory exists 0.218
And there is a GNOME bookmark for the Downloads directory 19.340
Then I start the Tor Browser in offline mode 31.105
And I can save the current page as "index.html" to the Downloads GNOME bookmark 17.251
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:6:in `new'
./features/step_definitions/browser.rb:6:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:38:in `browser_save_page_as'
./features/step_definitions/browser.rb:543: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 9.587 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#2)' (at time 07:07:43)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:07:43_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:07:43_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/24/artifact/build-artifacts/07:07:43_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:17.816
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD without network and logged in 9.151
Then the live user's Music directory exists 0.180
And there is a GNOME bookmark for the Music directory 19.349
Then I start the Tor Browser in offline mode 26.254
And I can save the current page as "index.html" to the Music GNOME bookmark 22.880
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:6:in `new'
./features/step_definitions/browser.rb:6:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:38:in `browser_save_page_as'
./features/step_definitions/browser.rb:543: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 9.835 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#3)' (at time 07:09:10)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:09:10_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:09:10_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/24/artifact/build-artifacts/07:09:10_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
1:17.641
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails from DVD without network and logged in 9.231
Then the live user's Pictures directory exists 0.065
And there is a GNOME bookmark for the Pictures directory 18.189
Then I start the Tor Browser in offline mode 25.647
And I can save the current page as "index.html" to the Pictures GNOME bookmark 24.507
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:6:in `new'
./features/step_definitions/browser.rb:6:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:38:in `browser_save_page_as'
./features/step_definitions/browser.rb:543:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:130:in `And I can save the current page as "index.html" to the Pictures 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 9.049 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#4)' (at time 07:10:38)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:10:38_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___4_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:10:38_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/24/artifact/build-artifacts/07:10:38_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
1:12.708
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD without network and logged in 8.808
Then the live user's Videos directory exists 0.199
And there is a GNOME bookmark for the Videos directory 18.017
Then I start the Tor Browser in offline mode 22.941
And I can save the current page as "index.html" to the Videos GNOME bookmark 22.741
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'org.gnome.Nautilus' application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:6:in `new'
./features/step_definitions/browser.rb:6:in `desktop_portal_save_as'
./features/step_definitions/browser.rb:38:in `browser_save_page_as'
./features/step_definitions/browser.rb:543:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:131:in `And I can save the current page as "index.html" to the Videos GNOME bookmark'
features/torified_browsing.feature:124:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'
After features/support/hooks.rb:330 9.084 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#5)' (at time 07:12:00)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:12:00_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:12:00_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/24/artifact/build-artifacts/07:12:00_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product @not_release_blocker
54.312
Scenario Starting a second instance of the Unsafe Browser results in an error message being shown
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.443
When I successfully start the Unsafe Browser 20.084
# Wait for whatever facility the GNOME Activities Overview uses to
# learn about which applications are running to "settle". Without
# this sleep, it is confused and it's impossible to start a new
# instance (it will just switch to the one we already started).
And I wait 10 seconds 10.010 
Slept for 10 seconds
And I try to start the Unsafe Browser 0.260
Then I see a warning about another instance already running 10.514
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 11.001 
SCENARIO FAILED: 'Starting a second instance of the Unsafe Browser results in an error message being shown' (at time 07:26:24)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:26:24_Starting_a_second_instance_of_the_Unsafe_Browser_results_in_an_error_message_being_shown.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:26:24_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/24/artifact/build-artifacts/07:26:24_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/24/artifact/build-artifacts/07:26:24_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
24.977
Scenario Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume
Steps
When I plug a USB drive containing a basic VeraCrypt volume 8.404
And I cancel the GNOME authentication prompt 2.463
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 6.824
And I open this VeraCrypt volume in GNOME Files 6.430
Then I see the expected contents in this VeraCrypt volume 0.753
When I lock the currently opened VeraCrypt volume 0.100
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:330: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 8.448 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume' (at time 07:31:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:31:14_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/24/artifact/build-artifacts/07:31:14_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/24/artifact/build-artifacts/07:31:14_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/24/artifact/build-artifacts/07:31:14_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
30.263
Scenario Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume
Steps
When I plug a USB drive containing a hidden VeraCrypt volume 11.874
And I cancel the GNOME authentication prompt 2.455
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 7.403
And I open this VeraCrypt volume in GNOME Files 7.955
Then I see the expected contents in this VeraCrypt volume 0.475
When I lock the currently opened VeraCrypt volume 0.098
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:330: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.635 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:32:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:32:02_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/24/artifact/build-artifacts/07:32:02_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/24/artifact/build-artifacts/07:32:02_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/24/artifact/build-artifacts/07:32:02_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
32.014
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.764
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 9.657
And I open this VeraCrypt volume in GNOME Files 5.037
Then I see the expected contents in this VeraCrypt volume 0.452
When I lock the currently opened VeraCrypt file container 0.101
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:330: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.346 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM' (at time 07:32:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:32:50_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/24/artifact/build-artifacts/07:32:50_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/24/artifact/build-artifacts/07:32:50_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/24/artifact/build-artifacts/07:32:50_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
44.396
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 11.499
And I open this VeraCrypt volume in GNOME Files 4.655
Then I see the expected contents in this VeraCrypt volume 0.473
When I lock the currently opened VeraCrypt file container 0.103
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:330: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.306 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container' (at time 07:33:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:33:48_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/24/artifact/build-artifacts/07:33:48_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:33:48_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/24/artifact/build-artifacts/07:33:48_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.017
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
29.971
Scenario Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile
Steps
When I plug a USB drive containing a basic VeraCrypt volume with a keyfile 8.281
And I cancel the GNOME authentication prompt 2.428
And I unlock and mount this VeraCrypt volume with GNOME Disks 13.250
And I open this VeraCrypt volume in GNOME Files 5.339
Then I see the expected contents in this VeraCrypt volume 0.541
When I lock the currently opened VeraCrypt volume 0.129
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:330: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 6.038 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 07:34:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:34:33_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/24/artifact/build-artifacts/07:34:33_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/24/artifact/build-artifacts/07:34:33_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/24/artifact/build-artifacts/07:34:33_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.journal
After features/support/hooks.rb:100 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
28.695
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 12.298
And I cancel the GNOME authentication prompt 2.433
And I unlock and mount this VeraCrypt volume with GNOME Disks 6.986
And I open this VeraCrypt volume in GNOME Files 6.351
Then I see the expected contents in this VeraCrypt volume 0.481
When I lock the currently opened VeraCrypt volume 0.143
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:330: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 6.963 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:35:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:35:17_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/24/artifact/build-artifacts/07:35:17_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/24/artifact/build-artifacts/07:35:17_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/24/artifact/build-artifacts/07:35:17_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
53.593
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.586
And I unlock and mount this VeraCrypt file container with GNOME Disks 24.314
And I open this VeraCrypt volume in GNOME Files 4.887
Then I see the expected contents in this VeraCrypt volume 0.694
When I lock the currently opened VeraCrypt file container 0.109
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:330: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.624 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 07:36:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:36:27_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/24/artifact/build-artifacts/07:36:27_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/24/artifact/build-artifacts/07:36:27_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/24/artifact/build-artifacts/07:36:27_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.015
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
53.758
Scenario Use GNOME Disks to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 27.110
And I unlock and mount this VeraCrypt file container with GNOME Disks 20.588
And I open this VeraCrypt volume in GNOME Files 5.497
Then I see the expected contents in this VeraCrypt volume 0.459
When I lock the currently opened VeraCrypt file container 0.101
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:330: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.729 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 07:37:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:37:36_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/24/artifact/build-artifacts/07:37:36_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:37:36_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:37:36_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.016
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
43.336
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.611
And I unlock and mount this VeraCrypt file container with GNOME Disks 21.366
And I open this VeraCrypt volume in GNOME Files 4.745
Then I see the expected contents in this VeraCrypt volume 0.507
When I lock the currently opened VeraCrypt file container 0.105
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:330: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.807 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM' (at time 07:38:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/24/artifact/build-artifacts/07:38:35_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/24/artifact/build-artifacts/07:38:35_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/24/artifact/build-artifacts/07:38:35_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/24/artifact/build-artifacts/07:38:35_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000